XADM: Exchange 2000 Server JET Database Stops Unexpectedly Because of Large Subject Prefix on Embedded Messages

This article was previously published under Q288524
This article has been archived. It is offered "as is" and will no longer be updated.
The Exchange 2000 JET database may stop unexpectedly with a call stack that is similar to the following call stack:
ChildEBP RetAddr  Args to Child47d4e05c 61d51cbb 00000000 3a121ae0 0000021c MSVCRT!wcslen+0x447d4e070 61d51a97 00000000 3afed180 2fc16960 JCB!StripTrailingWhiteSpace+0xe47d4e73c 001c0ff6 3a121ae0 00000005 3afed180 JCB!EcJcbFabricateURLCompNameCallback+0x54f47d4e77c 001b8cb8 3a14b890 00000080 80000280 ESE!ErrRECICallback+0x8c47d4e7a8 001c1686 00000080 80000280 055d168c ESE!ErrRECCallback+0x6747d4e80c 001c1386 00000005 47d4e828 3afed180 ESE!ErrRECRetrieveColumns+0x3bf47d4e828 001c134e 055d15d8 00000005 05562820 ESE!ErrIsamRetrieveColumns+0x3947d4e840 001c12bc 055d15d8 00000005 05562820 ESE!JetRetrieveColumnsEx+0x4f47d4e878 004059bc 3a121ae0 3afed180 055d15d8 ESE!JetRetrieveColumns+0x5e47d4e898 00405767 055d15d8 00000005 00000001 store!JTAB_BASE__EcRetrieveColumns+0xd347d4e8b8 00404402 05562820 000004b0 47d4ebc8 store!JTAB_BASE__EcLoadCache+0xef47d4e8e8 00404dd4 47d4eb64 47d4e923 00000001 store!JTAB_BASE__EcRetrieveColumnByPtagid+0xf847d4eb40 0040531d 47d4eb64 47d4ebc8 000004b0 store!JTAB_BASE__EcGetPropByPtagid+0xb147d4eb6c 0040b52b 0e62000b 47d4ebc8 000004b0 store!JTAB_BASE__EcGetProp+0x3847d4ebe4 00441d9c 055222b8 00000000 0532a298 store!EcGetURLCompNameWithPostfix+0x6447d4ec28 00441ade 056667d8 47d4ec68 00000001 store!EcGetNewPostfix+0x37947d4ec54 004419e7 0532a298 055222b8 00000001 store!EcGetUniqueURLCompName+0xb647d4ec7c 00444a3f 47d4f04c 0532a298 00000000 store!EcSetHashAndResolveURLCompName+0x5b47d4ed8c 00449e18 09a53810 00000000 47d4f038 store!OMSG__EcInsertMsgFolder+0xe8747d4efc8 00717056 47d4f04c 47d4f038 47d4f074 store!OMSG__EcDeliver+0xec1					
The Exchange 2000 information store uses a JET database (Ese.dll), which in turn uses the Jcb.dll (JET Call Backs) file. The trap is reported as a JET exception because the trap occurs within an exception-wrapped JET call, but the trap is actually the result of a logic error in the Jcb.dll file. The Exchange 2000 server's Store.exe program also stops unexpectedly when this problem occurs because the Store.exe program depends on the JET database.
This problem can occur if JET incorrectly constructs a Uniform Resource Locator (URL) for an object when a large subject prefix exists in an embedded message.
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 theMicrosoft 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: JET

File nameVersion
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 1.

Article ID: 288524 - Last Review: 10/23/2013 16:16:10 - Revision: 1.3

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange2000presp1fix kbfix kbqfe KB288524