February 12, 2004 at 4:42 pm
Hello,
I am trying to set up a linked server in SQL Server 2000 Standard to an Access 2000 database called ‘MMTestEntry.mdb’. The Access databases uses Access security. The System.MDW file is located at C:\Program Files\Microsoft Office\Office\System.mdw.
My login to SQL Server is a Windows domain account, Valverde\cdunn. I have an account for Access called ‘cdunn’ with Membership in Admins, Default, and Users and no password.
The Access database, the SQL Server database, the System.MDW file, and the instance of SQL Server are all on the same machine, ‘SQL_Server’.
The ‘General’ properties of the Linked Server (from EM) are as follows:
Provider Name: Microsoft Jet 4.0 OLE DB Provider
Product Name: Access 2000
Data Source: E:\Databases\EdServices\MMTestEntry.mdb
Provider String: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\Databases\EdServices\MMTestEntry.mdb;Persist Security Info=False
On the ‘Security’ properties of the linked server, I tried a couple of different things, but I was not sure what to set up here.
In any case, when I tried to view the tables from the linked server in the EM, I got the following error message:
Error 7399: OLE DB provider Microsoft.Jet.OLEDB.4.0’ reported an error,
OLE EB error trace [OLE/DB Provider Microsoft.Jet.OLEDB.4.0’ IDBInitialize:: Initialize returned 0x80004005; ].
I’m not sure what this error means, and I was not able to quickly find anything when I searched Google.
What should I do to correctly configure this Linked Server?
Thanks for your help!
CSDunn
February 12, 2004 at 5:40 pm
February 13, 2004 at 12:31 pm
Thanks for the link to further details on how to set this up. As it turns out, security on the objects in the Access database were not being enforced. I was able to map to 'Admin' with a NULL password without having to point to the system.mdw file in the registry.
CSDunn
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply