URGENT FIX REQUIRED: A storage transient failure has occurred during content conversion.
-
Sunday, February 24, 2013 6:24 AM
Hello,
Please help, basically we have the same issue as the following post, only the proposed answer is not the final answer and the issue persists:
Environment:
Windows Server 2012 DC edition
Exchange 2013 Std edition
Outlook 2013 (Office 2013 Std edition)
No Malware protection enabled within Exchange 2013
No Antivirus application on Windows ServerIssue:
Same problem experienced with two separate installations, random e-mails are stuck in the Exchange Submission Queue with Delivery Type Undefined and retry error "A storage transient failure has occurred during content conversion."Workaround:
Running the following command will clear the queue but causes adverse effects:Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $true
Would be great if Microsoft could help out here, we are sort of stretching relationships with our customers..Regards,
Lyndon.
All Replies
-
Tuesday, February 26, 2013 2:58 AMModerator
Hi Lyndon,
The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Format (TNEF) message encoding is used on messages sent to the remote domain.
Set-RemoteDomain:
http://technet.microsoft.com/en-us/library/aa997857(v=exchg.150).aspx
More information for your reference.
A storage transient failure has occurred during content conversion:<//span>
Wendy Liu
TechNet Community Support
-
Tuesday, February 26, 2013 5:03 AM
Thank you Wendy for your response, although this is till not the definitive answer I am after.
I have done a fair amount of research into the TNEF settings and would prefer to use the default setting $Null.
Although this issue keeps re-occurring for a couple of random messages a day, so changing the TNEF setting manually each day will get annoying real quick..
From previous forum posts we are not the only ones experiencing this issue, and we are yet to determine if it is an Exchange 2013, Outlook 2013, Windows 2012 etc. issue.
Although we have various setups for different companies, we are yet to see this issue on Exchange 2010SP2 with Outlook 2010 or 2013.
I believe that Microsoft will release a fix soon to resolve this issue, but I feel it necessary to keep drawing attention to this until the fix is out.. or until some genius out there can help us.. please.. =]
Regards,
Lyndon. -
Wednesday, February 27, 2013 3:42 PMAnyone? =/
-
Monday, March 18, 2013 12:29 PM
I had the same issue and have been looking into this for a few days now. So far I have been able to reproduce the problem, but I have no yet figured a acceptable solution yet.
I have a Windows 2012 server with Exchange 2013 installed, using Outlook 2010 for testing so far.
I see the issue if we embed image files in the emails, either via signature or if I just copy paste the image in the email. The issue is limited to either replies or meeting invitations, so I guess that Outlook refuses or fails to convert the emails from RTF to html.
If I use webmail the issue is not there, so I guess it is somehow related to the Outlook 2010 and I'll try testing with Outlook 2013.
*Edit*
Both Outlook 2007 and 2013 have this issue, so seems like we will have to wait untill Microsoft fixes this.
- Edited by Søren Farsø Monday, March 18, 2013 1:21 PM
-
Tuesday, March 19, 2013 8:04 AM
Thanks for the reply and extra diagnostic info Søren.
One of our Exchange 2013 servers has been behaving itself with the TNEF $False setting, although one still persists with this issue.
Still waiting quite patiently for Microsoft to sort their *bleep* out... =]
Regards,
Lyndon -
Tuesday, March 19, 2013 8:12 PM
This issue would happen when You are running Exchange 2013 on Windows 2012 and the sender is sending the message in Rich text format. The only way to go around this is to send the messages in HTML/Plain text format from the client. This issue is expected to be fixed in CU1 release.
-PSS
-
Wednesday, April 03, 2013 8:27 PM
This problem is also present with Exchange 2010 SP3 on Windows Server 2012.
We upgraded this weekend to Server 2012 with Exchange 2010 and after the upgrade we are not able to sent emails from outlook 2007, 2010 & 2013 using Rich Text format.
But sending using HTML is not a problem.
Raoul.
-
Monday, April 08, 2013 11:10 AM
Hello All,
So far so good with Cumulative update 1 for Exchange Server 2013 (KB2816900).
http://www.microsoft.com/en-us/download/details.aspx?id=38176
Regards,
Lyndon.
- Marked As Answer by LyndonR Monday, April 08, 2013 11:11 AM
-
Friday, April 19, 2013 12:28 AM
Having the same issue with Windows Server 2012 and Exchange 2010 SP3.
Even if I change the email from RTF to HTML, it still gets stuck in the Queue and is labeled DEFER.
-
Monday, May 20, 2013 7:01 PMDid you find a fix for this?
-
Tuesday, May 21, 2013 1:32 AM
I went with this:
Set-RemoteDomain -Identity * -TNEFEnabled:$true
It works - haven't had any reports of problems, other than maybe a signature in an email that was broken (missing images), but can't say this was the cause.
-
Tuesday, May 21, 2013 11:26 PM
this worked for me as well. exchange 2010 SP2 on windows server 2012.
Set-RemoteDomain -Identity * -TNEFEnabled:$true
checked outgoing mail and it all seems to be fine just has the winmail.dat now but checking the actualy email itself in a client(outlook) it seems fine.
.png)
