June 30, 2008 at 7:48 am
we also facing problem on our production. Openrowset is working for some day and then again it fails on the production. Once we restart db, then openrowset works fine and but again after for 4-5 days only
we are using openrowset for reaing 45-50 mb data.
Following are the erros we are getting from time to time
1. OLE DB provider "MSDASQL" for linked server "(null)" returned message "[Microsoft][ODBC Text Driver] Could not find installable ISAM.".
and some times
2. OLE DB provider "MSDASQL" for linked server "(null)" returned message "[Microsoft][ODBC Text Driver] System resource exceeded.".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "(null)".
June 30, 2008 at 9:28 am
The thing about resources being exceeded makes me wonder if you have some application not cleaning up its connections. Can you check for that?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 30, 2008 at 11:23 am
there is a sql job which runs in once every night which has openrowset.
July 1, 2008 at 9:32 am
I had this problem as well - allowing ole automation fixed it
sp_configure 'Ole Automation Procedures', 1;
GO
RECONFIGURE;
GO
September 23, 2008 at 10:40 am
I have this same problem but my Ole Automation Procedures is already set to 1.
Basically the query against the linked server works for a bit and then we start to see errors like the following:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "CONTRACTS" returned message "System resource exceeded.".
Msg 7320, Level 16, State 2, Line 1
The memory on the server doesn't seem to be near capacity and I'm having some trouble trying to figure this one out. Any help would be appreciated.
Best regards,
-D
November 25, 2009 at 2:18 pm
I have this problem too. My server is an SQL Server 2005 on a Dell server running Windows 2003 server R2 SP2. We have some night jobs using openrowsets to get data from excel sheets. They work for weeks, also for months, then suddently they start to give problems like mentioned above. This without changing anything on the configuration of the machine, without applying any fix to OS or DB Engine.
I'm going crazy for this, because it's also impossible to troubleshoot the error as there is no way to recreate the issue artificially. What I can ensure is that the machine doesn't run out of memory,all the night processes runs without overlapping toghether, just one job after the others.
Please le me know if someone has found a solution. Could it be a problem related to the Jet40 dll?
All the excel sheets are stored in the same drive where the SQL DB runs on the server machine.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply