Reason:
Either the CPUID record in the appropriate CA VM:Schedule configuration file has the wrong CPUID or the CA VM:Schedule CPUID has expired and there are no days left in the grace period. CA VM:Schedule cannot operate without a valid CPUID for this CPU, and, therefore, shuts down.
Action:
Your CA VM:Schedule system administrator must call Technical Support for a new CPUID.
|
Copyright © 2013 CA.
All rights reserved.
|
|