System resource exceeded on Windows 7

Question

I'm getting a "System resource exceeded" error on Windows 7 machines.  Trying to run a basic delete query.  This is very odd since the exact same query on the same database and table works fine on Windows XP.  Tests I have tried.

1. Windows 7 64-bit Enterprise, Access 2003, running this:

CodeProject.Connection.Execute "DELETE FROM tblPA_DATA_MultiPolicy_Umb_Limit WHERE State=2 AND RatingPlan=8"

fails with the "System resource exceeded" error

2. Windows 7 64-bit Enterprise, Access 2003, running this:

CodeProject.Connection.Execute "dqryCompleteJunk", , adCmdStoredProc

fails with the "System resource exceeded" error.  The saved query is just the same query put into a saved query to see if that worked.

3. Windows 7 64-bit Enterprise, Access 2003, running this:

"dqryCompleteJunk" directly from the Access saved query

fails with the "System resource exceeded" error. 

4. Windows 7 64-bit Enterprise, Access 2010, running this:

"dqryCompleteJunk" directly from the Access saved query

fails with the "System resource exceeded" error. 

5. Windows XP, Access 2003, runs fine with no error

The test database is very large as I purposely picked one of my larger backend files.  We have been getting this error in several databases all on Windows 7 and they all run fine on Windows XP.  The only way I can get it to run on Windows 7 is to add useless indexes to the table.  That is not a good solution as there are hundreds of tables and adding unneccessary indexes will cause import problems and potentially slow normal user use.  I am guessing there must be a setting I can tweak.  I tried changing the MaxLocksPerFile.  It started at 9,500 and is now 100,000.  This didn't help.  All the databases are in a stable state, no need for compact.  None of the table structure is off.  Any help would be great.

Ken

Answer 1

Hi Kennethj,

Thanks for posting in the MSDN Forum.

It's based on my experience that your issue can fixed via http://support.microsoft.com/default.aspx?scid=kb;EN-US;943509. Please try it and let me know the result.

Have a good day,

Tom

---

Tom Xu [MSFT]
MSDN Community Support | Feedback to us

Answer 2

That hotfix doesn't have anything for Windows 7, and my Jet version is higher than any mentioned.  I have 4.00.9756.0.  I did a search and can't find any newer hotfixes.

Answer 3

I have also ran this:

http://support.microsoft.com/kb/2553116

Which I already had.

I tried setting the MaxBufferSize to 50,000 in the registry under HKEY_LOCAL_MACHINE | Software | Wow6432Node | Microsoft | Jet|4.0|Jet 4.0 which didn't help.  I saw this mentioned here:

http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/86e59bc0-3524-45be-89d0-3528cfea842b/

and

http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/64650383-63e4-4891-82e4-6f8d568849f5/

I can't get my databases to run in compatablity mode or with admin rights.  My dbs are all on a network share and it yells at me about that.

Answer 4

Hi Ken,

With 32-bit applications, Out Of Memory issues can occur if you exhaust the 2 GB of virtual memory available to the process, or if memory becomes fragmented to the point that we don’t have a block of contiguous memory large enough to service the request.

It is possible that differences in the operating systems may consume slightly different amounts of virtual memory, so if your delete operations were near the 2 GB limit in Windows XP you may have exhausted the memory or don't have a contiguous block of memory in Windows 7.

The available options would be:

1. Add the indexes you mention to prevent loading so much data into memory

2. Use SQL Server instead of Access as your database engine

3. Use a 64 bit version of Access 2010 because a 64 bit application is able to work with up to 8TB of virtual memory

Regards,

Dennis

Answer 5

I guess we'll have to hope that option 1 works for us for all situations.  Fairly frustrating since it's broke in 2010 as well with the new ACE database engine.  Option 2 sounds great except we haven't had great performance out of anything we've used in SQL, now that is mostly from other less experienced devs and my boss has odd expectations out of SQL Server.  Option 3 is a no go.  We have hundreds of Win32 API calls and converting just the library database to 64 bit isn't going to work.  I tried that with the help of the Access team and we had to many sticking points where the code wouldn't compile, never mind if it worked on testing.

Answer 6

Kennethj,

Are you using a file browser dialogue window in your application before you get this error?  I strongly believe that that fragments the available memory under W7. 

See here for a question I raised in another thread (scroll down to my post on June 8th)

http://answers.microsoft.com/en-us/windows/forum/windows_7-files/file-save-dialogue-often-does-nothing-when-i-click/73c3ecc4-dc5e-47e8-861f-486e5342c714?page=2

and here:

http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/a543ecf0-fe4a-4476-be7e-296989c79acb

K

Answer 7

I'm not using anything before I try to run these queries.  Just open the database and run.

Answer 8

OK, it's just that I get a similar error just trying to open an MDB that I've browsed to , hence the question!

---

K