Our exchange server has been having some issues lately. Exchange randomly stopped working one morning a couple of weeks ago. I tried restarting a couple of services, but had no luck so I restarted the server, once it was back up and running everything was working smooth again. I looked through the event log and saw thousands of errors. No problems have occured since then, up until today it happened again. I rebooted, and all was well again. I went through the application event log, I could not get to the start of the failure since there was not enough log space, it maxed out at 60,000 events, but here is what I found from the earliest error to the last, before I rebooted: (these errors are identical to the previous failure) ERROR 1: http://i210.photobucket.com/albums/bb65/djfrost143/1.jpg WARNING 1: http://i210.photobucket.com/albums/bb65/djfrost143/2.jpg ERROR 2: http://i210.photobucket.com/albums/bb65/djfrost143/3.jpg WARNING 2: http://i210.photobucket.com/albums/bb65/djfrost143/4.jpg ERROR 3: http://i210.photobucket.com/albums/bb65/djfrost143/5.jpg What could be the cause of this? It seems to be that the exchange server is not able to connect to active directory?

What do you mean by "crashing"? Or by "stopped working"? All those messages indicate that your DC became nonresponsive. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "RKoba" wrote in message news:3d4d7807-2dff-4262-84d3-7ccef6fccf1c... Our exchange server has been having some issues lately. Exchange randomly stopped working one morning a couple of weeks ago. I tried restarting a couple of services, but had no luck so I restarted the server, once it was back up and running everything was working smooth again. I looked through the event log and saw thousands of errors. No problems have occured since then, up until today it happened again. I rebooted, and all was well again. I went through the application event log, I could not get to the start of the failure since there was not enough log space, it maxed out at 60,000 events, but here is what I found from the earliest error to the last, before I rebooted: (these errors are identical to the previous failure) ERROR 1: http://i210.photobucket.com/albums/bb65/djfrost143/1.jpg WARNING 1: http://i210.photobucket.com/albums/bb65/djfrost143/2.jpg ERROR 2: http://i210.photobucket.com/albums/bb65/djfrost143/3.jpg WARNING 2: http://i210.photobucket.com/albums/bb65/djfrost143/4.jpg ERROR 3: http://i210.photobucket.com/albums/bb65/djfrost143/5.jpg What could be the cause of this? It seems to be that the exchange server is not able to connect to active directory? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, I suggest you Exbpa to do a health check for your Exchange server. At the same time, please run “DCDiag /v /a” to check the health of DC. Please do the check and let us know the result. Thanks, Elvis

What do you mean by "crashing"? Or by "stopped working"? All those messages indicate that your DC became nonresponsive. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." I mean that none of the client computers could send or recieve email (through outlook). The server does not physically power off, I did have problems remoting into it but I have been able to restart the server physically with no troubles.

I will try this. Will either expba or dcdiag affect the end users in any way while I am running the utilities? Will it cause system performance to decrease or services to stop running? I can not afford to have the DC or Exchange servers down during the work day.

ExBPA will not stop any services or anything Can the clients connect to the server with outlook? Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

ExBPA will not stop any services or anything Can the clients connect to the server with outlook? Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog Ok and how about DCdiag? just want to make sure nothing bad will happen before I run them. And as of now, the clients can connect to the server through outlook. Outlook is sending and receiving email via our Exchange server. The issue has been that the clients (all of them) all of a sudden mid-day can not receive or send emails through outlook, the exchange server is having issues, the only way we have been able to fix it is a reboot of the server.

DCdiag can be used without any stops or impact on the systems Ok.. Do you got any 3rd part applications that might are having problems with memory leak?Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

DCDiag showed no issues and ExBPA showed only an issue with the page file, which I fixed. The Server locked up again on Monday. One thing I tried last time was I changed the exchange server to look to itself for the recipient update services (it is a DC). That was not the fix, since it just happened again. The same thing happened. All of a sudden, no one could send or recieve emails. I could not remote into the exchange server, nor could I log into it locally, it was locked up, or frozen. I could not even shut it down gracefully, I had to to a hard reset. I checked the event logs after the server was up and running again, and the same errors showed up. This time I noticed an error in the system log: System Error: 2019 The server was unable to allocate from the system nonpaged pool because the pool was empty. This is the error that occured right before the thousands of application errors. So there is definitly a memory leak right? Where do I go from here? How do I found hout what is causing the memory leak?