September 28, 2010 at 1:26 pm
Hey guys,
I'm a bit new with SSRS. I have inherited two reporting servers that are about 5 years behind on patching and have a few other issues that need to be looked at. The first thing I tried to do was fire up SSMS and connect to the reporting server instance to check some of the server properties/etc.
When I try to connect though, I get the following error message:
The underlying connection was closed: An unexpected error occurred on a send. (System.Web.Services)
The handshake failed due to an unexpected packet format. (System)
This is using SSMS on the local report server machine. I have tried using the hostname, ip, localhost, '.'...no difference. Does anyone have any ideas as to where I should start here?
Thanks in advance
September 28, 2010 at 2:23 pm
Can you connect with the Report Manager web admin tool?
Did you try to connect with an account that has appropriate permissions to the SSRS instance?
What about from a remote machine? Perhaps the client tools were not updated but the SSRS instance was at some point?
-Luke.
September 28, 2010 at 3:50 pm
You might try using the URL in the server name when connecting via SSMS.
http://<SERVERNAME>/reportserver
If I remember correctly this had to be done to work around an issue with SSMS 2008 connecting to RS 2005.
September 28, 2010 at 3:53 pm
Thanks Ed - that did it. I'm using SSMS 2005 (installed at the same time as RS) directly on the report server, so it's not just an SSMS 2008 issue apparently. I can connect from both boxes now using the full URL though.
Also thanks Luke - I missed your reply earlier.
November 19, 2014 at 9:10 am
Thanks for the post about putting the http://<ServerName>:<port>/ReportServer in the 'Server name:' when connecting to the report server via SSMS. This worked for me when connecting to the Report Server in SSMS 2008 R2.
I needed to connect from SSMS on the DB server when the Report Server was on a Web Server. The Web Server did not have SSMS installed.
Thanks!!!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply