If after installing Security Center, you are unable to open the MCP Cryptographic Services logical database or the realms logical database, refer to the following text for troubleshooting tips.
Waiting Entries
If a waiting entry shows a program waiting for *SYSTEM/ACCESSROUTINES ON DISK, this indicates that the Security Center database was not installed correctly.
Verify the following:
-
The most up-to-date version of the Security Center MMC snap-in has been installed on the workstation from which the installation is initiated.
-
All database users are logged off before beginning the installation.
A waiting entry that indicates the database must be initialized means that the Security Center database had not yet been installed when a program other than Security Center attempted to access user realms data. Each time a user attempts to access realms in this case, another waiting entry might be generated.
To resolve this situation
-
Use the Security Center MMC snap-in to install the database.
-
Remove the waiting entries by responding <mix>OK or <mix>DS to each entry. These entries have no impact on the ability to access the database once it has been installed. A large number of them, however, might occupy enough job queue entries that other jobs in that queue are prevented from starting.
Security Error
A failed attempt to open the database and a security error might indicate that the usercode or program attempting the access is not in the guard file.
Access to the Security Center database is limited to the programs and users listed in the guard file. During database installation, *SYSTEM/SECURITYCENTER creates the guard file as *SECURTIYCENTERGF and saves the source for the guard file as SYMBOL/SECURITYCENTERGF. The SYMBOL file is saved under the usercode of the administrator who initiates the installation.
Additional programs and users can be specified by editing the SYMBOL file and running the GUARDFILE utility to create a new guard file.
Open Error
If an Enterprise Database Server open error 41 appears on the ODT display or in the SUMLOG, this error indicates that not all versions of the database access programs and utilities are compatible with the current *DESCRIPTION/SECURITYCENTERDB file.
The installation might not have been successful, or an old version of one or more programs was executed. Do the following:
-
If the Security Center database is in use when the installation begins, mismatched DMSII run-time software occurs. Refer to Preparing for Installation. Discontinue any current database users, save the *SYSTEM/SECURITYCENTERDB/DBLOADDUMPFILE file and reinstall Security Center
-
If that does not resolve the open error, mismatched files must exist in the code path. Using BOT entries in the SUMLOG, and Release ID information in PD or CANDE LFILES responses, verify that the Release ID of SYSTEM/SECURITYCENTER and of the code files named SYSTEM/SECURITYCENTERDB/= show the same release levels. Resolve mismatches, particularly between SYSTEM/SECURITYCENTER and SYSTEM/SECURITYCENTERDB/DMSUPPORT.
