Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 20423 | Error | QBB85 | -1006185L | "Unsupported raw device type %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20424 | Error | QBB86 | -1006186L | "Program error on raw device %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20425 | Error | QBB87 | -1006187L | "OS error was found on a lock (mutex,condvar,etc) Call: error = %2 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20426 | Error | QBB88 | -1006188L | "USEAGE error was found on a lock (mutex,condvar,etc) Call %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20427 | Error | QBB89 | -1006189L | "The condition variable was killed %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20428 | Error | QBB90 | -1006190L | "The semaphore variable was canceled %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20429 | Error | QBB91 | -1006191L | "Unknown error was found on a lock (mutex,condvar,etc) Call %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20430 | Error | QBB92 | -1006192L | "OS error was found on Thread Call: error = %2, %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20431 | Error | QBB93 | -1006193L | "Unknown error was found on Thread Call %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20432 | Error | QBB94 | -1006194L | "Could not get a thread %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20433 | Error | QBB95 | -1006195L | "OS error was found on hos_threadman Call: error = %2 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20434 | Error | QBB96 | -1006196L | "hos_threadman: the environment variable HOS_NUM_OF_CPUS does not exist %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20435 | Error | QBB97 | -1006197L | "Unknown error was found during hos_threadman Constructor %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20436 | Error | QBB98 | -1006198L | "Unknown error was found during hos_threadman Destructor %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20437 | Error | QBB99 | -1006199L | "Unknown error was found on hos_threadman Call %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20438 | Error | QBC00 | -1006200L | " and last packet was " | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20439 | Error | QBC01 | -1006201L | " and last packet was " | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20440 | Error | QBC02 | -1006202L | "Syntax error in conversion of string to DATETIME value." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20441 | Error | QBC03 | -1006203L | "Syntax error in conversion of string to DATE value." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20442 | Error | QBC04 | -1006204L | "Syntax error in conversion of string to TIME value." | No additional information available. Click here for a list of possible parameters and odbc states. |