deploy a report to report server in SQL 2k5

I have made a report using Business Intelligence Development Studio in
SQL2005. When I deploy that report the report server, I got the error:
****************************************************************************************************************************
A connection cannot not be made to the report server http://servername.
Addition Information:
The server committed a protocol violation. Section=ResponseHeader detail=CR
must be followed by LF (System.Web.Service)
******************************************************************************************************************************************************
Then I use IE to open http://servername/reportserver , I get the following
message:
Server Error in '/ReportServer' Application.
----
Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>Can anyone please help? I am desperate.
" 00 Michael Jordan" <a@.b.com> wrote in message
news:u2kvq7SEIHA.1184@.TK2MSFTNGP04.phx.gbl...
>I have made a report using Business Intelligence Development Studio in
> SQL2005. When I deploy that report the report server, I got the error:
> ****************************************************************************************************************************
> A connection cannot not be made to the report server http://servername.
> Addition Information:
> The server committed a protocol violation. Section=ResponseHeader
> detail=CR
> must be followed by LF (System.Web.Service)
> ******************************************************************************************************************************************************
> Then I use IE to open http://servername/reportserver , I get the
> following
> message:
>
> Server Error in '/ReportServer' Application.
> ----
> Runtime Error
> Description: An application error occurred on the server. The current
> custom
> error settings for this application prevent the details of the application
> error from being viewed remotely (for security reasons). It could,
> however,
> be viewed by browsers running on the local server machine.
> Details: To enable the details of this specific error message to be
> viewable
> on remote machines, please create a <customErrors> tag within a
> "web.config"
> configuration file located in the root directory of the current web
> application. This <customErrors> tag should then have its "mode" attribute
> set to "Off".
> <!-- Web.Config Configuration File -->
> <configuration>
> <system.web>
> <customErrors mode="Off"/>
> </system.web>
> </configuration>
> Notes: The current error page you are seeing can be replaced by a custom
> error page by modifying the "defaultRedirect" attribute of the
> application's
> <customErrors> configuration tag to point to a custom error page URL.
> <!-- Web.Config Configuration File -->
> <configuration>
> <system.web>
> <customErrors mode="RemoteOnly"
> defaultRedirect="mycustompage.htm"/>
> </system.web>
> </configuration>
>|||we have the same problem.we want to give a custom message if any error
occured in Reporting Service.So,pls help.......
"00 Michael Jordan" wrote:
> Can anyone please help? I am desperate.
>
> " 00 Michael Jordan" <a@.b.com> wrote in message
> news:u2kvq7SEIHA.1184@.TK2MSFTNGP04.phx.gbl...
> >I have made a report using Business Intelligence Development Studio in
> > SQL2005. When I deploy that report the report server, I got the error:
> >
> > ****************************************************************************************************************************
> > A connection cannot not be made to the report server http://servername.
> >
> > Addition Information:
> >
> > The server committed a protocol violation. Section=ResponseHeader
> > detail=CR
> > must be followed by LF (System.Web.Service)
> >
> > ******************************************************************************************************************************************************
> >
> > Then I use IE to open http://servername/reportserver , I get the
> > following
> > message:
> >
> >
> >
> > Server Error in '/ReportServer' Application.
> > ----
> >
> > Runtime Error
> > Description: An application error occurred on the server. The current
> > custom
> > error settings for this application prevent the details of the application
> > error from being viewed remotely (for security reasons). It could,
> > however,
> > be viewed by browsers running on the local server machine.
> >
> > Details: To enable the details of this specific error message to be
> > viewable
> > on remote machines, please create a <customErrors> tag within a
> > "web.config"
> > configuration file located in the root directory of the current web
> > application. This <customErrors> tag should then have its "mode" attribute
> > set to "Off".
> >
> > <!-- Web.Config Configuration File -->
> >
> > <configuration>
> > <system.web>
> > <customErrors mode="Off"/>
> > </system.web>
> > </configuration>
> >
> > Notes: The current error page you are seeing can be replaced by a custom
> > error page by modifying the "defaultRedirect" attribute of the
> > application's
> > <customErrors> configuration tag to point to a custom error page URL.
> >
> > <!-- Web.Config Configuration File -->
> >
> > <configuration>
> > <system.web>
> > <customErrors mode="RemoteOnly"
> > defaultRedirect="mycustompage.htm"/>
> > </system.web>
> > </configuration>
> >
>
>