November 18, 2007 at 9:48 pm
i have an SQL job where lot of queries are executed as steps.
Last step performs openrowset query and that fails with error
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)". [SQLSTATE 42000] (Error 7303) OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error". [SQLSTATE 01000] (Error 7412). The step failed.
I restart the SQL Server, and the same openrowset works fine.
This happens every time. Can anyone please tell me what might be wrong ??
Thanks in advance.
November 20, 2007 at 3:05 am
I'm looking at the "for linked server "(NULL)"" and I'm thinking that it doesn't really seem right to me.
November 20, 2007 at 10:07 pm
select * from OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;DATABASE=\\10.114.0.50\shared\tar\PAT_INFO_OUTPUT.xls', 'Select * from TBL_CIC_INFO_OUTPUT')
this is the command. and that works fine if the server is restarted. but, restarting it daily isnt the solution that can work. Please give me some idea.
November 22, 2007 at 12:42 am
Hmm... your error isn't really related to a "linked server" as the term usually applies. You're dynamically creating a connection to an excel spreadsheet on a UNC...
There's something about doing it "that way" that's giving me a bit of the heeby jeebies but there are some things you could take a look at starting with:
(1) \\10.114.0.50, is this server a MS server or other O/S? What type of authentication is being used?
(2) What type of account is your SQL server configured to run under, local, domain?
(3) Same for SQL Agent?
(4) Does the job ever run successfully or only when you execute the job manually?
November 22, 2007 at 12:54 am
Joe Clifford (11/22/2007)
Hmm... your error isn't really related to a "linked server" as the term usually applies. You're dynamically creating a connection to an excel spreadsheet on a UNC...There's something about doing it "that way" that's giving me a bit of the heeby jeebies but there are some things you could take a look at starting with:
(1) \\10.114.0.50, is this server a MS server or other O/S? What type of authentication is being used?
(2) What type of account is your SQL server configured to run under, local, domain?
(3) Same for SQL Agent?
(4) Does the job every run successfully or only when you execute the job manually?
The error is exactly what I pointed out: "for linked server "(NULL)""
,,,,,,,,,,,,,the connection string is invalid.
AS Old Hand points out, there are a number of reasons why that would be.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply