I migrated an installation of Reporting Services 2005 running on Windows Server 2003 Std. 32Bit to a new server running Windows Server 2008 Enterprise 32Bit (not 2008 R2) with SQL Server and Reporting Services 2012.
Everything worked fine until we tried to run the reports from our application which has a custom class that run the reports. They work fine in 2005 but won't work in 2012.
The specific error is:
Client found response content type of '', but expected 'text/xml'.
The error is thrown in the method:
[System.Web.Services.Protocols.SoapHeaderAttribute("SessionHeaderValue", Direction=System.Web.Services.Protocols.SoapHeaderDirection.InOut)]
[System.Web.Services.Protocols.SoapHeaderAttribute("ServerInfoHeaderValue", Direction=System.Web.Services.Protocols.SoapHeaderDirection.Out)]
[System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://schemas.microsoft.com/sqlserver/2003/12/reporting/reportingservices/Render" +
"", RequestNamespace="http://schemas.microsoft.com/sqlserver/2003/12/reporting/reportingservices", ResponseNamespace="http://schemas.microsoft.com/sqlserver/2003/12/reporting/reportingservices", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
[return: System.Xml.Serialization.XmlElementAttribute("Result", DataType="base64Binary")]
public System.Byte[] Render(string Report, string Format, string HistoryID, string DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, string ShowHideToggle, out string Encoding, out string MimeType, out ParameterValue[] ParametersUsed, out Warning[] Warnings, out string[] StreamIds) {
object[] results = this.Invoke("Render", new object[] {
Report,
Format,
HistoryID,
DeviceInfo,
Parameters,
Credentials,
ShowHideToggle});
Encoding = ((string)(results[1]));
MimeType = ((string)(results[2]));
ParametersUsed = ((ParameterValue[])(results[3]));
Warnings = ((Warning[])(results[4]));
StreamIds = ((string[])(results[5]));
return ((System.Byte[])(results[0]));
}
Again, this is working fine against the 2005 SSRS but not the 2012 SSRS.
Any ideas what might be the issue? Any help would be appreciated.
Thanks. Jose