Kbase P124066: MS SQL Server Linked Servers fails with error when using Shared Network installation of Progress / O
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/13/2010 |
|
Status: Verified
SYMPTOM(s):
MS SQL Server Linked Servers fails with error when using Shared Network installation of Progress / OpenEdge
MS SQL Server 2000 Linked Servers fails with error when using Shared Network installation of Progress / OpenEdge
Connection fails with error when selecting Tables or Views
Error 7399: OLE DB provider 'DataDirect.ClosedIntegratorBase' reported an error.
OLE DB error trace [OLE/DB Provider 'DataDirect.ClosedIntegratorBase' IDBInitialize::Initialize returned 0x80004005
Standard connections to Progress database via ODBC driver work as expected
MS SQL Server can hang when testing the Linked Server
Hang occurs when executing internal stored procedure
ODBC trace log contains the following information:
SQL Server Ente 3a8-4ce0 ENTER SQLExecDirectW
HSTMT 01601E08
WCHAR * 0x000B2A60 [ -3] "exec master..sp_tables_ex N'<ODBC DSN Name>' , null, null, null, '''TABLE'''\ 0"
SDWORD -3
FACT(s) (Environment):
Using Linked Servers feature of MS SQL Server
Progress has been installed via Netsetup
Linked Server functions correctly when Progress is installed locally on the same machine as MS SQL Server
Progress 9.1x
OpenEdge 10.x
Windows
MS SQL 2000
CAUSE:
Progress Technical Support was unable to create an environment where MS SQL Server Linked Servers worked with a Shared Network Installation of Progress / OpenEdge. However, given that the Progress / OpenEdge ODBC driver installed with the Shared Network Installation worked correctly with standard SQL queries and tools, the problem would appear to lay with MS SQL Server Linked Server functionality.
FIX:
Install Progress / OpenEdge products required locally on the same server as MS SQL Server rather than using the Shared Network Installation option