FIX: Incorrect Error Numbers Reported on Big Endian Client (254126)
The information in this article applies to:
This article was previously published under Q254126
BUG #: 57351 (SQLBUG_70)
SYMPTOMS
Any error that is reported to a big endian client is incorrect. For example, the normal 5701 error message that you receive during login returns as message 1159069696 instead. This may affect the application's error and message handling if the application performs certain processing for specific error numbers.
CAUSE
The bytes in the error message are not swapped before they are sent.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
MORE INFORMATION
Error numbers are 4 byte integer values. Using the 5701 error as an example, this is hex 0x00001645. In its non-byte-swapped format, this is hex 0x45160000, or decimal 1159069696. This 1159069696 value is the error that a client application would receive prior to applying this fix.
Sybase clients using Sybase CT-Lib are the only big endian client currently known to be able to connect to SQL Server 7.0.
| Modification Type: | Major | Last Reviewed: | 3/14/2006 |
|---|
| Keywords: | kbBug kbfix kbQFE KB254126 |
|---|
|