Technical article 118118

Upgrade from AFPS 3.5.2n fails.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written

Problem

Upgrading from 3.5.2n to 4.0.2 appears to work fine and although the shares are accessible after the upgrade, if I try to change the name of the server by using the "netconfig" command, it results in the following error appearing in:

/usr/net/servers/lanman/logs/lmxconfig.log
Restoring SAM database...
or:
^[[=0Restoring SAM database...

Reading the accounts database Failed to open or create /usr/net/servers/lanman/samsave/harveywst. 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 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.

Solution

The workaround to this situation would be to perform a fresh install of AFPS 4.0.2.

This problem has been reported to SCO Engineering.

NOTE:     If you are installing on OpenServer 5.0.4/5.0.5 then you will need to
          install OSS605a the NetBIOS patch available from:
https://ftp.scoexpert.com/openserver5

Otherwise you may experience a "tcl" error from the installation script during the install process.

See also

ta#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."

lmshare(AS)

From the Xinuos technical article database, record 118118. Reproduced with permission. The original is at www.sco.com/ta/118118, which is reachable but blocked from search engines.

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.