Microsoft KB Archive/266093

From BetaArchive Wiki
Knowledge Base


XADM: Information Store Stops Responding Because of Invalid QueryRows Request

Article ID: 266093

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q266093


SYMPTOMS

The information store (Store.exe) may suddenly stop and generate an access violation. If Dr. Watson is active as the default debugger, a Dr. Watson log and a User.dmp file (if Dr. Watson is configured to create a User.dmp file) may be generated.

The call stack is similar to the following:

ChildEBP RetAddr Args to Child
141ff8e0 0040e59c 000011ee 1e8ece80 00000000 store!EcFormatMVString8+0x21
141ff908 004103ac 000011ee 00000000 141ff934 store!EcFormatValue+0x654
141ff938 00445a06 000011ee 00000015 00000048 store!EcFormatRow+0x132
141ff998 00445b05 00000001 0000000b 00000000 store!VMSG__EcQueryRows+0x2d0
141ff9c8 00445ca9 0000000b 00000000 00000001 store!EcQueryRowsOp+0x65
141ffa18 0040f45e 00000001 00002504 1e1d9f68 store!EcQueryRows+0x9e
1ef35858 1ef35858 eca10001 00002148 00000000 store!EcRpc+0x81c


RESOLUTION

To 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.

STATUS

Microsoft 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.

Keywords: kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB266093