I'm going to do my best to describe my environment and what the problem is, but feel free to ask for more information. I'm running Exchange 2003 Enterprise on Windows 2000 Server. I have Symantec Information Foundation Mail Security running on the server. I have another Exchange 2000 server that is remote in Dubai that is a member of my Exchange Administrative Group. Over the past 2 months or so, initially about once every 2 weeks and now once every week or so with no specific day, our Exchange server just stops delivering email and people running Outlook cannot access Exchange. If you get on the Exchange server, everything looks fine as far as services. Under System Manager everything looks fine except for emails backed up in the Queue for Local delivery and then delivery to the Exchange server in Dubai. I can still access email through OWA but it is very slow to open initially. Looking through Event Viewer, there are no obvious signs of what caused the issue. There are several repeating errors but I'm not sure which are symptoms and which would be the cause. A few examples follow:The following call : EcGetMime to the store failed. Error code : -2147467259. MDB : afac2536-7f67-4da5-821d-5dc744b00b78. FID : 1-43. MID : 1-5C69. File : . (This message repeats throughout the day, even when Exchange seems to be running ok)Exchange mailbox Server response timeout: Server: [TASMS01.TAS.local] User: [wlatham@tas.com]. Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded. (This message repeats typically during the time that Exchange is not working right, with several users that are using OWA on their iPhones or other devices. Don't typically see this error when Exchange seems to be running ok, making me think it's a symptom)The following call : EcGetMime to the store failed. Error code : 1290. MDB : bcea9511-7856-438e-91c1-418ba6d4b7cf. FID : 1-42. MID : 1-386B68. File : . Error 0x6bb deleting unused restricted view from folder 1-13CDC85A on database "First Storage Group\Mailbox Store (TASMS01)". Microsoft Exchange Information Store will try to delete the view again at the next maintenance interval.The process SAVFMSESp.exe was forcibly terminated. Reason: SAVFMSECtrl process failed to communicate with SAVFMSESp process.The following call : EcGetMime to the store failed. Error code : -1073151865. MDB : bcea9511-7856-438e-91c1-418ba6d4b7cf. FID : 1-3D. MID : 1-36C9A4. File : . This problem just occurred last night, so the following 4 errors or warnings came up at a specific time during the night, but were not repetitive like the ones above:Process STORE.EXE (PID=3072). DSAccess needs to close a connection to the Domain Controller TASDC01.TAS.local due to error 0x80040920. Process INETINFO.EXE (PID=816). DSAccess needs to close a connection to the Domain Controller TASDC01.TAS.local due to error 0x80040920. Process MAD.EXE (PID=2416). DSAccess needs to close a connection to the Domain Controller TASDC01.TAS.local due to error 0x80040920. Microsoft Exchange System Attendant reported an error '0x8007203a' in its DS Monitoring thread. That's the majority of the error messages that show up in the Application log from the point I last received email last night until the point I had to reboot Exchange this morning.This is starting to become a real frustrating issue and I'm trying my best to find the solution to keep it from happening again.

Check info: 1. When you said exchange server just stops delivering email, do you mean all internal and external mail flow? 2. The issued scope is all users, right? 3. Does the either one of the software below exist? When the issue reoccurred, please disable all 3rd party software on the exchange, including the Anti-Virus product, and monitor the results GroupShield Netshield 4. Does the exchange 2000 server patch the service pack 3? If not, please see KB 319682, which shows the same error as your first error event and same mail flow issue 5. As for the SAVFMSESp.exe error event, the process is actually the instance to scan messages and to respond to the corresponding VSAPI working thread in the store.exe. It didnt mean that the event is the problem (it can even a result of another issue); however I would like to suggest you take a look into this issue with Symantec. Heres one persons comment for this event after talking to Symantec 6. Error code 0x80040920 indicates Object does not exist, I assume theres related GC/DC connection issue in the environment. So, please run DCDiag /v /a and NetDiag /v to check the health of DC and connection to DC from the Client/Exchange which runs the ESM tool 7. Please check if _msdcs.tas.com zone is missing in the DNS server, same symptom will occur if so 8. Please also run Exchange Best Practices Analyzer (ExBPA) against the exchange server for a health check Resources: Working With the Exchange Best Practices Analyzer

I have this same issues as of lately. Let me add some conditions of my specifics... 2 X Exchange Servers on different sites linked via VPN. The server that stops, and that the smtp service doesnt respond to a restart on is a server 2000 box and exchange 2003 / 6.5 spk2. Same deal, randomly, as of late, the server locks. mailboxes on those indovidual servers maintain communicatoin, but smtp out and the sitelinks fail. restarting the server that the smtp servive locks on is the only trick, and after its like nothing happened. That box does have syamntec mail security, the latest release. That has been upgraded to that release, adn this problem started some time after. I am not convinced that is the issue, although prior to and during the failure, I recieve event log entires that mention something about SME not being able to scan files... what else can I tell you? Did you manage to fix this?