Article ID: 810078
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange Server 2000 Service Pack 1
- Microsoft Exchange 2000 Server Service Pack 2
- Microsoft Exchange Server 2000 Service Pack 3
SYMPTOMS
After you move a mailbox from Microsoft Exchange 5.5 Server to Exchange 2000 Server, the first logon to that mailbox may trigger an access violation in the information store.
MORE INFORMATION
A review of the call stack generated by the access violation is similar to the following:
ChildEBP RetAddr Args to Child
3110e95c 6123ceae 0c97bfe0 3110e978 00000001 EXCDO!CrackLTFolderEID+0x10
3110f020 004a90fa 0c94b1c8 3110f04c 06ac9e50 EXCDO!CCDOMailBoxCreateCallback::EcDoFn+0x5b0
3110f058 004a9032 00000000 00000000 17f1b698 store!EcDodofunctionsAndQueueSubs+0x11e
3110f080 004d150f 00000002 0c8e0878 0c94b1c8 store!EcProcessSyncEvents+0x32
3110f1ec 004627ce 0c94d1d0 0c6b2e30 0c94d1e0 store!LOGON::EcSetfLocalized+0x6dc
3110f44c 00463d1a 06ac3630 0c6b2e30 8000040c store!LOGON::EcConfig+0x1671
3110f59c 0046e542 00000000 00000000 0fb208fb store!EcDoPrivateLogonOp+0x118
3110f7ac 0043a123 3110f7ec 00000000 000001fc store!EcLogon+0x2ff
3110f8d8 004399bc 3110f900 00000200 3110f8f4 store!EcRpc+0x3d8
3110f8f0 77d43b58 388fab88 0c8e3d60 00000040 store!EcDoRpc+0x60
3110f914 77da2577 00439977 3110fab8 00000004 RPCRT4!Invoke+0x30
3110fd10 77da3174 00000000 00000000 3110fdfc RPCRT4!NdrStubCall2+0x63d
3110fd2c 77d430b1 3110fdfc 0012b3c0 3110fdfc RPCRT4!NdrServerCall2+0x17
3110fd64 77d42ff7 00439967 3110fdfc 3110fe40 RPCRT4!DispatchToStubInC+0x84
3110fdbc 77d42f09 00000002 00000000 3110fe40 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x100
3110fddc 77d4bd18 3110fdfc 00000000 3110fe40 RPCRT4!RPC_INTERFACE::DispatchToStub+0x5e
3110fe44 77d4bc59 00000000 2e02a840 388c9818 RPCRT4!OSF_SCALL::DispatchHelper+0xa4
3110fe58 77d4ba5e 00000000 00000002 00000001 RPCRT4!OSF_SCALL::DispatchRPCCall+0x115
3110fe90 77d4b7a8 2e02a828 00000003 00000002 RPCRT4!OSF_SCALL::ProcessReceivedPDU+0x43
3110feb0 77d4aea7 2e02a828 000000a0 00015f90 RPCRT4!OSF_SCALL::BeginRpcCall+0xd0
CAUSE
This issue occurs when the Microsoft Outlook special folders have a 32-byte short-term entryid instead of the expected 42-byte long-term entryid. This short-term entryid causes the information store to access uninitialized memory while parsing the entryid.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Component: MDB
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). 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
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB810078
