Technical article 116782

Upgrading an AFPS 3.5.2n server, which is a PDC or BDC providing a resource domain with accounts from a trusted account domain, the upgrade to AFPS 4.0.2 fails.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

When upgrading an AFPS 3.5.2n server, which is a PDC or BDC providing a resource domain with accounts from a trusted account domain, the upgrade to AFPS 4.0.2 fails.

For example, if you have a Master Domain called "DOMAINA", which contains a list of users and global groups, such as "fred". This is known as the Account Domain.

You also have a domain of servers called "DOMAINB", which provide
resource and have a collection of local groups that refer to users
from the Account Domain.  This is known as the Resource Domain.

The Resource Domain trusts the Account Domain so that users from the Account Domain can access resources such as shares and printers.

If the Resource Domain is a Primary Domain Controller (PDC) or Backup Domain Controller (BDC) running AFPS 3.5.2n with or without APP606a and you try to upgrade to AFPS 4.0.2 for Windows 2000 support, the upgrade will fail.

To perform the Upgrade:

1. Boot into single-user mode 2. Manually remove APP606a, (the upgrade to 402 will do this for you) 3. Reboot into single-user mode 4. /usr/net/servers/lanman/bin 5. ./elfread -d system (to ensure that SAM,LSA,Built-in DBs are up to date)

NOTE: ./elfread -c <logname> will now clear the Event View log defined.

6. net stop server 7. ./samcheck -cv 8. net start server 9. Run "custom" 10.Select "Install New Software" 11.Select AFPS 4.0.2 from the Optional Services CD, warns that element will be upgraded

At the point at which the upgrade is in the process of restoring the SAM Database:

Reading the accounts database

The Domain Admins membership object is missing. MembershipSID:<Insert SID Number here> is not in alias 544's members.

1 built-in objects were missing. 1 membership links were incomplete. The SAM database is too corrupt to check or repair. If the role of the server is a backup domain controller, you must synchronize your account database with the Primary Domain Controller. Otherwise, you must run joindomain to create a new database. ERROR: Unable to initialize local SAM database. Aborting configuration temporarily. Creating post-processor script. This script will be run automatically when the kernel has been relinked and the system rebooted.

NOTE:     Even if the upgrade appears to be successful, it may still be
          corrupted and may still fail if alterations are made to the AFPS
          configuration within "netconfig".

Solution

The only workaround available at this time is to perform a fresh installation of AFPS 4.0.2 and recreate all the existing permissions.

This problem has been reported to SCO Engineering.

See also

ta116142, "Why do I get the message "Unknown Product Licensed Successfully" when installing SCO Advanced File and Print Server 4?"

From the Xinuos technical article database, record 116782. Reproduced with permission. The original is at www.sco.com/ta/116782, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.