sheafsu
asked on
In SQL Server 2008, I am receiving an error whenever I try to access any linked server based on a mdb or xls file
I am getting the error:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "LA_CITIZENS_CURRENT_ACCES
Msg 7303, Level 16, State 1, Procedure loadMonthlyMDBData, Line 38
Whenever I try to create a linked server based on an Office product like an Access database or Excel spreadsheet. It doesn't seem to matter whether the file is local or on the network. Linked files have been working fine for months until today. Had to restart SQL Server a couple of days ago, not sure if that makes a difference. Linked Servers connecting to other databases seem to be working fine
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "LA_CITIZENS_CURRENT_ACCES
Msg 7303, Level 16, State 1, Procedure loadMonthlyMDBData, Line 38
Whenever I try to create a linked server based on an Office product like an Access database or Excel spreadsheet. It doesn't seem to matter whether the file is local or on the network. Linked files have been working fine for months until today. Had to restart SQL Server a couple of days ago, not sure if that makes a difference. Linked Servers connecting to other databases seem to be working fine
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nmcdermaid,
I have doubts about excel/access file, I wonder if it not corrupted.
I have doubts about excel/access file, I wonder if it not corrupted.
Yes, thats why you need to copy it somewhere that has Excel or Access and try opening it there.
Sorry, thought you were the original poster.
Could be a permissions thingy, is there anything else different other than restarting the services e.g. updating Office ? Have shares or permissions changed especially for the SQL services owner (ie the account used to start and run those services) ? Is it only linked servers using Jet ?
mark_wills,
we are in blind so far that is why I suggested to check whether files are not corrupted and create linked server again so that if proper steps follows while creating the linked server again, permission error could be resolved.
we are in blind so far that is why I suggested to check whether files are not corrupted and create linked server again so that if proper steps follows while creating the linked server again, permission error could be resolved.
Yep, but is was working...
Thats why I wanted to know why he restarted the service originally - was it to change the logon account perhaps?
Why did you restart the SQL Service?