Solved

Error synchronizing with Exchange 2003 - "There are not enough system resources available for this operation"

Posted on 2006-11-29
6
6,793 Views
Last Modified: 2011-07-13
Here's my situation:

We've got an SBS 2003 R2 server running Exchange 2003.  When I hit Send/Receive in Outlook, I get an error on the Exchange task:
'Microsoft Exchange Server' reported error (0x8004010E) : 'There are not enough system resources available for this operation.'

I've modified the boot.ini to add /USERVA=3030, and I've tried it with and without /3Gb (currently the /3GB isn't there).
I've also added the registry entries to increase the database size.
  I set the private storage box size to 15Gb with the buffer set at 5%.
  I set the public storage box size to 5Gb with the buffer set at 5%.
  My user's individual box is set to 2GB with it currently sitting at 325MB.
I checked the free system page table entries and virtual bytes for store.exe in the performance monitor.  Here's where they sit at this moment:
  Free System Page Table Entries:  228832
  Virtual Bytes (store.exe):  1,325,076,480

Any thoughts?  Thanks in advance!
Chris
0
Comment
Question by:CompTechNS
  • 3
6 Comments
 
LVL 1

Author Comment

by:CompTechNS
ID: 18041124
Here's what we have for hardware resources:

2 - Dual Core Xeon 2.67GHz Processors
2 GB Memory
System drive is 80GB (57GB free)
0
 
LVL 1

Author Comment

by:CompTechNS
ID: 18042874
Update:

I ran Windows Update on the server.  There was nothing Exchange related but there were a couple non-critical updates.  I also ran Office Update on my PC and it was basically the same deal, just some minor security updates and a small "Office Update".  

After rebooting the server I was able to synchronize with no problem.  I had rebooted the server prior to now with no success so I'm not sure what changed here unless there was something in one of the updates...

I'm going to let this thread go for at least a few hours before I deem it resolved just to make sure this isn't an issue that is going to resurface after a period of time.
0
 
LVL 1

Author Comment

by:CompTechNS
ID: 18049233
Apaprently the updates were all I needed.  As of now we're still in good shape...

This thread can be closed.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 18056166
It's actually the reboot that probably fixed this.  Often when there's been an update on the server and it hadn't rebooted yet, you'll get this kind of error.

Jeff
TechSoEasy
0
 

Accepted Solution

by:
AnnieMod earned 0 total points
ID: 19388371
PAQed with points refunded (500)

AnnieMod
Cleanup Admin
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
If you are a user of the discontinued Microsoft Office Accounting 2008 (MSOA) and have to move to a new computer running Windows 8, you will be unhappy to discover that it won't install.  In particular, Microsoft SQL Server 2005 Express Edition (SSE…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question