When i try to deploy report in a local machine i get message: The underlying connection was closed: An unexpected error occurred on a send.Authentication failed because the remote party has closed the transport stream. In addition i can build or preview report in BI Dev Studio without any errors. But I can't deploy it in BI Dev Studio or run in Report Builder 2.0. --- Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)

Are you able to access report server in IE?

Did you check hte properties for the report project that you're attempting to deploy this report to, that it contains a valid URL for deploying?

Yes, i can access report server in IE. Yes, i'd check properties. (if they were incorrect, I would receive an error like this: Bad request) Anyway I have installed all software (Sql Server + Windows Installer 4.5 + .NET Framework 3.51) on other comp. and could build and deploy any report. Thanks for answers.

The only other thing I can think of right now is if report server is configured for SSL, and the url for the project is not SSL. If you can access the url of the VS project in IE then I'm not sure what's going on with VS.

I'm experiencing the exact same problem, and i'm not running with SSL.

Same for me. I can connect to my Report Server Web Service using IE 8and the urlhttp://computer:8080/reportserverIf I use Builder 2.0 and introduce exactly the same url under Report Builder Options I get the error message about the closed transport stream. The strange thing is that when I press "Save As..." I see the folders at my reporting server. Is just that it will not deploy the report. The computer is my local machine and I am the local administrator.Is Builder 2.0 using my credentials or does it use something different?Thanks for any help

Ran across the same issue. Was not running SSL on my local machine. Once I updated the rsreportserver.config to use an non-secure connection all was good. See http://dinesql.blogspot.com/2009/01/reporting-services-2008-error.html for details.

Updated the rsreportserver.config to a non-secure connection by setting the value from 2 to 0 worked for me. I also have the TargetServerURL set to the ReportServer not Reports.

On the SQL Server Machine, Navigate to \Program Files\SQLServer\MSRS.n \Reporting Services\ReportServer Create a back up copy of rsreportserver.config Open the file rsreportserver.config Edit the Key Value for SecureConnectionLevel. Set this value to 0 Save the file. Restart ReportServer Service **Must have administrator rights to the machine.

Thanks Paul... This help me a lot.... :)

Thanks a lot :)

MAn you are ____!!! thanks!!!

This worked like a charm for me too... :) Thanks a lot!

Tks Very helpful. I had the same problem. Bye Silvio Normey Gómez HP Brazil

Exelent answer!