Exchange 2003 Sending old email messages after hard boot

The issue has happened twice now, and the owners of this server are extremely upset.

I began to troubleshoot this problem in February of this year and followed the steps located here http://support.microsoft.com/kb/906557 to delete the temp tables.  However after a hard boot last night the same emails were sent out once again.  I have today followed those instructions to delete the temp tables for the SMTP servernameGUID. I did notice a second SMTP instance listed in the mfcmapi that I cannot open it errors out with the following error when trying to view -

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function
File .\MAPIStoreFunctions.cpp
Line 48

So I cannot view the box to even see the temptables on this second SMTP server.  How do I resolve this issue so it does not happen again?

Hardware Details - Dell Poweredge Server Dual Xeon 1.86 4GB of RAM

Windows Small Business Server 2003 SP2 all updates

Exchange version 6.5.7638.1

Your help is greatly appreciated, Thank you in advance:)
benconnectedAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Alan HardistyConnect With a Mentor Co-OwnerCommented:
No - visit the link I posted (http://support.microsoft.com/kb/950757/ ), request the hotfix, download it, install it and job done.
0
 
benconnectedAuthor Commented:
Additional errors when trying to open the second SMTP instance in Mfcmapi.exe

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function CallOpenMsgStore( lpMAPISession, NULL, &sbEID, MDB_NO_DIALOG | MDB_NO_MAIL | MDB_TEMPORARY | MAPI_BEST_ACCESS, &lpMailboxMDB)
File .\MAPIStoreFunctions.cpp
Line 471

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function HrMailboxLogon( lpMAPISession, lpMDB, szServerDN, szMailboxDN, ulFlags, lppOtherUserMDB)
File .\MAPIStoreFunctions.cpp
Line 578

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function OpenOtherUsersMailbox( lpMAPISession, lpSourceMDB, m_lpszServerName, szMailboxDN, ulFlags, &lpNewMDB)
File .\MailboxTableDlg.cpp
Line 124

Then it doesn't open
0
 
Alan HardistyCo-OwnerCommented:
This is often referred to as the Greylisting Bug and can be resolved with a Hotfix from Microsoft:
http://www.experts-exchange.com/articles/Software/Server_Software/Email_Servers/Problems-sending-mail-to-one-or-more-external-domains.html
That should keep your owners happy : )
0
Problems using Powershell and Active Directory?

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

 
Alan HardistyCo-OwnerCommented:
Oops - wrong link - sorry:
http://support.microsoft.com/kb/950757/ 
0
 
benconnectedAuthor Commented:
Thank you Alanhardisty for your quick reply, I have actually run the Exchange SP2 update already prior to this issue.  Version: 6.5.7638.1 SP2  is the version I have currently installed. Do you have any other suggestions?
0
 
Alan HardistyCo-OwnerCommented:
If you have a read of the pre-requisites, you will find that SP2 was brought out prior to this hotfix, thus you won't have the patch and it will fix your problem - guaranteed.
"Prerequisites This hotfix requires Microsoft Exchange Server 2003 Service Pack 2 to be installed on the server because of file dependencies."
 
0
 
benconnectedAuthor Commented:
So if I understand you correctly, your recommending re-running  a fresh download of SP2 for Exchange Server 2003?
0
 
benconnectedAuthor Commented:
Thank you Alanhardisty for you help.  I contacted Microsoft spoke with a support rep for Exchange 2003 and he did confirm is was a file related to the SMTP service called aqueue.dll which was known to cause the issue described.   The file is located in %systemroot%\system32\inetsrv and the correct file version can be noted here http://support.microsoft.com/default.aspx?scid=kb;EN-US;934709. The file in question has not yet been released to the public so I cannot provide the download link, I assume it will be released in Server 2003 SP3.   He also directed me to clear the temptables noted here http://support.microsoft.com/kb/906557.  I had already done this the time prior to this and thought it was fixed.  The final issue which could have caused the problem was the Antivirus scanning exclusions which are noted here http://support.microsoft.com/kb/823166.  After completing all of these tasks he assured me that this should not occur again.  However time will only tell.  I did note your fix and saved the download link in my email for that fix should this happen again.  I thank you for your quick response and I am awarding you the points for the effort and it is possible your suggestion will be used in the very near future.  Hopefully this info can help someone else facing the same problem.
0
All Courses

From novice to tech pro — start learning today.