Kbase P134410: Progress client crashes when executing FIND FIRST against Microsoft SQL Server 2005
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/08/2008 |
|
Status: Unverified
SYMPTOM(s):
Progress client crashes when executing FIND FIRST against Microsoft SQL Server 2005
Same behaviour occurs when using a FOR EACH statement
Running client directly on Windows 2000 Server
Using version 3.70.11.46 of Microsoft's SQL Server ODBC driver
Problem starts during SQLColAttribute function calls of the ODBC driver:
_edit 10dc-1124 ENTER SQLColAttribute
SQLHSTMT 017921B8
SQLSMALLINT 83
SQLSMALLINT 1011 <SQL_DESC_NAME>
SQLPOINTER 0x0012BE19
SQLSMALLINT 59
SQLSMALLINT * 0x0012BDA0
SQLPOINTER [Unknown attribute 1011]
_edit 10dc-1124 EXIT SQLColAttribute with return code -1 (SQL_ERROR)
SQLHSTMT 017921B8
SQLSMALLINT 83
SQLSMALLINT 1011 <SQL_DESC_NAME>
SQLPOINTER 0x0012BE19
SQLSMALLINT 59
SQLSMALLINT * 0x0012BDA0
SQLPOINTER [Unknown attribute 1011]
DIAG [S1002] [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index (0)
Several instances of the following errors are seen in the dataserv.lg file:
HH:MM:SS : SQLState: 01000
Native Error Code: 10093
Error Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionClose (closesocket()).
HH:MM:SS : SQLState: S1000
Native Error Code: 11
Error Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.
HH:MM:SS : SQLState: 01000
Native Error Code: 10093
Error Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()).
Problem does not occur when running code from a Windows XP client
FACT(s) (Environment):
OpenEdge 10.1x
Windows 2000
MS SQL 2005
CAUSE:
Version of the ODBC driver in use has not been certified for use with OpenEdge 10.1x and is therefore not supported. A list of certified ODBC drivers for use with MS SQL Server is available in the OpenEdge Product Availability Guide.
FIX:
Option #1
Install the latest MDAC version from Microsoft to obtain a newer SQL Server ODBC driver
Option #2
Use the OpenEdge 10.1x ODBC Wire Protocol driver for MS SQL Server