XADM: Information Store Receives Access Violation on LAST or NEXT Command (269076)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q269076 SYMPTOMS
When a Network News Transfer Protocol (NNTP) client logs on to an Exchange Server computer that is configured as an NNTP server and the client issues a "LAST" or "NEXT" command, the information store service may stop unexpectedly because an access violation occurs. The Dr.Watson log or the User.dmp file contains a stack dump that is similar to the following:
FramePtr RetAddr Param1 Param2 Param3 Function Name
1143f984 78021646 1143f99c 011315b7 1143fdf0 0x7801031c
1143f9bc 006172b5 1143f9e0 00000400 01131598 0x78021646
1143fdd4 00613d86 01131598 00613df0 14c4f608 STORE!NNTPCON::HrSendStatusResponse
1143fecc 00616633 00000015 00000001 14c4bfd8 STORE!NNTPCON::EcLast
1143fef8 006162f4 0111af68 0000000c 0000000c STORE!NNTPCON::EcOnCmd
1143fef8 006162f4 0111af68 0000000c 0000000c STORE!NNTPCON::EcOnCmd+0x332
CAUSE
The issue can occur if the information store sends a message in response to the client that issued the LAST or NEXT command. Because the related message has a percent sign in the message ID, the information store incorrectly processes the character as a type field character when the response message is composed, which results in an access violation.
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:
191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
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/2/2003 |
|---|
| Keywords: | kbbug kbExchange550preSP4fix kbExchange550sp4Fix kbfix kbQFE KB269076 |
|---|
|