Create a linked server into MS Access which reside in the remote Server.

Question

Create a linked server into MS Access which reside in the remote Server.

zozilany

SSC Veteran

Points: 226
More actions
August 15, 2011 at 5:39 am

#242143

I am trying to create a Linked Server to an MS Access database on a computer other than where SQL Server resides. I can create the linked server if the path is local (same computer as where SQL Server resides) but when I try to create a linked server to a copy of the same MS Access database but on another computer using a remote server path, it won't work, It says, Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "<linked server name>". (Microsoft SQL Server, Error: 7303)
Is it necessary to specify a Local Login and Remote User in the 'Local server login to remote server login mappings' section? How to do the login mappings and what kind of permission need to have the SQL Server user account?
Your help is appreciated.
Regards, Ravi

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323504 More actions · Answer 1

zozilany (8/15/2011)
I am trying to create a Linked Server to an MS Access database on a computer other than where SQL Server resides. I can create the linked server if the path is local (same computer as where SQL Server resides) but when I try to create a linked server to a copy of the same MS Access database but on another computer using a remote server path, it won't work, It says, Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "<linked server name>". (Microsoft SQL Server, Error: 7303)
Is it necessary to specify a Local Login and Remote User in the 'Local server login to remote server login mappings' section? How to do the login mappings and what kind of permission need to have the SQL Server user account?
Your help is appreciated.
Regards, Ravi

Ravi I'm pretty sure the issue is network permissions.

the account which SQL server uses to run the service will need read/write access to that file share (\\UNC_Path\SharedFolder\); that's why when a local copy is set up it works (because these accounds have access tot he local disks) but not when you try to use a remote file...you end up getting error 5 , which is permission denied.

I believe if you have set up a proxy account, if you are sysadmin, it will use that account no matter what, and that account might not be the same as the one that runs the service.

the account in services:

so you might need to make sure the proxy account has permissions to the file share where the access database exists.

once raw access is available, then SQL uses that linked server, and it starts passing the remote username and remote passwords if you are using them.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

zozilany SSC Veteran Points: 226 More actions · Answer 2

Hi Lowel,

Thanks for your reply.

I have tried the first option by giving myself (myaccount) as a proxy, also i have ensure the remote file have been given access to my account.

But still i have not able to success.

It would be nice, if you have any steps i need to follow in setting up the linked server properties. (Where i need to setup my account to access the remote file.) So that i will try that option.

Your help is appreciated.

Regards, Ravi

MyDoggieJessie SSC-Forever Points: 44484 More actions · Answer 3

Try setting up a system DSN driver first through ODBC on the server itself at the OS level, then create the linked server using the DSN from what you just created.

When you create the Linked Server, give it the same name as the ODBC one you created, in the Provider combo select the OLEDB Provider for ODBC drivers, The data source should also be the same name as the ODBC one you created, then in the Provider string, fill in the driver info...it's usually something like :: "Driver={Microsoft.Jet.OLEDB.4.0};SourceDB=YourPathToTheAccessDB"

Aiding to what Lowell said, make sure your proxy account has access to the folder where the file resides as well. In most situations like this, it ends up being security-related or a mixup in how the Domain/System Administrators set up the share. You can test this easily using xp_cmdshell (if you have that enabled on your SQL server instance) if you can access the file/share via this tool you'll know the permissions are fine (as this tool uses the proxy account)

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience