Messages 978 through 997

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-978L Error 2645 WW047 "Directory for output file does not exist" The file cannot be written because the directory does not exist.

Click here for a list of possible parameters and odbc states.

-979L Error 2646 WW048 "Output file cannot be written" Unable to create or write an output file. The file may be locked or read-only.

Click here for a list of possible parameters and odbc states.

-980L Error 2647 WW049 "The URI '%1' is invalid" The specified URI is not valid.

Click here for a list of possible parameters and odbc states.

-981L Error 2648 WW050 "Unable to connect to the remote host specified by '%1'" A connection could not be initiated to the remote server.

Click here for a list of possible parameters and odbc states.

-982L Error 2649 WW051 "Connection timed out" The connection to the remote host timed out due to inactivity.

Click here for a list of possible parameters and odbc states.

-983L Error 2650 WW052 "HTTP request failed. Status code '%1'" The HTTP request returned a status code that indicated failure.

Click here for a list of possible parameters and odbc states.

-984L Error 2651 WW053 "Could not initialize the encryption DLL: '%1'" An attempt to initialize the encryption DLL failed.

Click here for a list of possible parameters and odbc states.

-985L Error 2845 08W20 "The database name 'utility_db' is reserved for the utility database." You are attempting to start a database with the name "utility_db". This name is reserved for the utility database.

Click here for a list of possible parameters and odbc states.

-986L Error 2653 WW055 "Invalid procedure type '%1'" A procedure or function was specified with an invalid type.

Click here for a list of possible parameters and odbc states.

-987L Error 2654 WW056 "Invalid procedure subtype '%1' for type '%2'" A procedure or function was specified with an invalid subtype for the given procedure type.

Click here for a list of possible parameters and odbc states.

-988L Error 2655 WW057 "Invalid response from the HTTP server" The response from the remote HTTP server was invalid. It may have been empty, malformed, missing header information, and so on.

Click here for a list of possible parameters and odbc states.

-989L Error 2656 WW058 "NAMESPACE attribute is not valid with procedure type '%1'" The NAMESPACE attribute is only applicable to procedures of type SOAP.

Click here for a list of possible parameters and odbc states.

-990L Error 2657 WW059 "The secure connection to the remote host failed: %1" The server was unable to initiate a secure connection with the remote host.

Click here for a list of possible parameters and odbc states.

-991L Error 2658 WW060 "Clause '%1' has invalid attribute '%2'" The attribute value specified on the procedure is not valid.

Click here for a list of possible parameters and odbc states.

-992L Error 2659 54W04 "The specified listener could not be registered" The specified listener could not be registered because the maximum number of listeners has been reached, the class name is already in use, or system resources are not available.

Click here for a list of possible parameters and odbc states.

-993L Error 2660 WL007 "LOAD TABLE not allowed on temporary table with ON COMMIT DELETE ROWS" The LOAD TABLE statement automatically commits at completion. If a temporary table being loaded was declared with ON COMMIT DELETE ROWS, the rows are discarded at completion.

Click here for a list of possible parameters and odbc states.

-994L Error 2661 42WAC "Too many arguments for function or procedure '%1'" You supplied an argument list that the database server cannot handle. This can happen if the argument list of the function or stored procedure is too long. Rebuilding the database with a larger page size could prevent this error.

Click here for a list of possible parameters and odbc states.

-995L Error 2662 WP016 "Warning detected when optimizing SELECT INTO is treated as an error" The SELECT ... INTO #TEMPTABLE statement cannot proceed if a warning is detected while optimizing the query. To fix the problem, test the query by removing the INTO clause, and resolve the reported warning.

Click here for a list of possible parameters and odbc states.

-996L Error 2663 WO024 "Specified local connection ID not found" There is no connection with the specified connection ID.

Click here for a list of possible parameters and odbc states.

-997L Error 2664 WO025 "Local connection ID does not refer to the current database" The specified connection ID is for a connection to a database other than the current database.

Click here for a list of possible parameters and odbc states.


Created June 15, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com