Core System Errors (ID 1001 through 1022)
1001 property property-name is invalid, using default |
The property entered in the tspr.properties file for a device is invalid. The system is using the default value.
Solution:Enter a valid value for this property in the tspr.properties file or remove the line entirely.
1002 cannot get database access |
The device cannot access the CPDB.
Solution:Ensure that the database settings in /etc/opt/terraspring /tspr.properties are correctly pointing to the database. Check that the database is running. See the N1 Provisioning Server 3.1, Blades Edition, Installation Guide for details.
1003 method name with null arguments |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1004 not registered |
The process is not yet registered.
Solution:Restart all the processes on the control plane server, most important, segment manager. Also ensure that the database is not corrupted by, for instance, manual manipulation of data.
1005 application-ID already registered |
The process has already been registered
Solution:Stop and restart the segment manager.
1006 invalid entry in application table with application-ID |
The application table in the CPDB contains an invalid entry for the application.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1007 cannot dequeue or update request (request ID) |
The server is unable to process or update the specified request ID.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1008 Object name not serializable |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1009 invalid destination aid |
The database contains an invalid entry of a destination application ID (AID) associated with a particular process.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1011 cannot send event to destination-aid (exception-details) |
A process is unable to send an event to another process with destination_aid.
Solution:Ensure that the destination application is running properly.
1012 invalid request id |
An invalid request ID has been provided.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
1013 timeout expires |
An execution of a request has timed out.
Solution:A request performs a task. When this task is being executed, a timeout value is usually associated with the request. When the time since execution exceeds this value, this message is printed. Ensure that the destination application is running. Also ensure that no blocked requests for the destination application exist. Try to reissue the command.
1014 application-ID: max number of digit exceeded |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1015 application-ID: not a digit |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1016 Invalid IP address: IP-address |
An invalid IP address has been provided.
Solution:Check that all IP addresses in the CPDB have been correctly entered.
1017 method name:value invalid argument |
An invalid argument has been entered.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1022 Could NOT create the LogHandler, classname. |
An invalid LogHandler has been entered for the com.terraspring. core.log.exthandler.
Solution:Ensure that the exthandler property is set to a valid class name that implements the LogHandler interface.
- © 2010, Oracle Corporation and/or its affiliates