jczander
asked on
SQL 2005 Linked Server to Progress 9.1E
We have a sql server that connects to Progress via linked server. Suddenly, we are no longer able to connect and get the following error:
"Specified driver could not be loaded due to system error 126 (DATADIRECT 4.10 32-BIT Progress SQL92 v9.1E).".
We have other servers that connect to this Progress database and we have no problems. Users can connect to the database via access from their desktops. It is just this one box.
"Specified driver could not be loaded due to system error 126 (DATADIRECT 4.10 32-BIT Progress SQL92 v9.1E).".
We have other servers that connect to this Progress database and we have no problems. Users can connect to the database via access from their desktops. It is just this one box.
lcohan
I suggest you plan and restart that box and I'm affraid this may be the only way to clear the error. Before that you could try set a new ODBC driver and linked server to the same postgres database and using exactly the same credentials/configs and see if that one is working.
ASKER
Restarting did nothing. We reinstalled Progress as well. The SQL server runs fine. Progress is running fine. We can connect through the odbc from other machines.
It is either a sql driver issue or a data direct issue.
It is either a sql driver issue or a data direct issue.
I don't think you needed to re-install postgress but at the most DATADIRECT driver on the SQL Server box from where you try to connect but before that - did you tried to "Test Connection" on the existing ODBC driver after SQL Box reboot?
ASKER
That works.
If that works on the same box as SQL server in my opinion there's no way to not be able connect from SQL linked server on the same box.
As the following will do no harm caould you try add a new linked server on that SQL server and select "Microsoft OLEDB for ODBC data providers" under the "Provider:" then run a simple query in SQL like the one below to query data from a small PG table?
SELECT * FROM OPENQUERY(PGLinked_server_
As the following will do no harm caould you try add a new linked server on that SQL server and select "Microsoft OLEDB for ODBC data providers" under the "Provider:" then run a simple query in SQL like the one below to query data from a small PG table?
SELECT * FROM OPENQUERY(PGLinked_server_
ASKER
I tried that and get the same error. My guess is the sql driver is corrupted in some way.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
The SQL server was corrupted. Once it was restored to another box, the problem was resolved.