Importing Data from MS Access into SQL Serevr 2005 via Linked Server: User-Dependent failure

Question

I am operating an Express version of SQL Server 2005 on a Windows XP machine.
I have successfully setup a linked server to a remote Access (.mdb) database. With my user account (Windows authentication) I can retrieve and store data without any problem.
I have another user (apparently with same settings as my own account) that is always failing to get the data.
The Error message he gets is:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp" returned message "The Microsoft Jet database engine cannot open the file '\\DSITSO-NT0001\Exchange\Database5.mdb'.  It is already opened exclusively by another
user, or you need permission to view its data.".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp".
Here below the code used to set up the linked server (coming from the Code Snippets of SQL Server 2005).
EXEC sp_addlinkedserver
@server = N'TSU_Tmp',
@provider = N'Microsoft.Jet.OLEDB.4.0',
@srvproduct = N'OLE DB Provider for Jet',
@datasrc = N'\\DSITSO-NT0001\Exchange\Database5.mdb'
EXEC sp_addlinkedsrvlogin
@rmtsrvname = N'TSU_Tmp',
@useself = N'TRUE',
@locallogin = NULL,
@rmtuser = N'Admin',
@rmtpassword = NULL
We both run the script, actually is a Stored Procedure, (see code below) on the same XP machine where SQL Server is running.
EXEC('INSERT INTO tblFcst
(StartBUCode, StartBUType, StartBUSeq, StartTrz, StartCty,
EndBUCode, EndBUType, EndBUSeq, EndTrz, EndCty,
FcstCreationPeriod, FcstValidForPeriod, Fcst, FcstExternalReference,
IsProcessed, IsSolved)
SELECT TSU.BUCodeSend, TSU.BUTypeSend, TSU.BuaNoSend, Null AS StartTrz, Null AS StartCty,
TSU.BUCodeRcv, TSU.BUTypeRcv, TSU.BuaNoRcv, Null AS EndTrz, Null AS EndCty,
TSU.[Current week], TSU.[Forecast for week], TSU.[Volume trp m3], TSU.[TSU_ID (Don''t touch me)],
0 AS IsProcessed, 0 AS IsSolved
FROM TSU_Tmp...tbl_TSU_trpm3 AS TSU;')
PS: it is run using an 'EXEC(String)' format as at compile time of Store Procedure the Linked Server is not existing and otherwise compile would fail.
We tried it with different files, in different locations. It always wors for me, never for him...
The files were not used by anyone else. The folder(s) where they were stored are open to "Everyone".
So I concluded it should be something linked to the User... :) But I really do not know what, as said apparently we have exactely the same setup in our Login profiles.
Any idea or suggestion is welcome.
Thanks
Luca

Answer 1

Hi Luca Lentati,
According to your description and T-SQL statement, we need to verify if the download and install the Microsoft.Jet.OleDB.4.0 as a provider.
 If the 64bit SQL Server is running on the server,  The error, the Microsoft.Jet.OleDB.4.0 is not support, I reommend you download and install the Microsoft.ACE.OLEDB.12.0 as a provider.
The error 7303 message indicates that the linked server does not have correct login mapping. You can execute the sp_helplinkedsrvlogin stored procedure to set the login information correctly. Also, verify that you have specified the correct parameters
for the linked server configuration.
In addition, if the issue still exists, I recommend you copy the access file to local Server, and create linked server between them , check if it can run well. If yes, it means that
 the account which SQL server uses to run the service does not have read/write access to that file share.
There is an article about configuring a Linked Microsoft Access Server on SQL 2005 Server , you can review the following article.
http://www.aspfree.com/c/a/Microsoft-Access/Configuring-a-Linked-Microsoft-Access-Server-on-SQL-2005-Server/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support