SQL Server Reports getting error - Client found response content type of 'text/html'

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

I am using Sql server 2005 reports. i have deployed my reports to client. But one user getting above error.

Error - Client found response content type of 'text/html', but expected 'text/html'.

The request failed with the error message:
--

XML

<html>
    <head>
        <title>Access Denied</title>
        <style>............

      <td>this site is forbidden accessed through this network</td>.............

Other user can access the reports.

Anything to configure in 'Reporting Services Configuration' ??

Any idea?

In 'Reporting Services Configuration' - Windows service Identity -

Service Name - ReportServer

Service Account - Domain\Administrator

Account Selected is Windows Account - Domain\Administrator

Should we select Built in account - local system?

Posted 2-May-12 22:57pm

Harshada J.

Updated 3-May-12 6:52am

Ganesan Senthilvel

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ganesan Senthilvel · Answer 1 · 2012-05-03T06:54:00

This is happening because there is an unhandled exception in your Web service, and the .NET runtime is spitting out its HTML yellow screen of death server error/exception dump page, instead of XML.

Since the consumer of your Web service was expecting a text/xml header and instead got text/html, it throws that error.

You should address the cause of your timeouts (perhaps a lengthy SQL query?).

Jeff Atwood's blog that explains implementing a global unhandled exception handler and using SOAP exceptions. Ref: http://www.codinghorror.com/blog/2004/08/throwing-better-soap-exceptions.html[^]