Dear sir,
I installed a copy of SQL Server 2005 Evaluation Edition in my XP Professional Computer. When I try to connect to Report Service using Management Studio, it fails to connect with the following error:
**********************************************
TITLE: Connect to Server
------------------------------
Cannot connect to XXXXXXXXXXXX
------------------------------
ADDITIONAL INFORMATION:
The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.SqlServer.Management.UI.RSClient)
**********************************************
I have no problem connect to other services.
Also, I can connect to the Report Manager using IE brower and use all the functions without problem. Actually I failed to connect to the Report Manager before because I got the following error as seen in the event viewer:
"Failed to execute the request because the ASP.NET process identity does not have read permissions to the global assembly cache. Error: 0x80070005 Access is denied. "
I solved the problem by adding the ASPNET account to the "Administrators" group
Anyway, do you have any advice on how to successfully connect the Report Services in Management Studio
Pls help!!!!~~
Thanks in advance
Fail to Connect Report Service via Management Studio
fan
Solution is still not found yet.
mike todd
Don't know if this is exactly the same, but the same error message appears, so it might help. Check out the following link:
http://programcsharp.com/blog/archive/2005/10/04/7595.aspx
I ran into the message when I set up a restricted web application on my server so that only the administrative personnel could get in and see the new material before it went totally live. Seems that when I restricted it to Windows Authentication and then set the directory restriction to System and Admins, I forgot to allow localmachine\ASPNET have access as well. The moment I gave the account Read/Execute rights to the application directory, it worked.
Reading the blog above shows someone else ran into the same problem when they installed FPSE on their IIS machine, it set the directory rights for them and removed ASPNET. Another scenario is when the local IT folks decide it is in yours and their best interest to screw with the rights without telling you
.
Anyways, just go to your application directory and give the ASPNET account the proper rights and you should be good to go.
HTH, Jim
Nevil
millerfjtp
Have you encountered this error
Request failed with Http status 502: Bad Gateway. (Microsoft.SQLServer.Management.UI.RSClient
This happens when I try to connect to reporting server using the management studio on the local server while using both server name and ip address as the name of the server
Ted Hoffman
Thanks for your reply, Brian.
Do you mean i need to type http://servername/reportserver in the Server name field inside the Management Studio That is:
Server type: Report Services
Server name: http://servername/reportserver
Authentication: Windows Authentication
I just tried but same error is produced.
jclausius
I had the same problem. This is what I did to resolve the issue.
Server Type : Reporting Services
Server Name : http://localhost/reportserver
Authentication : Basic Authentication
User name : <used valid local user name>
Password : <enter valid password>
Remember Password <checked>
That seem to do the trick.
Chittesh
I have the same problem. May be you have found the right solution
Thanks
ghostman
jungleKing
<configuration>
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true" />
</settings>
</system.net>
</configuration>
Saw this as a fix for another product... maybe try this in one of the reporserver.config files
Slater
Anandba - MSFT