|
|
|
The following messages are produced by the Agent Technology Calendar function.
Reason:
An error occurred while attempting to process your request as a Logical Unit of Work (LUW).
Action:
Contact your system administrator.
Reason:
This message is typically accompanied by additional messages, which together describe the cause of the problem. These messages are useful to CA Support technicians and your system administrator. Contact your system administrator initially to correct this problem condition.
Action:
Check the accompanying error messages and consult your system administrator. For assistance, contact CA Support.
Reason:
A database error occurred while attempting to select a calendar from the database.
Action:
Contact your system administrator.
Reason:
An error occurred while attempting to commit your request as a Logical Unit of Work (LUW).
Action:
Contact your system administrator.
Reason:
A number of reasons can cause this error. You may not have authority to access the database, or the database may not be running.
Action:
Check to be sure that you have authority to open the database and that the database is running.
Reason:
An internal error occurred while processing your Calendar request.
Action:
For assistance, contact CA Support.
Reason:
An error occurred while attempting to close the database.
Action:
Contact your system administrator.
Reason:
A CAICCI function failed. This message is followed by the CACM_E_012 message, which details the actual error.
Action:
Refer to the CAICCI Return Codes in the online help for information about the specified return code, and then contact your system administrator.
Reason:
A CAICCI function failed. This message is typically accompanied by additional messages, which together describe the cause of the problem. These messages are useful to CA Support technicians and your system administrator. Contact your system administrator initially to correct this problem.
Action:
Check the accompanying error messages and consult your system administrator. For assistance, contact CA Support.
Reason:
An attempt to acquire virtual memory, through the malloc library call, failed.
Action:
Consult your system administrator. Additional system swap space may need to be defined. For assistance, contact CA Support.
Reason:
The Calendar is not defined to the database or was specified incorrectly.
Action:
Verify that the Calendar definition exists, and check the path and file name. Define the Calendar if it is not defined, or correct the path and file name. Resubmit the request. For assistance, contact CA Support.
Reason:
An invalid month or day value was specified as a date, or the date format is incorrect.
Action:
Contact your system administrator for the correct date format, correct the date, and resubmit the request.
Reason:
You specified an invalid time for a request.
Action:
Contact your system administrator for the correct time format, correct the time, and resubmit the request.
Reason:
You attempted to delete a Calendar profile that does not exist in the database.
Action:
No action is required.
Reason:
A number of reasons could cause this error:
Action:
Check the accompanying error messages to determine the exact cause and proceed accordingly. For assistance, contact CA Support.
Reason:
An error occurred during the execution of the system stat command. A component of the path does not exist or is not a directory.
Action:
Verify that the Calendar definition exists, and check the path and file name. Define the Calendar if it is not defined, or correct the path and file name. Resubmit the request. For assistance, contact CA Support.
Reason:
The binary file is either too long or too short.
Action:
Recreate the binary file by saving the Calendar definition using either the GUI or the command line interface.
Reason:
A number of reasons could cause this error:
Action:
Check the accompanying error messages to determine the exact cause and proceed accordingly. For assistance, contact CA Support.
Reason:
An internal error occurred while trying to read the binary file.
Action:
Recreate the binary file by saving the Calendar definition using either the GUI or cautil.
Reason:
You attempted to update a Calendar profile, but did not specify an ID.
Action:
Specify an ID and resubmit the request.
Reason:
A number of reasons could cause this error:
Action:
Check the path and file name of the Calendar, correct it and resubmit the request, or define a new Calendar profile. For assistance, contact CA Support.
Reason:
The path name specified is invalid or you do not have permission to access it.
Action:
Verify that the path name is correct and that you have permission to access it.
Reason:
An error occurred while deleting a Calendar definition from the database.
Action:
Check the Calendar name and path name to be sure it exists. For assistance, contact CA Support.
Reason:
The Calendar specified does not exist in the database.
Action:
Check the name of the Calendar, correct it and resubmit the request, or define a new Calendar profile.
Reason:
The Calendar process was unable to access the system date and time.
Action:
Contact your system administrator.
Reason:
A number of reasons could have caused this error:
Action:
Contact your system administrator.
Reason:
A number of reasons could have caused this error:
Action:
Contact your system administrator.
Reason:
The Calendar process was unable to open the key lock file used to prevent more than one Calendar process from starting.
Action:
For assistance, contact CA Support.
Reason:
The process ID of the previous Calendar process was not saved in the key lock file.
Action:
For assistance, contact CA Support.
Reason:
The prior Calendar process was shutdown prematurely or terminated in an error.
Action:
Restart the calendar service provider. For assistance, contact CA Support.
Reason:
The calendar process failed to position to the beginning of the key lock file.
Action:
For assistance, contact CA Support.
Reason:
The calendar process encountered an error while writing the process ID to the key lock file.
Action:
For assistance, contact CA Support.
Reason:
The calendar process was unable to create a new key lock file.
Action:
For assistance, contact CA Support.
Reason:
The process ID was not stored in the key lock file due to a previous error.
Action:
For assistance, contact CA Support.
Reason:
The Calendar process encountered an error while closing the key lock file.
Action:
For assistance, contact CA Support.
Reason:
An error occurred during the binary file rebuild. The named Calendar was not added to the active Calendar list.
Action:
Check the reasons and actions of all accompanying messages.
Reason:
The Calendar process has terminated.
Action:
Examine previous messages to see why the process terminated.
Reason:
A Calendar process running in CLIENT mode received a request for an operation that is only available while running in SERVER mode.
Action:
This is probably due to an installation error. Correct the install options with SVSETUP.
Reason:
The Action routine was unable to perform the request because the Calendar process is not started on the indicated node.
Action:
Start the Calendar process using the UNICNTRL START COM command. For more information on the UNICNTRL command, consult the online help.
Reason:
The calendar name you specified as part of a copy, rename, or save process has already been used.
Action:
Choose another calendar name and resubmit the processes.
Reason:
An internal error occurred that prevented the Calendar process from reattempting to connect to the database or DSB file.
Action:
For assistance, contact CA Support.
Reason:
An error occurred while attempting to access (open | map | verify) the calendar DSB file.
Action:
If an open error: Check the DSB file name and path for existence.
If a verify error: The DSB file is unrecognizable due to corruption or version incompatibility. Contact your system administrator.
If a map error: For assistance, contact CA Support.
Reason:
The value specified for the calendar configuration option Copy on incore Calendars is invalid.
Action:
Contact your system administrator.
Reason:
You have reached the limit of the calendar command buffer for this calendar. Any additional modification commands will not be saved for this calendar.
Action:
You can only exit from this calendar without saving your changes.
Reason:
An attempt to acquire virtual memory, through the malloc library call, failed.
Action:
Consult your system administrator. Additional system swap space may need to be defined. For assistance, contact CA Support.
Reason:
A system error occurred while attempting to start a child process. This message is typically accompanied by additional messages, which together describe the cause of the problem. These messages are useful to CA Support technicians and your system administrator. Contact your system administrator initially to correct this problem condition.
Action:
Check the accompanying error messages and consult your system administrator. For assistance, contact CA Support.
Reason:
Only one Calendar process can be active at a time.
Action:
Use the cautil caladmin -s command to shut down the previous process.
Reason:
The Calendar process was unable to create the key lock file.
Action:
For assistance, contact CA Support.
Reason:
The Calendar process was unable to establish a new session. This message is typically accompanied by additional messages, which together describe the cause of the problem. These messages are useful to CA Support technicians and your system administrator. Contact your system administrator initially to correct this problem condition.
Action:
Check the accompanying error messages and consult your system administrator. For assistance, contact CA Support.
Reason:
Informational message.
Action:
No action is required.
Reason:
Informational message.
Action:
No action is required.
Reason:
This message displays when you initialize or refresh the Calendars loaded into the Calendar process memory.
Action:
Informational only.
Reason:
The binary file for the named Calendar was created in a previous year and may have been invalid, so it was rebuilt.
Action:
Informational only.
Reason:
INSERT of named Calendar was successful after an unsuccessful ALTER.
Action:
Informational only.
Reason:
ALTER of named Calendar was successful after an unsuccessful INSERT.
Action:
Informational only.
Reason:
The caladmin command for shutting down the Calendar process was issued.
Action:
Informational only.
Reason:
The Calendar process has started processing. Initialization is in progress.
Action:
Informational only.
Reason:
The Calendar process is running.
Action:
Informational only.
Reason:
Part of the heading used by the Calendar process.
Action:
Informational only.
Reason:
The named Calendar is available.
Action:
Informational only.
Reason:
You attempted to unmount the original file system. This is not allowed.
Action:
Contact your system administrator.
Reason:
An interrupt signal was sent to the Calendar process. This message is typically accompanied by additional messages, which together describe the cause of the problem. These messages are useful to CA Support technicians and your system administrator. Contact your system administrator initially to correct this problem condition.
Action:
Check the accompanying error messages and consult your system administrator. For assistance, contact CA Support.
Reason:
The Calendar process could not successfully connect the database. Calendars are loaded from the DSB file path specified for the calendar settings description Copy of incore calendars. Subsequent database retry attempts will be made as the db load retry calendar settings.
Action:
Notify your system administrator of the connection failure so that the error can be investigated and corrected. Once the database is again available, the calendar process will reload its calendars at the next retry interval.
Reason:
The Calendar process was not successful in its attempt to access the database or DSB file after the specified number of retries.
Action:
If the calendar database or DSB file becomes available after the issuance of this message, calendars may be reloaded using the caladmin command with the -r option.
Reason:
A calendar update request was sent to the calendar process for the specified calendar. The request could not be processed either because the database was not yet available, or because the calendar configuration option Load from database? specified N (no).
Action:
If the calendar database becomes available after the issuance of this message, calendars may be reloaded using the caladmin command with the -r option. Otherwise, no action is required.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |