XADM: The Exchange Information Store Service Takes a Long Time to Start; or Users Cannot Log On to the Server, and Events 1014 and 1011 Are Logged in the Application Event Log

You may experience the following symptoms in Microsoft Exchange 2000 Server:

• The Exchange Information Store service (Store.exe) may take a longer time than expected to start. For example, the service may take up to several hours to start.
  
  -or-
• Users cannot log on to the server, and the following events are logged in the application event log:

  • Event ID: 1014
    Source: POP3SVC
    Category: General
    Description:
    An error occurred calling into the Microsoft Exchange Information Store service: the call to EcCreateOtherSess failed with error 0x3f0.

  • Event ID: 1011
    Source: POP3SVC
    Category: Authentication
    Description:
    Authentication attempt from IPAddress to EmailAddress has failed with error 0x3f0.

    Also, entries that are similar to the following are logged in the Store.log file:
    TID e38 TIME Time TAG 3: Error ecServerOOM (1008) in EcGetSess
    TID e38 TIME Time TAG 3: Error ecServerOOM (1008) in EcCreateOtherSess

This problem occurs because for each registered sink, one session object and one logon object are created in Exchange 2000 Server. If the information store contains a large number of mailboxes, the Information Store service may take a longer time to start, or it may run out of sessions. The information store can contain a maximum of 65,536 session objects.

If the information store contains a large number of sessions (for example, if it contains 50,000 sessions) the Information Store service may take a longer time than expected to start. If more than 65,536 sinks are registered, the maximum number of sessions is used. As a result, users cannot log on to the server, and other operations that require information store sessions cannot complete successfully.

Cumulative Rollup Information

To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 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.

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, submit a request to 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.

Component: MDB

The English version of this hotfix 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 Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.