Reason:
Your site’s VMXRPI CONFIG file lists the second (optional) parameter of the AVAILCHK record to specify that the system operator should be warned after a certain number of 30‑second intervals if the CA VM:Secure service virtual machine has not initialized the Rules Facility. This number of intervals has been reached, and the CA VM:Secure service virtual machine has still not initialized the Rules Facility. The system continues to send the message each time the specified number of intervals passes without Rules Facility initialization.
Action:
Check the status of the CA VM:Secure service virtual machine. If it is not logged on, log it on (or autolog it) to correct the problem, and review your procedures for autologging this service virtual machine at system startup time. If the CA VM:Secure service virtual machine is logged on, there may be an error in one of your configuration files that has aborted initialization of CA VM:Secure. It is also possible that the ACCESS RULE record has been removed from the PRODUCT CONFIG file, which would cause CA VM:Secure not to initialize the Rules Facility. Also, something may have happened to the rules minidisk. Check to see if the RULE minidisk still exists, has a label of RULE, and has rules files on it.
Examine the console log from the attempted initialization to diagnose the problem.
|
Copyright © 2014 CA.
All rights reserved.
|
|