Siebel Analytics Message Reference > Siebel Analytics Messages >

Siebel Analytics Server Access Messages

This category contains message numbers 43xxx.

43001

Authentication failed for @1%s in repository @2%s: invalid user/password.

Cause. The named user was unable to access the named repository. The user ID or password is invalid.

Response. Correct the user ID, password, or both. For details on secure access control, see Siebel Analytics Server Administration Guide.

43002

Session: @1%x Query engine failed for repository: @2%s user: @3%s

Cause. In the named session, an unknown error caused the failure of a query for the named user and repository.

Response. Contact Siebel Systems Technical Support for assistance.

43003

Session: @1%x unknown error while preparing session.

Cause. An unknown error occurred while preparing the session.

Response. Contact Siebel Systems Technical Support for assistance.

43004

Session: @1%x repository name: @2%s is invalid

Cause. The session specified an invalid repository name.

Response. Verify the repository name, correct any errors, and try the action again.

43005

Request: @1%x query compile error. May be due to circularity in the join graph.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43006

Request: @1%x query execution error.

Cause. An unknown error occurred during query execution.

Response. Contact Siebel Systems Technical Support for assistance.

43007

Request: @1%x unknown request option: @2%ld.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43008

Request: @1%x cursor option has to be dynamic for repositioned fetch access.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43009

Request: @1%x improper cursor access property: @2%ld.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43010

Request: @1%x failed to access cursor record at location: @2%ld.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43011

Request: @1%x is not prepared before.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43012

Request: @1%x input parameter not given for execute.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43013

Request: @1%x mismatch between parameter record size: @2%d and given record size: @3%d.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43014

Request: @1%x is not in fetch state; fetch may not be called before execute.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43015

Query failed because of an unknown query preparation error.

Cause. An unknown error caused the query to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43016

Query failed because of an unknown execution error.

Cause. An unknown error caused the query to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43017

Query failed because of an unknown fetch error.

Cause. An unknown error caused the query to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43018

An unknown exception has taken place.

Cause. An unknown error caused the query to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43019

Catalog name or pattern not given.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43020

Schema name or pattern not given.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43021

Table name or pattern not given.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43022

Procedure: @1%ld not yet supported.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43023

Number of sessions exceeded the limit.

Cause. The request could not be processed. The session would exceed the maximum number of connections allowed by the server.

Response. Try the request again later. To increase the maximum number of sessions allowed by the server, modify the MAX_SESSION_LIMIT parameter in the NQSConfig.INI file. The server must be shut down and restarted to make the new value effective.

43024

Number of requests per session exceeded the limit.

Cause. The request could not be processed. The request would exceed the maximum number of logical requests allowed for a session.

Response. Allow some requests to complete, and then try the action again. Usually, individual users will have only one open request per session at the same time. Application programs and Siebel Analytics Web, however, will typically have more than one open at the same time. To increase the maximum number of logical requests allowed for a session, modify the MAX_REQUEST_PER_SESSION_LIMIT parameter in the NQSConfig.INI file. The server must be shut down and restarted to make the new value effective. See Siebel Analytics Installation and Configuration Guide for additional information about this parameter.

43025

Request: @1%x open failed because of system error.

Cause. A system error occurred.

Response. Review the system error logs for additional information. Contact Siebel Systems Technical Support for assistance.

43026

Server startup error. Shared memory could not be setup in the server.

Cause. The failure to set up shared memory caused the Siebel Analytics Server start up to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43027

Server startup error. Session table could not be setup.

Cause. The session table could not be set up during the Siebel Analytics Server start-up process.

Response. Contact Siebel Systems Technical Support for assistance.

43028

Server startup error. Server listener could not be setup.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43029

Server startup error. Server timer could not be setup.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43030

@1%s:Siebel Analytics Server started. Version: @2%s.

Cause. The specified version of the Siebel Analytics Server started normally.

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

43031

@1%s:Siebel Analytics Server shutdown.

Cause. The Siebel Analytics Server shut down normally.

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

43032

Siebel Analytics Server could not be started. Initialization failed.

Cause. An unknown error caused the Siebel Analytics Server initialization process to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43033

Server task procedure Id: @1%d is invalid.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43034

User is not authorized to shutdown the server.

Cause. A user has attempted to shut down the Siebel Analytics Server, but that user is not authorized to perform the task. Only users defined as Siebel administrators can shut down the Siebel Analytics Server.

Response. Define the user as an Siebel administrator, or have another properly authorized user shut down the server.

43035

User is not authorized to set the server in single user mode.

Cause. An unauthorized user attempted to set the Siebel Analytics Server into single user mode.

Response. Change the authority for the user, or have a properly authorized user perform the action.

43036

Catalog, @1%s, is unavailable. Please contact the administrator.

Cause. The named catalog is currently unavailable. It may be open in offline mode. When a repository is opened in offline mode, it means that the repository is not loaded by the Siebel Analytics Server and is therefore not accessible by any users.

Response. Contact your Siebel Analytics administrator.

43037

Invalid catalog, @1%s, specified.

Cause. The named catalog is invalid.

Response. Verify the catalog name and perform a consistency check on the repository. Correct any errors and try the action again.

43038

Invalid access mode, @1%s, specified.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43039

Invalid timeout value, @1%s, specified.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43040

Invalid transaction option, @1%s, specified.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43041

Invalid session state, @1%s, specified.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43042

Invalid session option, @1%d, specified.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43043

Task canceled.

Cause. An outstanding task has been canceled.

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

43044

Repository, @1%s, has no catalogs.

Cause. The named repository has no catalog.

Response. Review the Business Model and Mapping Layer and the Presentation Layer of the repository, and define at least one subject area.

43045

Repository, @1%s, opened in read-only mode. Another process may have it opened in update mode.

Cause. The named repository was opened in read-only mode. If the server is running, the named repository may already be loaded.

Response. This is an informational message. No action is required. If you want to edit the repository while it is loaded, you must open it in online mode.

43046

Another server is already running, pid: @1%d.

Cause. The Siebel Analytics Server service is already running.

Response. Contact Siebel Systems Technical Support for assistance.

43047

Invalid procedure name: @1%s.

Cause. The named procedure is invalid.

Response. Contact Siebel Systems Technical Support for assistance.

43048

Invalid call specification in procedure: @1%s.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43049

Invalid input specification for procedure: @1%s.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43050

Invalid catalog name: @1%s.

Cause. The specified catalog name is invalid.

Response. Correct the catalog name and try the action again.

43051

Invalid SQL query: @1%s.

Cause. The specified SQL query is invalid.

Response. Correct the query and try the action again.

43052

Invalid expression: @1%s.

Cause. The named expression is invalid.

Response. Correct the expression and try the action again.

43053

Drill-down is not currently supported for composite queries: @1%s.

Cause. The named query is a composite query. Drill-down is not supported for composite queries.

Response. Either modify the query so it is not a composite query, or do not attempt a drill-down.

43054

Log Viewer process reported error @1%d.

Cause. The process that was created to run nQLogViewer reported an error.

Response. Contact Siebel Systems Technical Support for assistance. Include the error code reported in this message.

43055

Unable to open file @1%s produced by Log Viewer, error @2%d.

Cause. The query log file that is produced by the nQLogViewer executable could not be opened.

Response. Check the permissions for the directories that are part of the filename. Correct any problems and try the nQLogViewer again.

43056

File access error @1%d from Log Viewer file @2%s.

Cause. The specified error occurred when accessing the query log file that is produced by the nQLogViewer executable.

Response. Contact Siebel Systems Technical Support for assistance. Include the error code reported in this message.

43057

Log Viewer process creation failed with error @1%d.

Cause. An attempt to create the nQLogViewer process in order to extract the information from the query log failed.

Response. Contact Siebel Systems Technical Support for assistance. Include the error code reported in this message.

43058

Unable to acquire exclusive lock for refreshing repository variable: @1%s.

Cause. There are too many concurrent users on the system to allow a successful metadata update.

Response. Wait until the system is less busy, then try the action again.

43059

Dynamic refresh of repository scope variables has failed.

Cause. An error caused a refresh of repository scope variables to fail. The data source may not be available or a failure may have occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43060

Missing repository: @1%s.

Cause. An unknown error caused the named repository to close unexpectedly.

Response. Contact Siebel Systems Technical Support for assistance.

43061

Server startup error. Cluster monitor could not be setup.

Cause. A Cluster monitor error caused the server start up to fail.

Response. Contact Siebel Systems Technical Support for assistance.

43062

Server startup error. Unable to establish listener on port specified in the SERVER_PORT parameter in the Cluster Configuration File.

Cause. Messages following this one may clarify the source of the problem.

Response. Review the associated messages and take the appropriate corrective actions. If the problem persists, contact Siebel Systems Technical Support for assistance.

43063

An unknown exception caused the thread accepting connections from Cluster Controllers to fail.

Cause. An internal error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

43064

The following unexpected errors caused the thread accepting connections from Cluster Controllers to fail.

Cause. Messages following this one may clarify the source of the problem.

Response. Review the associated messages and take the appropriate corrective actions. If the problem persists, contact Siebel Systems Technical Support for assistance.

43065

The connection with Cluster Controller @1%ls was lost.

Cause. A connection had been established with the specified Cluster Controller but the connection was later dropped. This may be caused by many conditions.

Response. If the specified Cluster Controller should be online, examine its state and repair or restart it if necessary. If problems persist, examine the network connectivity to the specified Cluster Controller.

43066

The configuration on Cluster Controller @1%ls specifies additional servers that are not present in the cluster configuration of this Siebel Analytics Server.

Cause. The cluster configuration files (NQClusterConfig.INI) on this Siebel Analytics Server and the specified Cluster Controller do not match. Normally, all the Siebel Analytics Servers and Cluster Controllers should have the same configuration. However, the Cluster Controller and the Siebel Analytics Server will continue to operate as part of the cluster in spite of this condition.

Response. If the reported differences are not intentional, update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43067

The configuration on Cluster Controller @1%ls is missing Siebel Analytics Server(s) that are included in the cluster configuration of this Siebel Analytics Server.

Cause. The cluster configuration files (NQClusterConfig.INI) on this Siebel Analytics Server and the specified Cluster Controller do not match. Usually, all the Siebel Analytics Servers and Cluster Controllers should have the save configuration. However, the Cluster Controller and the Siebel Analytics Server will continue to operate as part of the cluster in spite of this condition.

Response. If the reported differences are not intentional, update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43068

The configuration on Cluster Controller @1%ls specifies a different Primary Cluster Controller or client controller port than this Siebel Analytics Server's cluster configuration.

Cause. The cluster configuration files (NQClusterConfig.INI) on this Siebel Analytics Server and the specified Cluster Controller do not match. Normally, all the Siebel Analytics Servers and Cluster Controllers should have the save configuration. However, the Cluster Controller and the Siebel Analytics Server will continue to operate as part of the cluster in spite of this condition.

Response. If the reported differences are not intentional, update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43069

The configuration on Cluster Controller @1%ls specifies a different Secondary Cluster Controller or client controller port than this Siebel Analytics Server's cluster configuration.

Cause. The cluster configuration files (NQClusterConfig.INI) on this Siebel Analytics Server and the specified Cluster Controller do not match. Normally, all the Siebel Analytics Servers and Cluster Controllers should have the save configuration. However, the Cluster Controller and the Siebel Analytics Server will continue to operate as part of the cluster in spite of this condition.

Response. If the reported differences are not intentional, update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43070

Cluster Controller @1%ls contacted this Siebel Analytics Server but the local configuration does not indicate it is a Cluster Controller.

Cause. There may be an inconsistency between the NQClusterConfig.INI file for this Siebel Analytics Server and the NQClusterConfig.INI file for the specified Cluster Controller. The port numbers may be incorrect in one or both files, or the list of Siebel Analytics Servers may be incorrect in the Cluster Controller's NQClusterConfig.INI file. This may be the result of copying cluster configuration files from one cluster to another without appropriate modifications. This Siebel Analytics Server will ignore the invalid request.

Response. Update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43071

A connection with Cluster Controller @1%ls was established.

Cause. A connection has been established with the specified Cluster Controller. This is usually the result of either the Siebel Analytics Server or Cluster Controller restarting. This may also result from repairing a network connectivity problem that was previously preventing communication.

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

43073

The monitoring of the Cluster Controller at @1%ls failed for the following reasons.

Cause. The thread that was allocated to monitoring the specified Cluster Controller failed and Cluster Controller communication was terminated. The message that follow this will contain additional information.

Response. Examining the following messages and take the appropriate corrective action. If the problem persists, contact Siebel Systems Technical Support for assistance.

43075

An unknown exception was encountered while monitoring Cluster Controller at @1%ls.

Cause. An unknown exception occurred. This is generally the result of an internal error.

Response. Contact Siebel Systems Technical Support for assistance.

43076

The configuration on Cluster Controller @1%ls specifies a different Master Siebel Analytics Server than this server.

Cause. All Cluster Controllers and Siebel Analytics Servers must have the same Master Siebel Analytics Server specified in their NQClusterConfig.INI files.

Response. Update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43077

The query cache is being purged because new published repositories were located.

Cause. When newly published repositories are found, the query cache is automatically purged before importing the new repositories. This ensures that query results properly reflect changes in the imported repositories.

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

43078

The query cache purge operation failed.

Cause. An attempt to delete all of the query cache data files failed. Accompanying error messages give additional detail.

Response. Examine accompanying error messages to determine why the operation failed. After fixing the source of the failure, restart the server. If necessary, contact Siebel Systems Technical Support.

43079

Siebel Analytics Server could not start because locating or importing newly published repositories failed.

Cause. While searching the repository publishing directory for newly published repositories or while importing newly published repositories to the reporting server's repository directory, an error was encountered. The server could not be brought online due to this error. Most errors that are encountered while accessing the repository publishing directory can be ignored by setting the REQUIRE_PUBLISHING_DIRECTORY parameter to "NO" in the Siebel Analytics Server configuration file. However, note that setting this parameter to "NO" may result in inconsistent query results from different clustered servers if it causes a failure such as this one to be ignored.

Response. Examine accompanying error messages to determine why the operation failed. After fixing the source of the failure or altering the setting of the REQUIRE_PUBLISHING_DIRECTORY, restart the server. If necessary, contact Siebel Systems Technical Support.

43080

The user is not authorized to kill sessions.

Cause. The user does not have the security privileges for this operation.

Response. Log in as an administrative user to kill sessions.

4308

Illegal operation attempted on a closed session.

Cause. A session-level operation was attempted on a session that is not open.

Response. The calling program must be modified to correct this out-of-sequence function call error.

43082

Illegal operation attempted on a closed request.

Cause. A request-level operation was attempted on a request that is not open.

Response. The calling program must be modified to correct this out-of-sequence function call error.

43083

Internal error: CheckReturnStatus should no longer be used to implement asynchronous calls.

Cause. There is an internal problem with this implementation of asynchronous calls.

Response. Try using synchronous calls only. Secondly, submit a service report to Technical Support.

43084

Function call sequence error: CloseServer called without a preceding OpenServer call.

Cause. There is a logic error in the client program.

Response. Make sure that the ODBC SQL environment and session are properly initialized and opened.

43085

Siebel Analytics Server disabled Performance Monitoring due to a bad registry.

Cause. Siebel Analytics Server disabled Performance Monitoring due to an inconsistent or corrupt registry. Registry corruption can occur after unclean server shut downs or by incorrectly modifying the registry manually.

Response. If Performance Monitoring is desired, shut down the server cleanly and restart it. Depending on the degree of corruption, the Siebel Analytics Server may be able to fix the registry. If the problem persists, contact Siebel Systems Technical Support. Under no circumstances should anyone but Siebel Systems Technical Support personnel attempt to manually fix the registry.

43086

Siebel Analytics Server disabled Performance Monitoring due to a Memory Mapped File creation error.

Cause. Siebel Analytics Server disabled Performance Monitoring due to a failure to create a Memory Mapped File.

Response. The problem is most likely due to unavailable operating system resources. Shut down the Siebel Analytics Server cleanly, reboot the operating system and restart the Siebel Analytics Server. If the problem persists, contact Siebel Systems Technical Support for assistance.

43087

Signalled server start.

Cause. The Siebel Analytics Server NT service has been signalled to start.

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

43088

Could not signal server start.

Cause. The Siebel Analytics Server NT service did not start properly.

Response. Contact Siebel Systems Technical Support for assistance.

43089

Stopping Siebel Analytics Server.

Cause. The Siebel Analytics Server received a shut down signal and is starting the shut down procedure.

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

43090

Server version (@1%s) is incompatible with the client. The client protocol version range is @2%d - @3%d. Server range is @4%d - @5%d.

Cause. The Siebel Analytics Server received a request from a client with an older or newer installation.

Response. The client installation upgraded/downgraded to match the server protocol version.

43091

ODBC procedure SetSessionValue internal error: The value type @1%s is not supported.

Cause. Wrong value type is used. It is not a supported type.

Response. The types allowed are: Integer, String, Float, Date, Time and DateTime.

43092

ODBC procedure SetSessionValue internal error: The value @1%s does not match the specified type.

Cause. Either the value or the value type is wrong.

Response. Make sure the value match the type and have correct format.

43093

An error occurred while processing the EXECUTE PHYSICAL statement.

Cause. An error occurred while processing the EXECUTE PHYSICAL statement.

Response. Examine the error message for any additional information. If that is not sufficient, then Contact Siebel Systems Technical Support for assistance.

43094

An error occurred while purging query cache via an ODBC function.

Cause. An error occurred while purging query cache through an ODBC function.

Response. Examine the error message for any additional information. If that is not sufficient, then. Contact Siebel Systems Technical Support for assistance.

43095

An error occurred while seeding query cache via ODBC function SASeedQuery.

Cause. An error occurred while seeding query cache through ODBC function SASeedQuery.

Response. Examine the error message for any additional information. If that is not sufficient, then Contact Siebel Systems Technical Support for assistance.

43096

The configuration on Cluster Controller @1%s specifies that TestMode is @2%s. However, the configuration on this Siebel Analytics Server specifies that TestMode is @3%s.

Cause. The cluster configuration files (NQClusterConfig.INI) on this Siebel Analytics Server and the specified Cluster Controller do not match.

Response. If the reported differences are not intentional, update the NQClusterConfig.INI files as necessary to synchronize their contents and restart the servers which reference the changed files.

43097

The configuration on this Siebel Analytics Server specifies a different client server port than Cluster Controller @1%ls.

Cause. The cluster configuration file (NQClusterConfig.INI) specifies a client server port and each Siebel Analytics Server must have the same client server port specified in their NQSConfig.INI file.

Response. Make the appropriate changes to NQSConfig.INI and restart the server.

43098

The format of the input string is wrong.

Cause. The input has error in terms of format.

Response. The allowed format is a semicolon separated list of: type variable=value.

43099

@1%s is a repository variable. You can only set the value of a session variable.

Cause. This is not allowed by design.

Response. Use a session variable or use a name that is different from all the session and repository variables.

43100

Log Viewer process reported error @1%d:@2%s.

Cause. The process that was created to run nQLogViewer reported an error.

Response. Contact Siebel Systems Technical Support for assistance. Include the reported error message.

43101

Unable to open file @1%s produced by Log Viewer, error @2%s.

Cause. The query log file that is produced by the nQLogViewer executable could not be opened.

Response. Check the permissions for the directories that are part of the filename. Correct any problems and try the nQLogViewer again.

43102

File access error @1%s from Log Viewer file @2%d:@3%s.

Cause. The specified error occurred when accessing the query log file that is produced by the nQLogViewer executable.

Response. Contact Siebel Systems Technical Support for assistance. Include the reported error message.

43103

Log Viewer process creation failed with error @1%d:@2%s.

Cause. An attempt to create the nQLogViewer process in order to extract the information from the query log failed.

Response. Contact Siebel Systems Technical Support for assistance. Include the reported error message.

43104

Could not restore the value of the variable '@1%s' to its default.

Cause. Invalid session variable.

Response. The variable specified must be in the repository, have a valid initial value and be associated with an initialization block.