Microsoft Knowledge Base Wiki

When the Microsoft Exchange Information Store service (Store.exe) runs on an Exchange Server 2010 Mailbox server, Store.exe crashes occasionally. When this issue occurs, the following events are logged in the Application log:

Time:     Time
ID:       1000
Level:    Error
Source: Application Error
Machine:  Computer
Message:  Faulting application name: store.exe, version: Version, time stamp: Time Stamp
Faulting module name: store.exe, version: Version, time stamp: Time Stamp
Exception code: 0xc0000005
Fault offset: Offset
Faulting process id: Process ID
Faulting application start time: Start Time
Faulting application path: C:Program FilesMicrosoftExchange ServerV14binstore.exe
Faulting module path: C:Program FilesMicrosoftExchange ServerV14binstore.exe
Report Id: ID

Time:     Time
ID:       4999
Level:    Error
Source: MSExchange Common
Machine:  Computer
Message:  Watson report about to be sent for process id: Process ID, with parameters: E12N, Build Type, Version Number, store.exe, store.exe, XXXX, c0000005, XXXX, Version Number.
ErrorReportingEnabled: False

Time:     Time
ID:       9659
Level:    Error
Source: MSExchangeIS
Machine: Computer
Message:  The Microsoft Exchange Information Store encountered an unexpected exception 0xC0000005 at address Address while processing a request for user User.

This issue occurs because the Information Store service tries to access an object that is deleted from the cache.

To resolve this issue, install the following update rollup:

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

Article ID: 2796490 – Last Review: May 30, 2013 – Revision: 1.0

Consider the following scenario:

• You have multiple Active Directory sites in a Microsoft Exchange Server 2010 environment that has Update Rollup 3 for Exchange Server 2010 Service Pack 2 or a later-version update rollup installed.
• The Outlook Anywhere feature is enabled on the Client Access servers in each site.
• You use Outlook Anywhere to connect to a mailbox through the Client Access server that is located in the same site as the mailbox.
• You try to open another mailbox that is located in a different site and that you have sufficient permissions to access. For example, you try to open a shared mailbox that is located in a different site.

In this scenario, the operation fails and you receive an error message that resembles the following:

Additionally, the following event is logged in the RPC Client Access log on the Client Access server:

RopHandler: Logon: RopExecutionException The client should use Outlook Anywhere and RpcClientAccess server from site SiteName to access the mailbox.

To resolve this issue, install the following update rollup:

To work around this issue, apply the following setting on all internet-facing Client Access servers:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then select the following registry subkey:

   HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeRPCParametersSystem

3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4. Type EnablePreferredSiteEnforcement, and then press Enter.
5. In the Details pane, right-click EnablePreferredSiteEnforcement, and then click Modify.
6. In the Value data box, type 0, and then click OK.
7. Exit Registry Editor.

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

For more information about the issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Article ID: 2756460 – Last Review: May 30, 2013 – Revision: 1.1

Microsoft has released Update Rollup 1 for Microsoft Exchange Server 2010 Service Pack 3 (SP3). This update is dated May 29, 2013. This article describes the following information about the update rollup:

• The issues that the update rollup resolves.
• How to obtain the update rollup.
• The prerequisites to install the update rollup.

Note If you are installing Update Rollup 1 for Exchange Server 2010 SP3 in a double-byte character set (DBCS) Windows Server 2012 environment, you must first change the system language preference for non-Unicode programs. To make this change, please see the “More Information” section.

Issues that the update rollup resolves

Update Rollup 1 for Exchange Server 2010 SP3 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2561346

  (http://support.microsoft.com/kb/2561346/
  )

  Mailbox storage limit error when a delegate uses the manager’s mailbox to send an email message in an Exchange Server 2010 environment

• 2729954

  (http://support.microsoft.com/kb/2729954/
  )

  Can’t send voice message to a selected non-primary email address in an Exchange Server 2010 environment

• 2750846

  (http://support.microsoft.com/kb/2750846/
  )

  Information Store service crashes when you mount public folder databases on an Exchange Server 2010 server

• 2751628

  (http://support.microsoft.com/kb/2751628/
  )

  Event ID 9682 does not record the folder name when you delete a public folder in an Exchange Server 2010 environment

• 2756460

  (http://support.microsoft.com/kb/2756460/
  )

  You cannot open a mailbox that is located in a different site by using Outlook Anywhere in an Exchange Server 2010 environment

• 2763065

  (http://support.microsoft.com/kb/2763065/
  )

  Move request log is logged when you move a mailbox in an Exchange Server 2010 SP2 environment

• 2777742

  (http://support.microsoft.com/kb/2777742/
  )

  Address Book service crashes on an Exchange Server 2010 Client Access server when a server has been running for 25 days or more

• 2781488

  (http://support.microsoft.com/kb/2781488/
  )

  RPC_S_SERVER_UNAVAILABLE (0x6BA) error code when you use a MAPI or CDO-based application in an Exchange Server 2010 environment

• 2782683

  (http://support.microsoft.com/kb/2782683/
  )

  Email message that a user sends by using the “Send As” or “Send On Behalf” permission is saved only in the Sent Items folder of the sender in an Exchange Server 2010 environment

• 2784210

  (http://support.microsoft.com/kb/2784210/
  )

  Ethical wall does not function as expected when the ReportToOriginatorEnabled property is disabled in an Exchange Server 2003 and Exchange Server 2010 coexistence environment

• 2793348

  (http://support.microsoft.com/kb/2793348/
  )

  Read receipt is sent unexpectedly when you view an email message by using Outlook Web App

• 2796490

  (http://support.microsoft.com/kb/2796490/
  )

  Microsoft Exchange Information Store service crashes on an Exchange Server 2010 Mailbox server

• 2802569

  (http://support.microsoft.com/kb/2802569/
  )

  Mailbox synchronization fails on an Exchange ActiveSync device in an Exchange Server 2010 environment

• 2803132

  (http://support.microsoft.com/kb/2803132/
  )

  Delayed email message delivery on a BlackBerry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2

• 2806602

  (http://support.microsoft.com/kb/2806602/
  )

  EdgeTransport.exe process crashes on an Exchange Server 2010 Hub Transport server

• 2814723

  (http://support.microsoft.com/kb/2814723/
  )

  Server loses network connectivity and UDP ports are used up on an Exchange Server 2010 server

• 2814847

  (http://support.microsoft.com/kb/2814847/
  )

  Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device

• 2816934

  (http://support.microsoft.com/kb/2816934/
  )

  Error code 0X800CCC13 when an additional POP3 or IMAP account is used to send an email message and Outlook online mode is used to connect to an Exchange Server 2010 environment

• 2817140

  (http://support.microsoft.com/kb/2817140/
  )

  Exchange Replication service crashes intermittently in an Exchange Server 2010 environment

• 2817852

  (http://support.microsoft.com/kb/2817852/
  )

  Cyrillic characters are displayed as question marks in the “To” field of message items in the Sent Items folder in an Exchange 2010 environment

• 2818456

  (http://support.microsoft.com/kb/2818456/
  )

  Attachments are missing from an embedded message in an Exchange Server 2010 SP2 environment

• 2822208

  (http://support.microsoft.com/kb/2822208/
  )

  Unable to soft delete some messages after installing Exchange 2010 SP2 RU6 or SP3

• 2826066

  (http://support.microsoft.com/kb/2826066/
  )

  VSAPI-based antivirus software causes delayed response in an Exchange Server 2010 environment

• 2827037

  (http://support.microsoft.com/kb/2827037/
  )

  Copy of an item is created in the Version subfolder in an Exchange Server 2010 environment

• 2833888

  (http://support.microsoft.com/kb/2833888/
  )

  No items are displayed in Outlook after you install Exchange Server 2010 SP3 or Update Rollup 6 for Exchange Server 2010 SP2

• 2840099

  (http://support.microsoft.com/kb/2840099/
  )

  ArgumentOutOfRangeException exception when an EWS application creates a new MIME email in an Exchange Server 2010 environment

Update rollup information

To download and install Update Rollup 1 for Exchange Server 2010 SP3, go to the following Microsoft Update website: For more information about how to install the latest Update Rollup for Exchange 2010, go to the following Microsoft website:Note Microsoft Update does not detect update rollups on Exchange Server 2010 mailbox servers that are part of a database availability group (DAG).

To enable you to apply this update rollup in the following scenarios, the update rollup is also available from the Microsoft Download Center:

• Deploy Update Rollup 1 for Exchange Server 2010 SP3 to multiple computers that are running Exchange Server 2010 SP3.
• Deploy Update Rollup 1 for Exchange Server 2010 SP3 to mailbox servers that are part of a DAG.

The file is available for download from the following Microsoft Download Center website: Release date: May 29, 2013.

Important information for customers who install the update on computers that are not connected to the Internet

When you install this update rollup on a computer that is not connected to the Internet, you may experience long installation times. Additionally, you may receive the following message:

This behavior is caused by network requests to connect to the following website:

http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl

(http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl)

These network requests represent attempts to access the certificate revocation list for each assembly that native image generation (NGen) compiles to native code. However, because the Exchange server is not connected to the Internet, each request must wait to time out before the process continues.

To resolve this issue, follow these steps:

1. On the Tools menu in Windows Internet Explorer, click Internet Options, and then click the Advanced tab.
2. In the Security section, click to clear the Check for publisher’s certificate revocation check box, and then click OK.

Clear this security option in Internet Explorer only if the computer is in a tightly controlled environment. When the setup is completed, click to select the Check for publisher’s certificate revocation check box again.

Update issue on computers that have customized Outlook Web App files

Important Before you apply the update rollup, make a backup copy of any customized Outlook Web App files. For more information about how to customize Outlook Web App, go to the following Microsoft website:

When you apply an update rollup package, the update process updates the Outlook Web App files if they are required. Therefore, any customizations to the Logon.aspx file or to other Outlook Web App files are overwritten, and you must re-create the Outlook Web App customizations in Logon.aspx.

Update issue for CAS Proxy Deployment Guidance customers who deploy CAS-CAS proxying

If you meet both of the following conditions, apply the update rollup on the Internet-facing Client Access servers before you apply the update rollup on the non-Internet-facing Client Access servers:

• You are a CAS Proxy Deployment Guidance customer.
• You have deployed CAS-CAS proxying.

Note For other Exchange Server 2010 configurations, you do not have to apply the update rollup on the servers in any particular order.

For more information about CAS-CAS proxying, go to the following Microsoft website:

Prerequisites

To apply this update rollup, you must have Exchange Server 2010 SP3 installed.

Important Remove all interim updates for Exchange Server 2010 SP3 before you apply this update rollup.

Restart requirement

The required services are automatically restarted when you apply this update rollup.

Removal information

To remove Update Rollup 1 for Exchange Server 2010 SP3, use the Add or Remove Programs item in Control Panel to remove update 2803727.

You cannot install or uninstall Update Rollup 1 for Exchange Server 2010 SP3 on a computer that is running the DBCS version of Windows Server 2012 if the language preference for non-Unicode programs is set to the default language. To work around this issue, you must first change this setting. To do this, follow these steps:

1. In Control Panel, open the Clock, Region and Language item, and then click Region.
2. Click the Administrative tab.
3. In the Language for non-Unicode programs area, click Change system locale.
4. On the Current system locale list, click English (United States), and then click OK.

After you successfully install or uninstall Update Rollup 1, revert this language setting, as appropriate.

A fix for this problem is scheduled to be included in a future update rollup.

For more information about terminology that Microsoft uses to describe software updates, click the following article number to go to the article in the Microsoft Knowledge Base:

Article ID: 2803727 – Last Review: May 30, 2013 – Revision: 3.0

Consider the following scenario:In this scenario, user A may receive the following error message unexpectedly:

Additionally, the following event is logged in the Application log on the Mailbox server:

Log Name: Application
Source: MSExchangeIS
Date: Date 
Event ID: 8528
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: Computer 
Description:
The mailbox for /o=Organization/ou=Site/cn=Recipients/cn=UserB has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages to this mailbox are returned to sender. The mailbox owner should be notified about the condition of the mailbox as soon as possible.

Note When this issue occurs, the mailbox size of user B is nowhere near its storage quota limit.

This issue occurs because when user A is automatically re-logged back on to user B’s mailbox, the Exchange server incorrectly obtains quota information of user A’s mailbox instead of the quota of user B’s mailbox.

To resolve this issue, install the following update rollup:

To work around this issue, user A has to log off user B’s mailbox and then log on to user B’s mailbox again.

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

For more information about the Reread Logon Quotas Interval value, go to the following Microsoft website:For more information about how to configure storage quotas for a mailbox, go to the following Microsoft website:

Article ID: 2561346 – Last Review: May 30, 2013 – Revision: 4.0

You may experience the following symptoms either in Microsoft Outlook in Online mode or in Outlook Web App (OWA) when the mailbox is located on a server on which Exchange 2010 Service Pack 2 RU6 or Exchange 2010 Service Pack 3 has been installed:

1. You cannot soft delete messages that contain voice mail attachments.
2. You cannot soft delete messages that have attachments (such as a PDF file) that are sent from a FAX server, a printer, or a scanner.

Note This issue does not occur if the message is sent by a user instead of by an application, or if the message has no attachments.

This issue occurs after Exchange 2010 Service Pack 2 RU6 or Exchange 2010 Service Pack 3 is installed.

To resolve this issue, install the following update rollup:

Workaround 1: Hard delete the message instead of soft deleting

To hard delete email messages in Outlook, select the message, and then press Shift+Delete.

Workaround 2: Use cached mode for Outlook

When you use the cached mode of Outlook, the message can be soft deleted. For more information, go to the following Microsoft TechNet topic:

For more information about how to recover deleted messages in Microsoft Exchange 2007 or Microsoft Exchange 2003, click the following article number to go to the article in the Microsoft Knowledge Base:

For more information about how to recover deleted messages in Microsoft Exchange 2010, go to the following Microsoft TechNet website:

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2822208 – Last Review: May 30, 2013 – Revision: 17.0

Consider the following scenario:

• You install Microsoft Exchange Server 2010 Service Pack 3 (SP3) or Update Rollup 6 for Exchange Server 2010 Service Pack 2 (SP2) in an Exchange environment.
• Microsoft Outlook is running in online mode.
• You select a folder in Outlook.
• You add a To or Cc column to the folder view.

In this scenario, no items are displayed in the folder. However, if you remove the To or Cc column from the folder view, all the items are displayed in the folder.

Note This issue occurs only when the user profile does not use the Unicode format. For example, this issue occurs when the user profile uses the American National Standards Institute (ANSI) format. To determine which format the user profile uses, follow these steps as appropriate for the version of Outlook that you are running.

Outlook 2007

1. On the Tools menu, click Account Settings, select your Exchange account, and then click Change.
2. Click More Settings, and then click the Advanced tab.

   The format is displayed under the Mailbox Mode heading.

Outlook 2010 and Outlook 2013

1. On the File tab, click Info, click Account Settings, and then click Account Settings.
2. On the E-mail tab, select your Exchange account, and then click Change.
3. Click More Settings, and then click the Advanced tab.

   The format is displayed under the Mailbox Mode heading.

To resolve this issue, install the following update rollup:

To work around this issue, use one of the following methods:

Method 1

Remove the To or Cc column from the folder view.

Method 2

Run Outlook in cached mode.

Method 3

Create a new user profile that uses the Unicode format.

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

Article ID: 2833888 – Last Review: May 30, 2013 – Revision: 4.0

The Microsoft Exchange Replication service (MSExchangeRepl.exe) crashes intermittently in a Microsoft Exchange Server 2010 environment. Additionally, the following event is logged in the Application log:

Log Name: Application
Source: MSExchange Common
Date: Date
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer 
Description:
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version Number, msexchangerepl, M.E.Isam.Interop, M.E.I.JetInterop.MakeManagedDateTime, System.ArgumentOutOfRangeException, XXXX, Version Number. 
ErrorReportingEnabled: True

This issue is caused by a System.ArgumentOutOfRangeException exception that occurs when the Exchange Replication service encounters invalid date and time parameters.

To resolve this issue, install the following update rollup:

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

Article ID: 2817140 – Last Review: May 30, 2013 – Revision: 1.0

The Microsoft Edge Transport service (EdgeTransport.exe) may crash on a Microsoft Exchange Server 2010 Hub Transport server. Additionally, the following events are logged in the Application log:

Log Name: Application
Source: MSExchange Common
Date: Date 
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer 
Description:
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version Number, edgetransport, M.E.Data.Storage, M.E.D.S.COWSentItems.GetMailboxSentItemsConfiguration, M.E.M.StoreDriver.FailFast+UnexpectedSubmissionException, XXXX, Version Number. 
ErrorReportingEnabled: True

