XADM: Information Store Stops Responding When an IMAP4 User Logs on to an Orphaned Mailbox (252820)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q252820 SYMPTOMS
If an Internet Message Access Protocol, Version 4rev1 (IMAP4) user logs on to an orphaned mailbox that has a home server property that is undefined, the information store may stop responding and you may receive an access violation.
The stack trace is displayed as follows:
FramePtr RetAddr Param1 Param2 Param3 Function Name<BR/>
10f7fe14 006275af 11d53e18 11d53db8 00000000 STORE!SzDupSz+0xb<BR/>
10f7fe3c 00628731 00000000 11d53ddc 11d30f6e STORE!IMAPCON::EcServerHostFromServerDN+0x1e<BR/>
10f7fe58 006285a9 11d10150 00000000 00000002 STORE!IMAPCON::EcQueueReferralResponse+0x179<BR/>
10f7fee0 00501f71 11d10150 11d30f6e 00000012 STORE!IMAPCON::CbSubscribeUnsubscribe+0x258
CAUSE
When an IMAP4 user issues a subscribe command, the information store tries to make a copy of the home server property. If the home server property is null, the STRCPY function does not work.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the Microsoft
Download Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
| Modification Type: | Major | Last Reviewed: | 10/9/2003 |
|---|
| Keywords: | kbbug kbExchange550preSP4fix kbExchange550sp4Fix kbfix kbgraphxlinkcritical kbQFE KB252820 |
|---|
|
