Modified the ESE buffer size to several different values, ending with the max 307200

Increased and decreased the Pagefile from default to various sizes up to 12G split on 2 drives

The specs on the server are high-end : Dual P4 3G Intels, 4G RAM, Windows 2003 Enterprise OS (all current Windows Updates except Server 2003 SP1), Exchange 2003 Enterprise SP1. This server is a member server and not a DC in the domain.

I've been beating my head against the wall for nearly 2 weeks now ... can anyone else offer any suggestions before I call this one into Microsoft? Do I *really* need to worry about this message? One of the first options in the KB article instructs how to turn off the check, but I didn't put 4G of RAM into this box for it to sit and rot ... and I'd rather not ignore this for it to come back and bite me down the road.

Hi
Maybe test your motherboard and memory (sandra sisoft) "http://www.3bsoftware.com/downloads/sandra.html"
If you use only 1 Giga Ram (for exemple) Do you have the same error ?
What is your Server ? Do you have checked with Tool of manufactury your system ?

I will give those tool a shot. The system is a brand spanking new Dell 2850 raack server. I've run the Dell diags on the server with nothing out of the ordinary there. I've just now begun physical troubleshooting and testing it now with only 1G in the server now after reversing all of the KB options I've done already. My next step was to run the linux memtest from CD that I have here as well but I'll try Sandra first since that hits motherboard as well. This will be a real comedy fest if it turns out to be hardware ...

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Actually it looks like reseating the RAM fixed the issue. Since you pointed me to the hardware side I'll award you the points because it was certainly related. After I pulled out all of the RAM and seated a single 1G stick and booted it, no errors in event log. I shut the server down again, placed in the second stick to get to 2G, booted and no errors in event log. Also did the same for the third and fourth sticks, low and behold ... no errors! Weird, certainly! And for anyone else having this error, I know that everyone has been pointing to article 81537. I also highly suggest looking at this link as well as it goes over the step-by-step in the planning phase.

Featured Post

Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...

In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Recipients >> Sha…

To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Servers >> Certificates…