Microsoft KB Archive Search

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.

  1. Home
  2. Messages are stuck in the Submission queue until NDRs are returned or the server is restarted

Messages are stuck in the Submission queue until NDRs are returned or the server is restarted

View products that this article applies to.

Symptoms

In a Microsoft Exchange Server 2013 environment, messages are stuck in the Submission queue until nondelivery report (NDR) messages are returned or the server is restarted. Additionally, the following exception is logged in the message tracking logs:

Microsoft.Exchange.Data.Storage.OleConversionServerBusyException: OLE conversion failed ---> Microsoft.Exchange.ProcessManager.ComInterfaceInitializeException: Work process exit before class id registered!
at Microsoft.Exchange.ProcessManager.ComProcessAgent`1.InternalLaunchWorkProcess(OnCreateWorker createWorker, Object requestParameters)
at Microsoft.Exchange.ProcessManager.ComProcessAgent`1.LaunchWorkerProcess(OnCreateWorker createWorker, Object requestParameters)
at Microsoft.Exchange.ProcessManager.ComProcessManager`1.ExecuteRequest(Object requestParameters)
at Microsoft.Exchange.Data.Storage.OleConverter.ConvertToBitmap(Stream oleDataStream)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.OleConverter.ConvertToBitmap(Stream oleDataStream)
at Microsoft.Exchange.Data.Storage.OleAttachment.ConvertToBitmap()
at Microsoft.Exchange.Data.Storage.OleAttachment.ConvertToImage(Stream outStream, ImageFormat format)
at Microsoft.Exchange.Data.Storage.OleAttachment.TryConvertToImage(Stream outStream, ImageFormat format)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeStreamAttachment(StreamAttachmentBase attachment, MimeFlags flags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeAttachment(MimePartInfo part, MimeFlags flags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimePart(MimePartInfo part, MimeFlags mimeFlags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeParts(List`1 parts, MimeFlags mimeFlags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimePart(MimePartInfo part, MimeFlags mimeFlags)
at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.ConvertItemToMimeInternal(MimeStreamWriter writer, ConversionLimitsTracker limits)

↑ Back to the top

Cause

This problem occurs because of handle leaks that cause the OleConversionServerBusyException exception in the transport.

↑ Back to the top

Resolution

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

↑ 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

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3138644
Revision : 1
Created on : 1/7/2017
Published on : 3/15/2016
Exists online : False
Views : 258