[AccessD] System Resources Exceeded

[James Button]

My understanding is that Access (well the older versions)  have some
specific-use memory pool limits ,
as in there is (or used to be) a 64MB limit in one of the memory pool
allocations.
also some 'SQL' can generate a requirement for relatively enormous temporary
storage space.
If the failure is not almost instantaneous, it may be worth running Task
Manager, and Resource Manager to see if you can identify any discernible
resource usage. 

JimB

-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of RANDALL R
ANTHONY via AccessD
Sent: Wednesday, May 8, 2019 7:01 PM
To: Jim Dettman <jimdettman at verizon.net>; 'Access Developers discussion and
problem solving' <accessd at databaseadvisors.com>
Cc: RANDALL R ANTHONY <RRANTHON at sentara.com>
Subject: Re: [AccessD] System Resources Exceeded

Yes, trust me this is a very small mdb with about 400K records in two tables.
Most I've seen it grow is about 350MB, after a C&R it goes back down to about
70MB.

-----Original Message-----
From: Jim Dettman <jimdettman at verizon.net> 
Sent: Wednesday, May 08, 2019 1:58 PM
To: RANDALL R ANTHONY <RRANTHON at sentara.com>; 'Access Developers discussion and
problem solving' <accessd at databaseadvisors.com>
Subject: RE: [AccessD] System Resources Exceeded

Notice: This email originated outside the Sentara Healthcare network. Beware of
links and attachments. Forward suspicious emails to spam_team at sentara.com.


 Have you actually checked?  Just saying that things can bloat quickly and
you can run into the 2GB limit easily.   Just double check so you can
scratch it off the list.

 If you have, great.  If not, you really want to check, especially when
someone gets the error.   Generally though if it hits the limit in a
multi-user situation, you'd have a lot of other problems at the same time.

Jim.

-----Original Message-----
From: RANDALL R ANTHONY [mailto:RRANTHON at sentara.com]
Sent: Wednesday, May 8, 2019 12:17 PM
To: Jim Dettman; 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] System Resources Exceeded

Thanks for the tips Jim, I'll check it out.  BTW, the DB is less than 200MB in
size.

-----Original Message-----
From: Jim Dettman <jimdettman at verizon.net>
Sent: Wednesday, May 08, 2019 11:05 AM
To: 'Access Developers discussion and problem solving'
<accessd at databaseadvisors.com>
Cc: RANDALL R ANTHONY <RRANTHON at sentara.com>
Subject: RE: [AccessD] System Resources Exceeded

Notice: This email originated outside the Sentara Healthcare network. Beware of
links and attachments. Forward suspicious emails to spam_team at sentara.com.


"out of system resources" is used for a number of things.

Disk space, hitting the lock limit, DB getting too big, running out of process
address space, etc.

I would:

1. Make sure the disk has free space.  
2. Check that the DB is not near the 2GB limit.
3. Add dbEngine.Setoption dbMaxLocksPerFile , 500000  to your startup code.

 See if that clears things up.   If not and your running 32bit office, then
you're probably running out of process address space.   Access is not large
address aware, so it's limited to 2GB of space.  Switching to 64bit would solve
the issue (but give you others possibly).

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of RANDALL
R ANTHONY via AccessD
Sent: Wednesday, May 8, 2019 9:51 AM
To: Access Developers discussion and problem solving
Cc: RANDALL R ANTHONY
Subject: [AccessD] System Resources Exceeded

Hello Group,
Just had a weird error pop-up on a relatively stable, small DB.  Win7 and
Win10 OSs, some with Access13, some with Access16 FE and BE.  Happened once
about two months ago, did a C&R and the problem went away.  However the customer
is reporting the issue is now occurring about 50% of the time.

Simple import routine, loads .txt file data (10 to 100 records) to a temp table,
then loads them to staging table and from there does a randomizer routine to
load to a table assigning X amount of records to any particular auditor.  This
process takes maybe a minute?  Two minutes?  Part of that latency is due to
extreme network distance from the user and the server farm, however that's never
been an issue.

Googling this the only suggested answer to the issue was provided by a Mark-NC,
see below.
I have seen this problem when running Access on a computer with multiple
processors. Try changing the Processor Affinity for the MSACCESS process in Task
Manager down to just one processor, and see if that improves performance.

Any help/clarification on this is greatly appreciated.  Thanks.


Randy Anthony, MCP
Database Administrator
4456 Corporation Lane, Ste. 200
Virgina Beach, VA 23462
757-252-8107

.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


.


.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com