Siebel Analytics Message Reference > Siebel Analytics Messages >

Communication Access Messages

This category contains message numbers 49xxx.

49001

The handler is not installed.

Cause. A handler for the Siebel Analytics Server service could not be located or could not be registered.

Response. Make sure that the Siebel Analytics Server service is set up correctly in the service control panel. See Siebel Analytics Installation and Configuration Guide and Siebel Analytics Server Administration Guide for additional details. If the problem persists, contact Siebel Systems Technical Support for assistance.

49002

Bad service request.

Cause. The Siebel Analytics Server service received an invalid service request.

Response. Make sure the COM gateway registration parameters are valid. To configure the Siebel Analytics Server to be automatically launched by a remote client, see Siebel Analytics Server Administration Guide. If the problem persists, contact Siebel Software Technical Support for assistance.

49003

Siebel Analytics Server service stopped.

Cause. The Siebel Analytics Server service stopped normally.

Response. The is an informational message. No action is required.

49004

Bad server configuration - Siebel service shutting down.

Cause. The Siebel Analytics Server service detected an invalid configuration, such as the incorrect spelling of a repository file name, and shut down.

Response. Review the messages in the NQServer.log file, and correct any syntax errors in the NQSConfig.ini file. Restart the Siebel Analytics Server service.

49005

The Siebel Analytics Server failed to startup - check the server log for details. Siebel service shutting down.

Cause. During start up, the Siebel Analytics Server service encountered conditions that prevented it from completing the start up process.

Response. Review the messages in the NQServer.log file for error details and follow the recommended actions to correct the problem. Restart the Siebel Analytics Server service.

49006

Siebel Analytics Server service terminated.

Cause. The Siebel Analytics Server service ended normally.

Response. If the service termination is not expected, examine previous messages in the NQServer.log file to determine the cause.

49007

Siebel Analytics Server service could not be terminated.

Cause. A request to terminate the Siebel Analytics Server service was received, but could not be processed.

Response. Kill the Siebel Analytics Server service, and the nqscomgateway processes. Restart the Siebel Analytics Server service.

49008

Siebel Analytics Server service halted.

Cause. A request to pause the Siebel Analytics Server service was received and processed normally.

Response. If the service pause is not expected, examine previous messages in the NQServer.log file to determine the cause.

49009

Server startup event creation failed - Siebel Analytics Server service shutting down.

Cause. The Siebel Analytics Server service encountered invalid start-up parameters.

Response. Make sure that the Siebel Analytics Server service is set up correctly in the Windows Service Control panel. See Siebel Analytics Installation and Configuration Guide and Siebel Analytics Server Administration Guide for additional details. If the problem persists, contact Siebel Systems Technical Support for assistance.

49010

Siebel Analytics Server service started.

Cause. A request to start the Siebel Analytics Server service was received and processed normally.

Response. This is an informational message. No action is required.

49011

Server shut down by request. Halting Siebel Analytics Server service.

Cause. A request to shut down the Siebel Analytics Server service was received and is being processed.

Response. This is an informational message. No action is required.

49012

Could not create the start event to restart Siebel Analytics Server service.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

49013

Could not restart Siebel Analytics Server service.

Cause. The Siebel Analytics Server service encountered errors that prevented it from restarting.

Response. Review the messages in the NQServer.log file for error details and follow the recommended actions to correct the problem. Restart the Siebel Analytics Server service. If necessary, contact Siebel Systems Technical Support for assistance.

49014

Siebel Analytics Server shut down unexpectedly - restarted.

Cause. The Siebel Analytics Server service shut down unexpectedly, but restarted normally. An unexpected shut down can be caused, for example, by a power failure.

Response. This is an informational message. No action is required.

49015

Siebel Analytics Server shut down unexpectedly - restart failed.

Cause. The Siebel Analytics Server shut down unexpectedly and was unable to restart. An unexpected shut down can be caused, for example, by a power failure.

Response. Examine previous messages in the NQServer.log file to determine why the service was unable to restart and follow the recommended actions to correct the problem. Restart the Siebel Analytics Server service. If necessary, contact Siebel Systems Technical Support for assistance.

49016

Server shut down unexpectedly - received stop during restart.

Cause. The Siebel Analytics Server shut down unexpectedly. During restart, a stop request was received. An unexpected shut down can be caused, for example, by a power failure.

Response. This is an informational message. No action is required. However, if the stop request was not expected, examine previous messages in the NQServer.log file to determine the cause.

49017

Server shut down unexpectedly - no exit code available. Halting Siebel service.

Cause. After an unexpected shut down of the Siebel Analytics Server, no exit code was available. This caused the Siebel Analytics Server service to be halted.

Response. Examine previous messages in the NQServer.log file to determine why the Server shut down. Correct any problems and then restart the Siebel Analytics Server service. If necessary, contact Siebel Systems Technical Support for assistance.

49018

Siebel Analytics Server pid @1%d exists, but cannot be opened - Siebel Analytics Server service halting.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

49019

Attached to existing Siebel Analytics Server: pid @1%d.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

49020

Siebel Analytics Server start up failed - cannot get exit code.

Cause. The Siebel Analytics Server failed to start. No exit code was available.

Response. Examine previous messages in the NQServer.log file to determine why the server was unable to start and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49021

Siebel Analytics Server failed to open the Service Manager during @1%s. The error is: @2%s.

Cause. The Siebel Analytics Server failed to open the Service Manager.

Response. Examine previous messages in the NQServer.log file to determine if the server was unable to start due to a prior error and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49022

Siebel Analytics Server failed to create a service during @1%s. The error is: @2%s.

Cause. The Siebel Analytics Server failed to create a Service.

Response. Examine previous messages in the NQServer.log file to determine if the server was unable to start due to a prior error and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49023

Siebel Analytics Server failed to delete a service during @1%s. The error is: @2%s.

Cause. The Siebel Analytics Server failed to delete a Service.

Response. Examine previous messages in the NQServer.log file to determine if the server was unable to start due to a prior error and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49024

Siebel Analytics Server failed to create a valid Event in @1%s.

Cause. An Event in Siebel Analytics Server is not valid.

Response. Examine previous messages in the NQServer.log file to determine why the server was unable to start and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49025

Siebel Analytics Server failed to create a process in @1%s. The error is: @2%s.

Cause. The Siebel Analytics Server failed to create a Service.

Response. Examine previous messages in the NQServer.log file to determine why the server was unable to start and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49026

Siebel Analytics Server caught an unknown exception.

Cause. An unknown exception was caught in the Siebel Analytics Server.

Response. Examine previous messages in the NQServer.log file to determine why the server was unable to start and follow the recommended actions to correct the problem. If necessary, contact Siebel Systems Technical Support for assistance.

49027

Siebel Analytics Server failed to create the required events - Siebel Analytics Server service shutting down.

Cause. The Siebel Analytics Server service encountered invalid start-up parameters.

Response. Make sure that the Siebel Analytics Server service is set up correctly in the Windows Service Control panel. See Siebel Analytics Installation and Configuration Guide and Siebel Analytics Server Administration Guide for additional details. If the problem persists, contact Siebel Systems Technical Support for assistance.

49028

Siebel Analytics Server encountered an error while waiting for an event.

Cause. The Siebel Analytics Server service encountered invalid wait parameters.

Response. Make sure that the Siebel Analytics Server service is set up correctly in the Windows Service Control panel. See the Siebel Analytics Installation and Configuration Guide and Siebel Analytics Server Administration Guide for additional details. If the problem persists, contact Siebel Systems Technical Support for assistance.

49029

An error was encountered in ServerManager @1%s.

Cause. An known exception was caught in the Siebel Analytics Server.

Response. Examine the error message in the NQServer.log file to determine if this error was caused by a previous error. If necessary, contact Siebel Systems Technical Support for assistance.

49030

An unknown Exception was encountered in ServerManager @1%s.

Cause. An unknown exception was caught in the Siebel Analytics Server.

Response. Examine the error message in the NQServer.log file to determine if this error was caused by a previous error. If necessary, contact Siebel Systems Technical Support for assistance.