SMTP Causes 100% CPU Usage

[Datanomics]

Last Friday I began a migration from a Win2K/Exc2003 server (DNEXOLD) to a Win2003/Exc2003 server (DNEXNEW). Note that both servers are FULLY updated with all MS updates & patches.

I had been using DNEXNEW for my own mailbox for the week without any issues. On Friday I moved over all other mailboxes in our organization. Everything was working wonderfully that eve, thru the weekend and this morning. For an hour. At 9:35am it suddenly came to a halt when the CPU Usage spiked to 100% and stopped processing mail.

I uninstalled McAfee GroupShield 6.0 after reading dozens of articles blaming it for similar issues (including several posts right here on Tek-Tips too!), alas, same problem. I also uninstalled McAfee VirusScan in desperation. No help.

I gave up and moved ALL the mailboxes back to the old server (DNEXOLD) just to get people functioning again.

I'm at a loss.....

Please understand I'm NOT an Exchange admin by any stretch so while I beg for your input and help please bear with me if I ask for clarification on some of your suggestions....

Thank you SO much for any help!!!

 

[Datanomics]

I found it's not the SMTP SERVICE, but rather the Default SMTP Virtual Server that's causing the problem. I changed the SMTP service to Manual, booted the server. Started the SMTP service - all was aok. THEN I started the Default SMTP Virtual Server - that's when all hell breaks loose. CPU Usage spikes to, and stays at, 100%. I can't even STOP the SMTP service OR Default SMTP Virtual Server after that... The only 'way out' is to reboot....

I also created a second Virtual Server & started it (while the Default was stopped after a reboot). It starts aok & the CPU Usage does NOT spike up, however I can't get any mail to pass thru it w/ my test account.... but that's a side issue.... (at least I think....)

Any help / suggestions would be very much appreciated!!

 

[Zelandakh]

Check the event log for 7034 errors. I wrote an article on it but darned if I can find it!!

Stop the SMTP service, delete the queue and badmail folders in the relevant Inetpub folder and restart the SMTP service and all should be well.

 

[Datanomics]

It WAS a third-party software, Policy Patrol, that caused the problem.

As I mentioned, I reverted all my users to the old server which had been stripped of ALL third-party software. Since there was no end in sight to the problem on the new server I started adding software back - one by one. Policy Patrol was first since it manages our signatures, disclaimers & forwarding. Around 2pm today the OLD server started exhibiting the SAME problem as the new server. There were only 2 common elements between the 2 servers - Exchange 2003 & Policy Patrol.

I contacted Policy Patrol and they had a fix for it which resolved the issue immediately however they were surprised that it happened on a server with NO other third party applications installed - not even virus protection. I know, a no-no, but desperate times.... They believe the database got corrupted and when I installed it on the old server and imported the database from the new server, along with the problem.... Why it was delayed in showing itself, in both cases, they don't know...

But thank you Zelandakh, for taking time to post a reply I really do appreciate it....! Had the problem not shown up on the old server I really was going to try your suggestions - but I was 'taking a day off' from troubleshooting - it was making me insane!!

--Lori

 

[Titleist]

Datanomics,

I had the exact same problems as you and Policy Patrol was the problem. I installed it for adding "Disclaimers" only and it ran fine for about 3 weeks then the smtp service spiked the cpu just as yours did. I called their tech support and was told that "It is running successfully on thousands of mail servers with no problems, it must be my Exchange setup." Needless to say, after uninstalling and gleefully cursing as I hit the "delete" key, I've had no issues since. I have since purchased "Exclaimer" and it's been running fine since day 1.

John

 

[Datanomics]

John,

Thanks for your post. Two things happened since my last post...

The 'fix' was only temporary. The database got corrupted AGAIN. So the solution this time was to uninstall the software completely, reinstall & recreate the database. I did it all. But.... this FRESH install and NEW database also caused the same problem just yesterday. I'm all for fixing problems properly, but after three failed attempts on something that brings our company to a grinding halt - sorry - you're problem, not mine. So as of noon yesterday, Policy Patrol is no more.

We used the software with absolutely no issues for 2yrs. It's a shame it suddenly went haywire. I have a feeling the problem is, or at least will become, more widespread than they realize....

Currently I have a disclaimer set up in everyone's Outlook and the users were informed that no changes are to be made unless they want their keyboards Crazy Glued to their hands. I intend to eventually look into other server-side packages and will definitely check out Exclaimer. Thanks for the suggestion!

-Lori