July 21, 2011 at 8:35 am
I've had this problem a number of times: every so often, I receive errors like this when trying to query an Excel xls file:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Could not find installable ISAM.".
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 "(null)".
What I've tried:
1. Ensuring the Excel file is not open. The OPENROWSET() statement is correctly configured, b/c the query works sometimes.
2. Bouncing the SQL service. This always fixes the problem, but doesn't tell me why it happens or when it will recur. And of course, it's a horrible "solution."
3. Checking MDAC. Used the MS consistency checker, and all looked OK.
4. Reading in the file saved in Excel XSLX 2007 format using the Microsoft.ACE.OLEDB.12.0' provider. This game me the following out-of-memory error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)" reported an error. The provider ran out of memory.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT * FROM [Sheet1$]" against OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)".
5. Tweaking the "MemToLeave" setting with the -g startup switch for the service, as described here: http://www.johnsansom.com/sql-server-memory-configuration-determining-memtoleave-settings/#axzz1SkRKB7Fz. I later ran the query given at his web page and returned the following values of Total avail mem, KB: 23800 and Max free size, Kb: 3444.
UPDATE: After a service restart, I immediately checked and got values of 216056 and 91840 for Total Available Memory, Kb and Max Free Size, Kb, respectively. Again, after a service restart I had no problem running the same OpenRowset() query. I started the service without the "-g" flag, using default values of MemToLeave. BOL (http://msdn.microsoft.com/en-us/library/ms190737%28v=SQL.90%29.aspx) says the default is 256 Mb.
This seems to suggest that there's insufficient RAM for running the OPENROWSET() query, consistent with the out-of-memory error trying to execute the query using the ACE.OLDEDB.12.0 provider for the XSLX file.
So.
I've seen enough blog postings to know that this is a pervasive problem with an often indeterminate solution.
1. Is this a problem caused by insufficient memory for Virtual Address Space?
2. If so, how do I find the cause of the problem?
3. If not, what can I do to fix this so it doesn't recur?
This is a significant problem for me, b/c I'm using OPENROWSET for importing Excel files into SQL. I am reluctant to use SSIS, b/c it's hitting a nail with a sledge hammer.
Any assistance would be welcome.
Rich
July 22, 2011 at 3:48 am
Use IMEX=1 in your extended properties for the driver.
N 56°04'39.16"
E 12°55'05.25"
July 22, 2011 at 6:19 am
SwePeso (7/22/2011)
Use IMEX=1 in your extended properties for the driver.
Thanks, but that's not the issue here.
The same query on the same Excel file works fine immediately after (and for some varying time after) a service restart.
Likewise, though I didn't include this in my o.p., the issue some have written about re: NTFS permissions in the user temp folder is not germane. I can run the same query on the same spreadsheet without problem after a service restart. So NTFS permissions aren't in play.
Anyone else have an idea?
Rich
May 19, 2013 at 12:27 pm
hi,
I had check following query it is working,
select * from OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=c:\Employee.xls;',
'SELECT * FROM [Sheet1$]')
If any problem ,Let me know.
Regards,
Dinesh
May 20, 2013 at 7:28 am
rmechaber (7/22/2011)
SwePeso (7/22/2011)
Use IMEX=1 in your extended properties for the driver.Thanks, but that's not the issue here.
The same query on the same Excel file works fine immediately after (and for some varying time after) a service restart.
Likewise, though I didn't include this in my o.p., the issue some have written about re: NTFS permissions in the user temp folder is not germane. I can run the same query on the same spreadsheet without problem after a service restart. So NTFS permissions aren't in play.
Anyone else have an idea?
Rich
I used to get that pretty often using Jet 4.0, and the only solution anyone ever had was to cycle the service. Recently switched to Ace, and hoping I don't also run into the other error now too. That was half the reason I switched.
May 26, 2013 at 9:48 am
Old thread, but in case someone finds this still relevant, I did finally discover the problem and solution.
If you Google memtoleave you will find the answer: SQL 2005 sets aside a separate address space apart from the buffer pool, used for things like OPENROWSET queries. If this becomes fragmented, you will be limited to using the largest contiguous chunk of memory left in it. The only way I'm aware of to reset this separate address space to the unfragmented value is to restart the SQL service, which is why bouncing the service "fixed" the problem.
The solution was to alter the service startup switch that allocates memtoleave memory to a larger value:
http://www.johnsansom.com/sql-server-memory-configuration-determining-memtoleave-settings/[/url]
For SQL 2005, the relevant explanation is here, look for the "-g" startup switch, and increase it as needed. This robs RAM from the buffer pool, so be careful with it.
The article on Kehayias' link, above, includes a query you can run to determine how much VAS is left available, and the largest contiguous chunk left. I put a version of this query on an Agent job and ran it hourly, dumping the results to a logging table, so I could track the pool's depletion.
I think 2008 fixed this, but in case anyone still runs 2005 I figured I'd post this fix.
Rich
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply