Bookshelf Home | Contents | Index | PDF |
Siebel Analytics Message Reference > Siebel Analytics Messages > Siebel Analytics Communications MessagesThis category contains message numbers 11xxx - 12xxx. 11001Siebel communication error (@1%x): @2%s, File @3%s, line @4%d. Verify Siebel Analytics Server machine is accessible. Cause. A communications error occurred at the specified location in the named file. The Siebel Analytics Server service may not be available. Response. Verify that the Siebel Analytics Server service is started, and then try the action again. If the problem persists, contact Siebel Systems Technical Support for assistance. 11002Siebel communication error (@1%x): @2%s. Verify Siebel Analytics Server machine is accessible. Cause. A communications error occurred. The Siebel Analytics Server service may not be available. Response. Verify that the Siebel Analytics Server service is started, and then try the action again. If the problem persists, contact Siebel Systems Technical Support for assistance. 11003Siebel communication error: @1%s, File @2%s, line @3%d. Verify Siebel Analytics Server machine is accessible. Cause. A communications error occurred at the specified location in the named file. The Siebel Analytics Server service may not be available. Response. Verify that the Siebel Analytics Server service is started, and then try the action again. If the problem persists, contact Siebel Systems Technical Support for assistance. 11004Siebel communication error: @1%s. Verify Siebel Analytics Server machine is accessible. Cause. A communications error occurred. The Siebel Analytics Server service may not be available. Response. Verify that the Siebel Analytics Server service is started, and then try the action again. If the problem persists, contact Siebel Systems Technical Support for assistance. 12001Unable to connect to Domain Controller for OS authentication. Cause. Operating system authentication could not be performed because the domain controller could not be accessed. The domain controller may be down, or the network may be experiencing problems. Response. Correct any communications problems, and verify that the domain controller is accessible. Try the action again. If the problem persists, contact Siebel Systems Technical Support for assistance. 12002Socket communication error at call=@1%s: (Number=@2%d) @3%s Cause. The communication failure is likely caused by incorrect Siebel ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12003Call=@1%s: An unknown socket communications error has occurred. Cause. The communication failure is likely caused by incorrect Siebel ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12004A socket has been closed while reading @1%lu of @2%lu bytes. Cause. The communication failure is likely caused by incorrect Siebel ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12005Cause. The communication failure is likely caused by incorrect Siebel ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12006Cannot initialize TCP/IP communications layer: unspecified port number. Cause. The communication failure is likely caused by an incorrect Siebel Analytics Server installation or configuration. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12007Cannot find port number for unknown service name: @1%s. Cause. The communication failure is likely caused by an incorrect Siebel Analytics Server installation or configuration. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12008Unable to connect to port @1%s on machine @2%s. Cause. This communication failure is likely caused by an incorrect Siebel Analytics Server installation or configuration. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). If basic network connectivity is present, then consider increasing the maximum number of server threads as the server could reject new connection requests to avoid exceeding the configured maximum number of threads. 12009Illegal message from client requesting unknown remote function @1%ld. Cause. This communication failure is likely caused by an incorrect Siebel Analytics Server installation or configuration (for example, incompatible client and server versions). Response. Correct any configuration problems. 12010Communication error connecting to remote end point: address = @1%s; port = @2%s. Cause. The communication failure is likely caused by incorrect Siebel Analytics ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12011Unexpected server-side socket shutdown detected by client-side heartbeat facility. Cause. The communication failure is likely caused by incorrect Siebel Analytics ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12012Unexpected client shutdown detected by orphaned heartbeat thread. Cause. The communication failure is likely caused by incorrect Siebel Analytics ODBC DSN communication settings or a bad server installation. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12013An unknown server error has occurred while responding to a socket message from the client. Cause. Unexpected server-side problem. Response. Contact Technical Support. 12014Illegal access to a socket pool that has not been opened or explicitly closed. Cause. Unexpected client-side problem. Response. Contact Technical Support. 12015Communication error with remote end point:@1%s. Cause. It is likely that the underlying network layer has failed, if the installation and configuration settings are correct. Response. Correct any communication configuration problems, and verify that underlying network connectivity is available (for example, using ping). 12016Client is incompatible with the server. Cause. This communication failure is likely caused by an incorrect Siebel Analytics Server installation or configuration (for example, incompatible client and server versions). Response. Correct any configuration problems. 12017Unexpected socket read timeout: connection terminated by network, e.g. by the firewall. Cause. This communication failure is likely caused by a firewall configuration with an overly aggressive time out of less than 5 minutes. |
Siebel Analytics Message Reference |