September 10, 2009 at 8:00 am
Hello,
We use a Microsoft SQL Server Linked server to query our ERP IBM UniData database in order to provide real-time shipment information for our UPS software. It has worked well until recently. We are now receiving the following errors when executing the query:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBM.UniOLEDB" for linked server "linkedservername" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "IBM.UniOLEDB" for linked server "linkedservername".
I am unaware of any changes that have occurred on our SQL server but there are other members of the IT staff that work on this server so I can't guarantee that statement. It appears to be the SQL server and not our ERP server because this same query through a linked server on a secondary SQL server is still working properly. I have taken the following steps in an attempt to fix the issue:
1. I stopped all SQL server services and restarted them.
2. I rebooted the SQL server.
3. I have reviewed the SQL Server configuration settings on both servers and they match.
4. I uninstalled and reinstalled the UniOLEDB driver then recreated the linked server.
The query we are executing:
SELECT ID, ORDER_NBR
FROM OPENQUERY(linkedservername, 'SELECT ID, ORDER_NBR FROM SHIPMENTS_NF') AS Rowset_1
Our environment settings are:
Microsoft Windows Server 2003 Std Edition R2
Microsoft SQL Server 2005 Std Edition SP3 9.00.4035.00
IBM UniData version 7.1.20
IBM System Builder (SB) version 5.4.2.4030
IBM UniOLEDB Driver 1.5.1.7211
Linked Server configuration settings:
Collation Compatible : False
Data Access : True
Rpc : True
Rpc Out : False
Use Remote Collation : True
Collation Name :
Connection Timeout : 0
Query Timeout : 0
Any suggestions would be appreciated.
Thanks,
Justin Lezon
September 10, 2009 at 8:11 am
If you have recreated everything exactly the same. I would check connectivity to the other server.
can you ping it from the server you are having trouble with. sometimes network glitches can cause linked servers to fail.
and from a security point of view, how have you set it up to authenticate against the other server.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 10, 2009 at 8:24 am
We are not using any server login mappings and connecting using a remote login. The linked sever connection test works (as well as pinging the server) it is only when we execute the query that we see this error. We are also able to connect using the same OLEDB driver with SSIS packages. We only have this issue with this linked server query.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply