Article ID: 924627
Article Last Modified on 11/2/2007
APPLIES TO
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
SYMPTOMS
Consider the following scenario. Event ID 474 that includes error 1018 (0xfffffc06) in logged in the Application log on a server that is running Microsoft Exchange Server 2003. This event ID indicates that the mailbox database is corrupted. You then run the Eseutil and Isinteg utilities to repair and recover the mailbox database. The Isinteg utility does not report any warnings, errors, or fixes. However, when you try to mount the database, the following event that includes error 0xfffffa84 is logged in the Application log:
Event ID: 9519
Event Type: Error
Event Source: MSExchangeIS
User: N/A
Computer: Server_Name
Description: Error 0xfffffa84 starting database "Storage Group Name\Mailbox Store Name" on the Microsoft Exchange Information Store. Failed to attach to Jet DB. For more information, click http://search.support.microsoft.com/search/?adv=1.
Note The error code 0xfffffa84 translates to the error JET_errIndexNotFound.
CAUSE
This problem occurs because the Eseutil utility removes an index that is created when the database is first created. The Eseutil utility removes the index when you use the following command:
Eseutil /p
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
You must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you apply the hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart the computer after you apply the hotfix. However, the Microsoft Exchange Information Store service and all dependent services will be restarted.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Exosal.dll | 6.5.7651.52 | 70,144 | 28-Sep-2006 | 19:43 | x86 |
| Exsmtp.dll | 6.5.7651.52 | 405,504 | 28-Sep-2006 | 19:58 | x86 |
| Mdbmsg.dll | 6.5.7651.52 | 3,375,104 | 28-Sep-2006 | 06:29 | x86 |
| Store.exe | 6.5.7651.52 | 5,260,800 | 28-Sep-2006 | 19:46 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages
For more information about 1018 errors, click the following article number to view the article in the Microsoft Knowledge Base:
314917 Understanding and analyzing -1018, -1019, and -1022 Exchange database errors
To view a white paper about 1018 errors, visit the following Microsoft Web site:
Additional query words: XADM
Keywords: kbexchstore kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB924627
