troubleshooting Question

Exchange Server 2007 SP3 Cannot Send Messages with Attachments to External Hosts ...

Avatar of dakind50
dakind50 asked on
ExchangeOutlookWindows Server 2008
4 Comments1 Solution544 ViewsLast Modified:
Hello,
 
I have a Microsoft Windows Server 2008 SP2 system running Microsoft Exchange 2007 SP3. Recently we have updated our systems using the latest updates from Microsoft (testing on the development platform went without a hitch) and all of a suddent several issues cropped up. This post will be about one of them as I will post the other issues on the appropriate forums.
 
The biggest problem we are having right now is that all clients, whether from Microsoft Outlook or Outlook Web Access, cannot send messages with any kind of attachments. I enabled ContentConversionTracing after several Google searches and I have found something hinting to be the culprit:
 
Microsoft.Exchange.Data.Storage.StoragePermanentException: Message content has become corrupted. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   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, MimeFlags flags)
   at Microsoft.Exchange.Data.Storage.ItemConversion.<>c__DisplayClassf.<InternalConvertItemToMime>b__e()
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall)
   at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToMime(EmailMessage messageIn, Stream mimeOut, OutboundConversionOptions outboundOptions)
   at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToMime(EmailMessage messageIn, Stream mimeOut, OutboundConversionOptions outboundOptions)
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall)
   at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToMime(MimeDocument documentIn, Stream mimeOut, OutboundConversionOptions outboundOptions)
OutboundConversionOptions:
- preferredCharset: iso-8859-1
- filterOutPersonalInformation: True
- encodeAttachmentsAsBinhex,: False
- suppressDisplayName: False
- internetMessageFormat: Mime
- internetTextFormat: HtmlAndTextAlternative
- imceaEncapsulationDomain: ourdomain.here
- preserveReportBody: True
- byteEncoderTypeFor7BitCharsets: UseQP
- clearCategories: True
- owaServer: 
- logDirectoryPath: C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\PipelineTracing
- isSenderTrusted: True
- dsnWriter: 
- userADSession: 
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- includeBcc: False
- useSimpleDisplayName: False
- partialStnefConversion: False
- preferredInternetCodePageForShiftJis: 0
- filterOutPredecessorChangeList: False
- quoteDisplayNameBeforeRfc2047Encoding: False
- overrideCalendarMessageCharset: 
ConversionLimits:
- maxMimeTextHeaderLength: 2000
- maxMimeSubjectLength: 255
- maxSize: 2147483647
- maxMimeRecipients: 12288
- maxRecipientPropertyLength: 2000
- maxBodyPartsTotal: 250
- maxEmbeddedMessageDepth: 100
- exemptPFReplicationMessages: True 

Since I was suspecting that this was an issue that is related to the .NET Framework, I have installed the latest Frameworks as well as run sfc /scannow to no avail.
 
After this, I tried to (1) roll back all of the updates to what it was before and (2) install the latest updates for everything Microsoft related on the system, again, to no avail.
 
I also found that I cannot reinstall .NET Framework 2.0 as the system seems to be referencing the 2.0 Framework.
 
What can I do to fix this issue?
 
Thanks.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros