BUG: Pass Invalid LOGINREC * to dbopen() May GP Fault ServerLast reviewed: April 28, 1997Article ID: Q97718 |
The information in this article applies to:
NT: 193 (4.2) SYMPTOMSWhen calling the dbopen() function from a DB-Library client application, SQL Server generates a general protection fault (GP fault).
CAUSEPassing an invalid pointer as the first parameter to dbopen() may cause the SQL Server to general protection fault (GP fault). If the LOGINREC * points to a random location in memory, or if the LOGINREC * has been freed prior to the call to dbopen() by dbfreelogin(), garbage will be sent to the SQL Server when the client attempts to connect. Although SQL Server may simply reject the login attempt, certain combinations of bad data can cause the server to GP fault.
WORKAROUNDEnsure that all DB-Library code passes a valid LOGINREC * as the first parameter to dbopen().
STATUSMicrosoft has confirmed this to be a problem in version 4.2 of SQL Server. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: dblib db_library trap
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |