Fixes an issue in which an event 1033 is logged and the Microsoft Exchange Mailbox Transport Delivery service crashes in an Exchange Server 2013 environment.

To fix this problem, install Cumulative Update 15 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.

Cause. This problem occurs because MSExchangeRPC crashes when it processes a stream object that has a Null value for a specific property bag. Resolution. To resolve this problem, install Update Rollup 10 for Exchange Server 2010 Service Pack 3. Discusses that the MSExchangeRPC service stops working intermittently in Exchange 2010.

This update prevents you from receiving error messages that are related to the application manifest expiry feature of the AD RMS clients. This fix is also necessary for Windows Rights Management clients. This update ensures continued compatibility between RMS-enabled applications and the RMS client.

The MSExchange FrontEnd Transport service crashes when email messages that contain a null "X-OriginatorOrg" message header are processed. Cause. This problem occurs because the Inbound Trust Agent does not invoke the SmtpDomain ctor when the "X-OriginatorOrg" message header is null. Resolution.

If you are trying to sign into another Microsoft service, you may be prompted to add a phone number or email address. We do this to ensure that your account is more secure and to make it easier for you to recover your password when necessary.

Solution 1: Remove your payment option and add it again. Go to settings and select Account > Manage Payment Options > Remove Payment Option. Remove the option you want to use, then add it again.

Fixes an issue in which the RPC Client Access service may crash when you import a .pst file by using the New-MailboxImportRequest cmdlet in an Exchange Server 2010 environment.

This issue is caused by Exchange Based Assistants (EBAs) in the service writing edits to the meeting item causing a conflict resolution problem. The current fix is to skip all notifications on meeting drafts so that no EBA or ItemAssistant will get a chance to modify a meeting draft.

When you use Queue Veiwer or run the Get-Message cmdlet to view the properties of a poison message in a Microsoft Exchange Server 2016 environment, the Edge Transport service (Edgetransport.exe) crashes. The crash causes messages in process to be moved to the poison queue unexpectedly.