Assume that you have an RDL report (.rdl) file whose file name contains a non-Latin character in Microsoft SQL Server 2012 Reporting Services (SSRS 2012). You define an email subscription for the report, and then you deliver the report. In this situation, the report cannot be delivered by email. Additionally, you receive the following error message in the Status
column of the Subscriptions
details when you check the properties of the report:
Failure sending mail: An invalid character was found in header value. Mail will not be resent.
When this issue occurs, the following exception is logged in the SSRS error log:
emailextension!WindowsService_0!990! Date Time:: e ERROR: Error sending email. Exception: System.FormatException: An invalid character was found in header value.
at System.Net.Mime.HeaderCollection.Set(String name, String value)
at System.Net.Mime.MimeBasePart.set_ContentID(String value)
at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.AddStreamToBodyPart(MailMessage message, Stream stream, String fileName, String contentMediaType, String contentDisposition)
at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.AttachReport(MailMessage message, RenderedOutputFile reportData)
at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.ConstructMessageBody(MailMessage message, Notification notification, SubscriptionData data)
at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.CreateMessage(Notification notification)
at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Notification notification)
Cumulative update information
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative Update 3 for SQL Server 2012
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, use only Latin characters in your report file name.
For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates