Kbase P184664: Access violation in ODBC driver after installing OpenEdge 10.2B03
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/04/2011 |
|
Status: Unverified
SYMPTOM(s):
Access violation in ODBC driver after installing OpenEdge 10.2B03
ODBC client crashes when querying table information after upgrading to OpenEdge 10.2B03
Access violation in ODBC driver when querying table information in WinSQL Catalog
Access violation in ODBC driver when attempting to build a multi-table query in Crystal Reports
Access violation at address 28678404 in module 'pgoe1024.dll'. Read of address 00000000.
Stack trace extracted from ADPlus for crash of CRW32.EXE reads:
pgoe1024!ProStatement::~ProStatement+0x4c64
pgoe1024!RowId::~RowId+0x29e4
ODBC trace log shows the last function call is SQLForeignKeysW
Entry for SQLForeignKeysW from ODBC trace log when failing (PGOE1024.DLL):
Winsql 12b4-8bc ENTER SQLForeignKeysW
HSTMT 00FA26C8
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00FA1970 [ -3] "PU"
SWORD -3
WCHAR * 0x00FA2D68 [ -3] "Bene"
SWORD -3
Entry for SQLForeignKeysW from ODBC trace log when working (PGOE1023.DLL):
Winsql 15b0-16bc ENTER SQLForeignKeysW
HSTMT 00FA26E8
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00FA1978 [ -3] "PU"
SWORD -3
WCHAR * 0x00FA2DC0 [ -3] "Bene"
SWORD -3
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
Winsql 15b0-16bc EXIT SQLForeignKeysW with return code 0 (SQL_SUCCESS)
HSTMT 00FA26E8
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00FA1978 [ -3] "PU"
SWORD -3
WCHAR * 0x00FA2DC0 [ -3] "Bene"
SWORD -3
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
WCHAR * 0x00000000
SWORD 0
Problem does not occur when using version 5.30.00.109 of the Progress OpenEdge 10.2B Driver (PGOE1023.DLL)
Problem does not affect existing reports
FACT(s) (Environment):
Service Pack 3 for OpenEdge 10.2B installed version 6.00.00.168 of the Progress OpenEdge 10.2B Driver (PGOE1024.DLL)
Version 6.00.00.168 of the Progress OpenEdge 10.2B Driver (PGOE1024.DLL) is installed as the default ODBC driver in 10.2B03
Registry entries point to PGOE1024.DLL once 10.2B03 is installed
Version 5.30.00.109 of the Progress OpenEdge 10.2B Driver (PGOE1023.DLL) is still present in DLC\bin
OpenEdge 10.2B
Windows
Progress OpenEdge 10.2B driver
CAUSE:
Bug# DD00060270
FIX:
Rollback to version 5.30.00.109 of the Progress OpenEdge 10.2B Driver (PGOE1023.DLL) that is still present in DLC\bin.
Backup the Registry before making changes.
Option #1 - Change Registry so any new ODBC DSNs will use the version 5.30.00.109 ODBC driver
Locate the following Registry keys:
32-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Progress OpenEdge 10.2B Driver
64-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Progress OpenEdge 10.2B Driver
Modify the Driver and Setup entries and change PGOE1024.DLL to PGOE1023.DLL.
Option #2 - Modify existing ODBC DSNs
a) Delete and recreate existing ODBC DSNs after performing the steps in option #1.
OR
b) Locate ODBC DSN in
32-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<Name of ODBC DSN>
64-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\<Name of ODBC DSN>
Modify the Driver entry and change PGOE1024.DLL to PGOE1023.DLL.