Select the product you need help with

XADM: The Information Store Generates a 0xfffffae2 JET_errInvalidTableId Error During Many Client Operations

Article ID: 312966 - View products that this article applies to.

This article was previously published under Q312966

SYMPTOMS

An Exchange 2000 server may generate a 0xfffffae2 JET_errInvalidTableId error during many client operations. The following error message may be logged:

Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: General
Event ID: 1110
Date: 8/13/2001
Time: 5:25:29 PM
User: N/A
Computer: Server
Description:
Error 0xfffffae2 occurred while writing per-user information for User@Domain.com on database "First Storage Group\Public Folder Store (server)".

You may also receive the following events in the event log:

Event Type: Warning
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 1025

Description:
An error occurred on database "First Storage Group\Mailbox Store ". Function name or description of problem: SLINK::EcTestMessage Error: 0xfffffae2

Event Type: Warning
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 1115

Description:
Error 0xfffffae2 returned from closing database table, called from function JTAB_BASE::EcCloseTable on table 5-1AF4EA0.

Back to the top | Give Feedback

RESOLUTION

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 the Microsoft Knowledge Base:

301378

(http://support.microsoft.com/kb/301378/EN-US/ )

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: Information store

Collapse this tableExpand this table

File name	Version
Store.exe	6.0.5770.4

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

Back to the top | Give Feedback

STATUS

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

Back to the top | Give Feedback