Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Microsoft Exchange Information Store service does not start successfully on an Exchange 2003 server


View products that this article applies to.

Symptoms

When you try to start the Microsoft Exchange Information Store service on a server that is running Microsoft Exchange Server 2003, the Microsoft Exchange Information Store service does not start successfully. Additionally, you do not receive an error message to indicate that there is a problem. In this situation, you may assume that the Microsoft Exchange Information Store service is taking a very long time to start.

↑ Back to the top


Cause

This problem occurs because the replay operation may encounter a loop condition when the Microsoft Exchange Information Store service logs file replay in the Exchange Server database. The replay operation will never be finished. Additionally, you will not receive an error message to indicate that there is a problem.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft Exchange Server 2003 Service Pack 2 (SP2) installed before you apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, the following services are stopped and then restarted when you apply this hotfix:
  • Microsoft Exchange System Attendant
  • Exchange Installable File System (ExIFS)
  • IIS Admin service and all dependent services

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English 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 nameFile versionFile sizeDateTime
Ese.dll6.5.7652.222,255,87228-Mar-200718:13
Exifs.sys6.5.7652.22196,28828-Mar-200715:26
Exwin32.dll6.5.7652.22175,61628-Mar-200716:29
Ifsproxy.dll6.5.7652.2218,43228-Mar-200716:44

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
246216 Exchange 2000 Server or Exchange Server 2003 ExIFS may not start after ExIFS is manually stopped

↑ Back to the top


More information

After you apply the hotfix, an event that resembles the following is logged when log files are replayed:

Event Type: Information
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 301
Description: Information Store (2636) SG1: The database engine has begun replaying logfile G:\EXCHSRVR\MDBDATA\MDBDATA\E00.log. For more information, click http://www.microsoft.com/contentredirect.asp.

Note Event 301 indicates regular log file replay.

If a loop condition occurs, the loop condition will now be detected. Additionally, the Extensible Storage Engine (ESE) logs an event that resembles the following:

Event Type: Information
Event Source: ESE
Event Category: General
Event ID: 901
Description: Information Store (2636) Internal trace: ver.cxx (8459)
For more information, click http://www.microsoft.com/contentredirect.asp.

Then, the Microsoft Exchange Information Store service is stopped. When this occurs, we recommend that you either restore another backup or repair the database because you cannot replay the log files. After the Microsoft Exchange Information Store service is stopped, the following events are logged:

Event Type: Information
Event Source: MSExchangeIS
Event Category: General
Event ID: 9643
Description: Process termination function StoreTerminateProcess was called by a function in module C:\Program Files\Exchsrvr\bin\ESE.dll; some parameters and their values were <uExitCode - -1>. A significant section of the call stack is in the data section.

Event Type: Error
Event Source: Microsoft Exchange Server
Event Category: None
Event ID: 1000
Description: Faulting application store.exe, version 6.5.7638.2, stamp 434353c1, faulting module store.exe, version 6.5.7638.2, stamp 434353c1, debug? 0, fault address 0x001fc3ae.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

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 Server 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

↑ Back to the top


Keywords: KB933398, kbqfe, kbhotfixserver, kbexpertiseinter, kbexchstore, kbautohotfix

↑ Back to the top

Article Info
Article ID : 933398
Revision : 5
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 227