Log Name: Application
Source: MSExchange Store Driver
Date: Date 
Event ID: 1009
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Computer: Computer 
Description:
The store driver encountered a poison message during message submission. The submission will be stopped for event ID on mailbox ID MDB ID. Exception is: System.NullReferenceException: Object reference not set to an instance of an object. 
at Microsoft.Exchange.Data.Storage.COWSentItems.GetMailboxSentItemsConfiguration(MailboxSession mailboxSession, Boolean isSendOnBehalfOf)
at Microsoft.Exchange.Data.Storage.COWSentItems.GroupOperation(COWSettings settings, IDumpsterItemOperations dumpster, COWTriggerAction operation, FolderChangeOperationFlags flags, StoreSession sourceSession, StoreSession destinationSession, StoreObjectId destinationFolderId, StoreObjectId[] itemIds, GroupOperationResult result, Boolean onBeforeNotification, CallbackContext callbackContext)
at Microsoft.Exchange.Data.Storage.COWSession.InternalFolderChangeItemGroup(List`1 clients, COWTriggerAction operation, FolderChangeOperationFlags flags, StoreSession destinationSession, StoreObjectId destinationFolderId, StoreObjectId[] itemIds, Boolean onBeforeNotification, CallbackContext callbackContext)
at Microsoft.Exchange.Data.Storage.COWSession.InternalBeforeFolderChange(COWTriggerAction operation, FolderChangeOperationFlags flags, StoreSession destinationSession, StoreObjectId sourceFolderId, StoreObjectId destinationFolderId, ICollection`1 itemIds, CallbackContext callbackContext)
at Microsoft.Exchange.Data.Storage.COWSession.OnBeforeFolderChange(FolderChangeOperation operation, FolderChangeOperationFlags flags, StoreSession sourceSession, StoreSession destinationSession, StoreObjectId sourceFolderId, StoreObjectId destinationFolderId, ICollection`1 itemIds, CallbackContext callbackContext)
at Microsoft.Exchange.Data.Storage.MailboxSession.OnBeforeFolderChange(FolderChangeOperation operation, FolderChangeOperationFlags flags, StoreSession sourceSession, StoreSession destinationSession, StoreObjectId sourceFolderId, StoreObjectId destinationFolderId, ICollection`1 itemIds, CallbackContext callbackContext)
at Microsoft.Exchange.Data.Storage.StoreSession.DoneWithMessage(Item item)
at Microsoft.Exchange.MailboxTransport.StoreDriver.MapiSubmissionItem.DoneWithMessage()
at Microsoft.Exchange.MailboxTransport.StoreDriver.MailItemSubmitter.b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriver.StorageExceptionHandler.RunUnderExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction)
at Microsoft.Exchange.MailboxTransport.StoreDriver.MailItemSubmitter.Submit()
at Microsoft.Exchange.MailboxTransport.StoreDriver.RpcSubmit.SubmitMessageImpl(SubmissionInfo submissionInfo).

This issue occurs because of a System.NullReferenceException exception. The Edge Transport service checks the send item configurations during message submission. However, when multiple threads access protected data at the same time, an exception is thrown and the service crashes.

To resolve this issue, install the following update rollup:

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

Article ID: 2806602 – Last Review: May 30, 2013 – Revision: 1.0

Consider the following scenario:

• User A has a mailbox (MB1) that is located on an Active Directory site in a Microsoft Exchange Server 2010 environment.
• User B has a mailbox (MB2) that is located on another Active Directory site.
• You grant user A the “Send As” or “Send on behalf” permission for MB2.
• You run the Set-MailboxSentItemsConfiguration cmdlet so that email messages that user A sends on behalf of MB2 or from MB2 are saved in the Sent Items folder in MB1 and MB2.
• User A sends an email message from MB2. Or, user A sends an email message on behalf of MB2.

In this scenario, the email message is saved only in the Sent Items folder in MB1.

To resolve this issue, install the following update rollup:

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

For more information about the Set-MailboxSentItemsConfiguration cmdlet, go to the following Microsoft website:

Article ID: 2782683 – Last Review: May 30, 2013 – Revision: 1.0

Consider the following scenario:

• You use Microsoft Exchange Virus Scanning API (VSAPI)-based antivirus software in a Microsoft Exchange Server 2010 environment.
• A user’s mailbox that is under the protection of the antivirus software contains multiple messages.
• The user performs a certain operation on the mailbox to connect to a Mailbox server. For example, the user enables the AutoPreview feature to view multiple messages by using Microsoft Outlook in online mode.

In this scenario, there is a long delayed response from the Mailbox server. Additionally, this issue may result in new clients being unable to connect to Exchange server or a failover of databases to standby servers.

This issue occurs because the operation that the user performed triggers a property promotion that triggers virus scanning requests for each message item. When there are many items in the virus scanning queue, all remote procedure call (RPC) connections to the Mailbox server are exhausted as new clients wait for the completion of virus scanning operation. Therefore, the Mailbox server cannot respond to any RPC requests. Then, monitoring can detect the Exchange server is unresponsive and initiative a failover.

To resolve this issue, install the following update rollup:

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

For more information about how to enable the AutoPreview feature, go to the following Microsoft website:For more information about the property promotion, go to the following Microsoft website:

Article ID: 2826066 – Last Review: May 30, 2013 – Revision: 1.0