Microsoft KB Archive/169681: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 62: | Line 62: | ||
== CAUSE == | == CAUSE == | ||
When processing messages destined for a domain associated with the | When processing messages destined for a domain associated with the "localhost" entry in the Imcroute.cfg, the IMS and Imcext.dll are unable to cooperate. | ||
</div> | </div> |
Latest revision as of 10:04, 21 July 2020
Article ID: 169681
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.0 Standard Edition
This article was previously published under Q169681
SYMPTOMS
When you use the Internet Mail Service (IMS) sample extension DLL, Imcext.dll, from the Back Office Resource Kit (BORK), the IMS may stop with an access violation, generating a Dr. Watson error message similar to the following:
(The address in the above example might be different from the one you see.)
CAUSE
When processing messages destined for a domain associated with the "localhost" entry in the Imcroute.cfg, the IMS and Imcext.dll are unable to cooperate.
WORKAROUND
To work around this problem:
- Do not use Imcext.dll.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
In addition to the Dr. Watson error, the Windows NT Server event log contains the following error message:
Event ID: 4037 Source: MSExchangeIMC Type: Error Category: Internal processing Description: An exception has occurred which was handled internally by the Internet Mail Service. This may have resulted in a message not being delivered. Code: 0xc0000005 Flags: 0x00000000 Address: 0x00402674
After this error occurs for the first time, each subsequent attempt to restart the service MSExchangeIMC will fail with exactly the same error messages.
Keywords: kbhotfixserver kbqfe kbbug kbfix KB169681