Wednesday, March 28, 2012
ReportViewer 2005 control and Soap versions
ReportViewer control within our applications.
Whilst this works OK on most sites, one or two cannot render any
reports, but get the cryptic message
"Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'"
and then shows some well formed XML beneath it.
They are all running the same versions of the applications, to the same
single report server, but some have to go through different firewalls.
They can all reach our servers as they can all make web service calls
sucessfully.
I think that something is stripping out the SOAP wrapper from around
the request/response but I cannot get any futher.
Does anyone know what version of SOAP the underlying RS communication
is using - I think the old viewer used SOAP 1.1 - and I thought that
the new control used SOAP vserson 1.2As an additional request....
Has anyone been able to turn IIS tracing on for the ReportServer
directory so you can use TRACE.AXD to see what message data is going
too and from the reportserver site ?
ReportServers own logs, even on verbose, only show what is is doing
after it has parsed the request, and the IIS logs only show a request
being made, not the request contents.
When I try \\localhost\ReportServer\trace.axd it just shows the
subdirectory structure and not the normal tracing web page I would have
expected.
Friday, March 23, 2012
ReportServer giving me a 404?
I uninstalled sql 2000 from one of my boxes after having problems running sql 2005 along side it.. I actually uninstalled both versions and deleted all the folder in the MS SQL Server folder within program files. At least the ones I could..it did tell me that some fiels were still in use?
Anyway I re-installed only sql 2005 with analysis and reporting services being my focus. Of course reporting services is the one that is giving me trouble.
I am running of windows server 2003 enterprise and of course everything else I am supposed to have.
Problem:
If I attempt to browse the reports directory it works fine...at least the page does not sure if it si making a connection to teh database but I assume it is. However, when trying to brose to the ReportServer I get a 404? I dont understand ...I changed the service account it was being ran under in the Reporting Services configuration but that failed to make a connection at all.
Can anyone give me some info needed on what could be going wrong here?
Thanks in advance!
Michael
Can you check IIS to see that the ReportServer virtual directory is properly configured? You can probably compare with a fresh install on a different machine to make sure things look ok.|||Im sorry but can you please be a little more specific?The virtual directories reportserver and reports were both automatically created. I havent had this problem in the past. Everything looks good...running on .net 2.0...everything looks good.
The only thing I can think of is the accounts the service is running on maybe? Local System. If I use adminitrator it tells me service unavailable. Its is a domain controller also.
Thank you,
Michael|||
I am having the same problem
Here is the error msg that I am getting when I try to deploy sample report project
TITLE: Microsoft Report Designer
A connection could not be made to the report server http://localhost/MYSERVER
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)
The request failed with HTTP status 404: Not Found. (Microsoft.ReportingServices.Designer)
BUTTONS:
OK
Any idea anyone?
|||This is a different problem dude...post a new one.|||Did you confirm in the IIS settings that the "Reports" virtual directory is actually created and mapped to the appropriate location within Program Files\Microsoft SQL Server\<instance>\Reporting Services\ReportManager?
Can you get to http://localhost/Reports/Pages/Folder.aspx?
Also check the IIS logs to see specifically which URL we are failing on. http://localhost/Reports should be configured to load "home.aspx" as the default page, and that guy redirects to Pages/Folder.aspx. Make sure that they are both there. If all of the files under ReportManager are there, then most likely the issue is that IIS is somehow not configured correctly.
Can you be more specific about the service unavailable message you are receiving?
Have you tried running the Configuration Tool?