May 30, 2005 at 6:34 am
We are linking a SQL2000 server to an Access DB. We have set this up no problem on a normal SQL2K server - works like a treat.
However, when we attempted to set this up with the same NT login on a SQL 2K Cluster any attempt to connect to the AccessDB fails with:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: ].
Does anyone know of any special problems with Linked Servers under SQL Clusters?
May 31, 2005 at 10:48 am
Are you using the virtual server/instance name when accessing the cluster as opposed to the physical node?
Also, the ODBC DSN settings need to be identically created on each physical node of the cluster a,b.
Regards, Melissa
May 31, 2005 at 12:28 pm
It may also depend on where the Access database actually sits. Is it on a shared resource of the cluster where all nodes would be able to use it, or is it on another server where all nodes are mapped to it? Like Melissa said, all nodes have to be identical.
Linda
June 1, 2005 at 2:15 am
Thanks for replies. I guess you didn't correctly understood me. This mdb file is outside of the cluster and the cluster nodes need to connect to this file through linked server. We don't need connect to cluster
The NT login on which the cluster runs has all permissions on that shared folder where that mdf file resides.
This linked server works only when we register these cluster servers with SQL login account on EM, or Execute queries from QA to which we connect with sql login too.
The problem is that NT login doesn't reach the destination not like SQL with sa rights
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply