Symptom:
Client machines or gateways fail to connect to the CMS.
Reason:
A change to the CMS system clock can sometimes cause subsequent connection attempts by client machines and gateways to fail. This is because key service objects on the CMS are mistakenly deleted as a result of the unexpected time change.
The problem is very rare, but if it happens the following error message is written to the CA Data Protection system log on the client machine or gateway (you may also see it on-screen):
java.rmi.NoSuchObjectException: no such object in table
Note: Logfiles are saved in the CA Data Protection \data\log subfolder of the Windows All Users profile.
Solution:
If you suspect that this problem has occurred, or you see this error message, you must restart the CA Data Protection infrastructure on the CMS.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|