PWRK-F-SAMCHECK (Advanced Server 7.3A upgrade)

[mssuk]

I tried upgrading Advanced Server from 7.2 to 7.3A-ECO2 last weekend (running under OpenVMS 7.3-1 which was not upgraded), but encountered a problem when running the PWRK$CONFIG procedure.

The error was as follows:-

PWRK-F-SAMCHECK, error upgrading SAM databases
PWRK-F-CONFIGERR, Server error during configuration

Does anyone know of a possible cause for this error?

 

[KIRBY2000]

I have the same problem and a possible work around.

If you run the SAMCHECK utility (ie: "SAMCHECK -s -v")
you will find (as I did) the SAM database is corrupted.
When it connects to the primary server (ie: 2000server)
the SAM database gets corrupted. It's documented
in the upgrade release notes.

On the current system run PWRK$CONFIG and set the
"Advanced Server domain:" parameter to somthing like
TEST and the "Advanced Server role:" from BACKUP
to PRIMARY. This will create a new (clean) SAM database.

Do the upgrade to EC02.
Change your PWRK$CONFIG parms back to where they were.
make sure you respond "Y" to the question
"Are you going to supply account/password info.."

I have NOT tried this yet, maybe in a few weeks I'll try
again.

Let me Know how it goes.

Thanks, Glen

Glen@Kirbyassociates.com

 

[HughSamson]

We do this with some frequency when refreshing a DR system of ours... supplying the password etc does work around it. However, at the end of the process, we answer NO to "start the pathworks processes". We then move the backup copy of SHAREDB back into the original position, and bring the services up. Works well enough for us...


Hugh.

 

[KIRBY2000]

When you run PWRK$CONFIG, Isn't the SHAREDB file
preserved?
Unless...if you delete it, and let it create a new one...

Thanks, Glen

FYI: The following message was posted on the OpenVMS.org technical forum in response to my possible work around:
Author: Michael Martone (---.nut.roche.com)
Date: 03-04-04 09:06

I got this error and tried to fix the corrupt SAM database. However, the real problem was a corrupt OpenVMS Registry. If you are still having this problem, you can build the Registry in another directory and then run PWRK$CONFIG (without making any changes).

Let me know if you still need help.

Best Regards,
Michael

 

[HughSamson]

We copy the following files, which let's us put the shares and security back as it should be, after leaving then rejoining the domain:

From:
pwrk$root:[lanmman.datafiles.<date>]
ACL.;
SHAREDB.;
LSA.;

To:
pwrk$root:[lanmman.datafiles]

It always comes up fine for us... all shares and security settings are back to normal, and we can then run a succesful SAMCHECK...