CompTechNS
asked on
Error synchronizing with Exchange 2003 - "There are not enough system resources available for this operation"
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
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
ASKER
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.
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.
ASKER
Apaprently the updates were all I needed. As of now we're still in good shape...
This thread can be closed.
This thread can be closed.
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
Jeff
TechSoEasy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
2 - Dual Core Xeon 2.67GHz Processors
2 GB Memory
System drive is 80GB (57GB free)