XCON: An Access Violation Occurs in the IISAdmin Service When You Shut Down the Exchange Services Under Stress

Article translations Article translations
Article ID: 317121 - View products that this article applies to.
This article was previously published under Q317121
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

On an Exchange 2000 Server computer, an access violation may occur in the IISAdmin service when you try to shut down the Exchange services under a heavy load.

If the correct symbols are installed on the computer, a DrWatson.log file or the corresponding User.dmp file may contain the following call stack:
ChildEBP RetAddr
2171fee4 5e7a1e22 pop3svc!POP3_SERVER_INSTANCE__OnDisconnect+0x9 
2171fefc 5e7a1cc5 IISIF!IFCONN__DisconnectClient+0x41 
2171ff10 5e7a1c0c IISIF!IFCONN__HrDisconnectNoRelease+0xf4
2171ff1c 5e7a1dae IISIF!IFCONN__HrDisconnect+0xc
2171ff34 5e7a1689 IISIF!OnQueuedDisconnection+0x76
2171ff4c 686287ab IISIF!NetIfCompletionRoutine+0x30
2171ff80 68628aa8 LSATQ!AtqpProcessContext+0x262
2171ffb4 77e8758a LSATQ!AtqPoolThread+0x1a8 
2171ffec 00000000 KERNEL32!BaseThreadStart+0x52
					

CAUSE

This problem occurs because of there is not enough thread safety around the configuration objects.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: Post Office Protocol version 3 (POP3)

Collapse this tableExpand this table
File nameVersion
Pop3fe.dll6.0.5770.46
Imap4fe.dll6.0.5770.46
Febecfg.dll6.0.5770.46
Pop3svc.dll6.0.5770.46
Imap4svc.dll6.0.5770.46
Iisproto.dll6.0.5770.46

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Properties

Article ID: 317121 - Last Review: October 24, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB317121

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com