text/xml reporting service error

[RdS]

Hello,

I use sourcesafe and vb 2003 for my dev environment. on the sourcesafe
server I also have sql2005 and reporting services installed. The web app
references this sql server for db. When I compile the app on my local
machine which is used for development I am able to lauch application with no
problem. When I run my web app on my local machine which uses my IIS 5
(WinXP Pro) the application runs fine. But if I connect to server where
code is actually stored and run from that machine I receive the following
error. The error is with the reportingservice.asmx proxy I have in my code.
what is the problem and how do I correct? thanks.

Client found response content type of '', but expected 'text/xml'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Client found response
content type of '', but expected 'text/xml'.

Source Error:

Line 554: "",
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)> _
Line 555: Public Function Render(ByVal Report As String, ByVal Format
As String, ByVal HistoryID As String, ByVal DeviceInfo As String, ByVal
Parameters() As ParameterValue, ByVal Credentials() As
DataSourceCredentials, ByVal ShowHideToggle As String, ByRef Encoding As
String, ByRef MimeType As String, ByRef ParametersUsed() As ParameterValue,
ByRef Warnings() As Warning, ByRef StreamIds() As String) As
<System.Xml.Serialization.XmlElementAttribute("Result",
DataType:="base64Binary")> Byte()
Line 556: Dim results() As Object = Me.Invoke("Render", New
Object() {Report, Format, HistoryID, DeviceInfo, Parameters, Credentials,
ShowHideToggle})
Line 557: Encoding = CType(results(1), String)
Line 558: MimeType = CType(results(2), String)

Source File: C:\Inetpub\wwwroot\AIL_2003\Framework\ReportingService.vb
Line: 556

 

[Steven Cheng[MSFT]]

Hello RdS,

Welcome to the MSDN newsgroup.

From your description, I understand you have a web application(ASP.NET)
which will connect to a remote SQL Server 2005database. The SQL Server 2005
instance also has reporting service installed and your web application will
use webservice SOAP api to query report from the SQL 2005 reporting
service. However, you found the web application run well on some machines,
but failed with a

"System.InvalidOperationException: Client found response content type of
'', but expected 'text/xml'."

error on some others, correct?

As for this issue, I'm still having some unclear points on your
application's environment. Currently how many machines are there involved
in this application. ( I assume that there is only two, the web
application's server and the SQL Server 2005 server, right?). Also, as
you mentioned:

==============
When I run my web app on my local machine which uses my IIS 5
(WinXP Pro) the application runs fine. But if I connect to server where
code is actually stored and run from that machine I receive the following
error.
==================

I'd appreciate if you can provide some further description on the two
condition(one works and the other fails). Especially the " if I connect to
server where code is actually stored and run from that machine", what does
the "connect to server" mean, are you connecting the IIS virtual directory
to the remote server(through file share) or is the "connect" just means
data access connection to a remote server?

Generally, as for such "System.InvalidOperationException: Client found
response content type of '', but expected 'text/xml'." exception, it is
likely caused by the remote webservice didn't return the expected response
content (SOAP response message of text/xml format). Therefore, for generic
troubleshooting, you can consider using some http/tcp trace tools to
capture the webservcie request/response message to see whether they're of
the correct format or content. There are some well-known trace tools such
as tcpTrace or the trace utility in the soap toolkit 3.0(you can get it
through the following link):

http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4088-
9753-86F052EC8450&displaylang=en


In addition, based on my research over the web, there has been some
similiar issues with the same error you encountered and most of them are
caused by the webservice client proxy is pointing to an incorrect service
endpoint( the target servcie Url). So you can also check your webservcie
client proxy's "Url" property to see whether it points to the correct
service endpoint. For your scenario, since your reporting service proxy is
calling the "Render" method, it should belongs to the execution Service ,
its end point should be something like:

http://server/reportserver/ReportExecution2005.asmx

rather than the

http://server/reportserver/ReportService2005.asmx

which is mainly for management webservice apis.

Please have a look at the above items. If there is anything unclear on
this, please feel free to post here. Hope this helps you some.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Steven Cheng[MSFT]]

Hello RdS,

How are you doing on this issue? Have you got any progress or does my last
reply helps you a little on this? If there is anything else we can help,
please feel free to post here.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)