Reason:
During initialization, CA VM:Secure found that its own user ID (normally VMSECURE) was not in the directory database, or was on hold. The most likely explanation for this is manual copying, renaming, or erasing of files on one or more of the CA VM:Secure minidisks. CA VM:Secure does not complete initialization, and is not operative.
Action:
Log on to the CA VM:Secure service virtual machine and access the DRCT, BKUP, and HOLD minidisks. If there is a directory entry for the CA VM:Secure service virtual machine on the BKUP or HOLD minidisk, move it to the DRCT minidisk. If there is no directory entry for the CA VM:Secure service virtual machine, you must restore one from your most recent backup of the DRCT minidisk. Since this error indicates manual manipulation of the CA VM:Secure database, you should check carefully for any other errors on these minidisks.
|
Copyright © 2014 CA.
All rights reserved.
|
|