mdn3000
asked on
Error 7399: OLE DB provider 'UNKNOWN' reported an error
We are in the process of migrating our SQL Server from version 7 to 2000 (also from NT Server to WS2003 on another domain/computer).
I added the ODBC data source and registered the linked server.
The strange thing is that while I can use openquery i QA to access the linked server, I get
Error 7399: OLE DB provider 'UNKNOWN' reported an error.
OLE DB error trace [OLE/DB Provider 'UNKNOWN' IDBSchemaRowset::GetRowset
in enterprise manager and DTS packages.
I have verified the ODBC connection and compared the registration with the existing (working) ones.
Does anybody have a clue to why this happens, and more importanly, how I can fix it?
I added the ODBC data source and registered the linked server.
The strange thing is that while I can use openquery i QA to access the linked server, I get
Error 7399: OLE DB provider 'UNKNOWN' reported an error.
OLE DB error trace [OLE/DB Provider 'UNKNOWN' IDBSchemaRowset::GetRowset
in enterprise manager and DTS packages.
I have verified the ODBC connection and compared the registration with the existing (working) ones.
Does anybody have a clue to why this happens, and more importanly, how I can fix it?
ASKER
Hi bragn,
thanks for the tip, but unfortunately that didn't do the trick.
The server I am trying to link is DB2.
I can access it using openquery in QA, but I get the error in enterprise manager/DTS
regards, MDN
thanks for the tip, but unfortunately that didn't do the trick.
The server I am trying to link is DB2.
I can access it using openquery in QA, but I get the error in enterprise manager/DTS
regards, MDN
I assume youve installed the latest service pack?
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
>>I can access it using openquery in QA, but I get the error in enterprise manager/DTS
Don't waste time working in the EM with linked servers. Setup the linked server, and use consistently OpenQuery, that gives best results & stability...
CHeers
Don't waste time working in the EM with linked servers. Setup the linked server, and use consistently OpenQuery, that gives best results & stability...
CHeers
ASKER
Hello all
I'm sorry for the delay, but I've been down with the flu the last week.
ShogunWade: Everything is up to date.
angelIII: Unfortunately OpenQuery only works in QA and _not_ in DTS (exact same code...), and we have alot of DTS packages...
MDN3000
I'm sorry for the delay, but I've been down with the flu the last week.
ShogunWade: Everything is up to date.
angelIII: Unfortunately OpenQuery only works in QA and _not_ in DTS (exact same code...), and we have alot of DTS packages...
MDN3000
Are you sure you have the drivers installed on the server?
ASKER
Thank you for your suggestions, but I found the problem/sollution!
Knowledge Base-artikel - 329332 deals with another error message, but the cause is the same.
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator (MS DTC) is not configured for network access. By default, the network access settings of MS DTC are disabled on new installations of SQL Server 2000 on computers running Windows Server 2003, Enterprise Edition. "
/MDN3000
Knowledge Base-artikel - 329332 deals with another error message, but the cause is the same.
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator (MS DTC) is not configured for network access. By default, the network access settings of MS DTC are disabled on new installations of SQL Server 2000 on computers running Windows Server 2003, Enterprise Edition. "
/MDN3000
cool. thx for the link to the solution.
PAQ + Refund
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Perhaps this will help you. Sounds like it.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;814398
Best regards,
bragn.