Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Strategist
Starting Member
1 Post |
 Posted - 2004-05-28 : 05:57:12
|
| I have run into a problem with linked servers, and was wondering if anyone else knows the answer. I have set up a linked server on SQL Server 2000 in which the link (i.e. the path) is to another server - where there is an Access Database. When I open Enterprise Server on my computer I can see the linked server, but if I try to browse the tables I get the error below:Error 7399: OLE DB provider 'Microsoft.JET.OLEDB.4.0' reported an errorOLE DB error trace[OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'IDBInitialize::Initalize returned 0x80004005: ]Intriguingly if I log into the SQL Server computer using Terminal Services Client, using my windows password and username, and open Enterprise Server there, then I get no problems and am able to see all the tables. Our DBA reckons that it may be to do with where the JET Engine is running - local to my machine when I get the error, and local to SQL Server when I run through Terminal Services Client.Anyone got any ideas? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-28 : 12:41:04
|
| Try installing the latest MDAC.Tara |
 |
|
|
jamie
Aged Yak Warrior
542 Posts |
Posted - 2004-06-21 : 10:36:26
|
| hi, I am having the same problem, I havetried installing mdac 2.7, also have given permissions tothe Temp folder but still get the same error.any other suggestions ? |
|
|
|
jamie
Aged Yak Warrior
542 Posts |
Posted - 2004-06-21 : 10:48:11
|
| For more info. when trying to run SELECT * FROM OPENQUERY, I receive the following error :Server: Msg 7399, Level 16, State 1, Line 1OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. [OLE/DB provider returned message: The Microsoft Jet database engine cannot open the file '\\SERVER1\data.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: ]. |
|
|
|
adamtuliper
Starting Member
1 Post |
Posted - 2004-06-29 : 09:48:48
|
| use sysinternals filemon to see where permissions are failing. My guess is you need permissions on the folder the mdb is in. When you open an mdb, a lock file (.ldb I believe) is created, so permissions on the folder will require that user has the ability to create new files in the folder your mdb is in, which is different than the temp folder. |
|
|
|
|
|
|
|
|
SQL 2000 Linked Server to Access Db