iJolly4
asked on
Linked Server problem
Hi,
I have created a linked server to an access database and this works fine on my local server. I created the same linked server on my production server and this worked fine when I am workking on the production server. If, however, within enterprise manager on my machine I register my production server and try to look at the linked server that I created on the production server I get the following message:
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: ]
If I try and run a query against the Linked server I get:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot open the file '\\gbrxxx\applications\app ln\Sales Compensation & Pipeline\SandRDetails\sale s.mdb'. It is already opened exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: ].
Any ideas???
Thanks
Iain
I have created a linked server to an access database and this works fine on my local server. I created the same linked server on my production server and this worked fine when I am workking on the production server. If, however, within enterprise manager on my machine I register my production server and try to look at the linked server that I created on the production server I get the following message:
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: ]
If I try and run a query against the Linked server I get:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot open the file '\\gbrxxx\applications\app
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: ].
Any ideas???
Thanks
Iain
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have solved the problem with the above link. The question is now closed.