Siebel Analytics Message Reference > Siebel Analytics Messages >

Siebel Analytics Client Communication Messages

This category contains message numbers 73xxx.

73001

Cannot contact the primary Cluster Controller (@1%s) or the secondary Cluster Controller (@2%s) specified for the clustered DSN.

Cause.  The primary and secondary Cluster Controller specified for the clustered DSN may not be up and running or may be overloaded.

Response.  Check the network connection and make sure that the Cluster Controllers specified are running properly. Try the action again. If the problem persists, contact Siebel Systems technical support for assistance.

73002

System Error from COM execution: @1%s. Failed at stage @2%s on machine @3%s. Reconnection succeeded on machine @4%s.

Cause.  An error was encountered while executing a COM call to a Siebel Analytics Server node. A retry on another machine was successful.

Response.  Verify that the Cluster Controller and Siebel Analytics Server nodes are properly configured, and review other system configuration information. Make any necessary changes. Verify that all Siebel Analytics Servers are online.

73003

System error from COM execution: @1%s. Failed at stage @2%s on machine @3%s. Attempted recovery failed on machine @4%s; System error from COM execution: @5%s.

Cause.  An error was encountered executing a COM call to a Siebel Analytics Server. A retry on another machine still failed.

Response.  Verify that the system configuration, in particular the Cluster Controller and Siebel Analytics Server lists, is correct. Verify that all Siebel Analytics Servers are up and running. If the problem persists, contact Siebel Systems technical support for assistance.

73004

COM Execution error @1%s at @2%s.

Cause.  An error was encountered executing COM at the specified line.

Response.  Verify that the system configuration, in particular the Cluster Controller and Siebel Analytics Server lists, is correct. Verify that all Siebel Analytics Servers are up and running. If the problem persists, contact Siebel Systems technical support for assistance.

73005

Execution error @1%s at @2%s.

Cause.  An error was encountered in executing the specified line.

Response.  Verify that the system configuration, in particular the Cluster Controller and Siebel Analytics Server lists, is correct. Verify that all Siebel Analytics Servers are up and running. If the problem persists, contact Siebel Systems technical support for assistance.

73006

Cannot obtain Siebel Analytics Servers from either the primary Cluster Controller (@1%s) or the secondary Cluster Controller (@2%s) specified for the clustered DSN.

Cause.  There may not be any Siebel Analytics Servers connected to the primary and secondary Cluster Controllers specified for the clustered DSN, or the Siebel Analytics Servers may not be up and running or they may be overloaded.

Response.  Check the network connection; make sure that the Siebel Analytics Servers are online and that they are connected to the Cluster Controller. If the problem persists, contact Siebel Systems technical support for assistance.

73007

Reconnection for the clustered DSN @1%s has been time-out.

Cause.  The primary and secondary Cluster Controllers specified for the clustered DSN may not be up and running, they may be overloaded, or there may be no Siebel Analytics Servers connected to them.

Response.  Check the network connection, make sure that the specified Cluster Controllers are running properly and that there are Siebel Analytics Servers connected to the Cluster Controllers.

73008

COM Execution error at of Siebel Analytics ODBC OpenSession() call.

Cause.  An error was encountered when executing Siebel Analytics ODBC OpenSession() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73009

COM Execution error at Siebel Analytics ODBC OpenRequest() call.

Cause.  An error was encountered when executing Siebel Analytics ODBC OpenRequest() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73010

COM Execution error at Siebel Analytics ODBC GetMessages() call.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73011

COM Execution error at Siebel Analytics ODBC GetMessages() call. The call is still running asynchronously.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call. The query is still running.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73012

COM Execution error at Siebel Analytics ODBC GetMessages() call. The task has been cancelled.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73013

COM Execution error at Siebel Analytics ODBC GetMessages() call. The call has been timed out.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73014

COM Execution error at Siebel Analytics ODBC GetMessages() call. The task has been killed.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73015

COM Execution error at Siebel Analytics ODBC GetMessages() call. An improper call sequence has been encountered.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73016

COM Execution error at Siebel Analytics ODBC GetMessages() call.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM The server has been shut down.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73017

COM Execution error at Siebel Analytics ODBC GetMessages() call. The call has succeeded with warnings.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73018

COM Execution error at Siebel Analytics ODBC GetMessages() call. The end of data has been reached.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.

73019

Governor Violation error during COM exectution at Siebel Analytics ODBC GetMessages() call.

Cause.  An error was encountered when executing Siebel Analytics ODBC GetMessages() COM call.

Response.  Check that the Cluster Controllers and their nodes are properly configured, and verify other cluster configuration information. Verify that all Siebel Analytics Servers are up and running.


 Siebel Analytics Message Reference
 Published: 11 March 2004