index > Team Foundation Server - Reporting > Having trouble deploying to the report server

Having trouble deploying to the report server

Tried every combination with and without SSL, using reports and reportserver - cannot get it to deploy. Tried target folder the same name as my report project and the same name as my team project - still no luck - what am I missing?TITLE: Microsoft Report Designer------------------------------A connection could not be made to the report server https://vstudio01:8143/reportserver.------------------------------ADDITIONAL INFORMATION:The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. (System.Web.Services)------------------------------The remote certificate is invalid according to the validation procedure. (System)------------------------------BUTTONS:OK------------------------------

Cade Roux

Hi Cade, did you try http://vstudio01 (not https, no port)? Is your report server configured to support HTTPS, take in consideration that even if you setup your Team Foundation Server to use HTTPS doesn't mean that Sharepoint and Report server are using HTTPS, those need to be configured separately.

Federico Kolliker Frers - MSFT

TITLE: Microsoft Report Designer
------------------------------

A connection could not be made to the report server http://vstudio01/.

------------------------------
ADDITIONAL INFORMATION:

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

------------------------------

The request failed with HTTP status 404: . (Microsoft.ReportingServices.Designer)

------------------------------
BUTTONS:

OK
------------------------------

Cade Roux

This is a bit outside of my domain - Reporing Services may be able to help faster (forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=82&SiteID=1)

One thing you could try is setting the ReportServerUrl to the fully-qualified domain name of the server for which your SSL certificate was issued. From

http://msdn2.microsoft.com/en-us/library/ms159261.aspx

"If a Secure Sockets Layer (SSL) certificate is installed, this value must be the name of the server that is registered for that certificate. If you get the error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel", set ReportServerUrl to the fully-qualified domain name of the server for which the SSL certificate was issued. For example, if the certificate is registered to https://adventure-works.com.onlinesales, the report server URL would be https://adventure-works.com.onlinesales/reportserver. "

Let me know if this helps.

Nick Ericson - MSFT

I am pretty sure this was the first combination of https and the FQDN hostname I tried, but I tried again and it worked today:

------ Build started: Project: Dev_Team_Mgmt, Configuration: Production ------
Build complete -- 0 errors, 0 warnings
------ Deploy started: Project: Dev_Team_Mgmt, Configuration: Production ------
Deploying to https://vstudio01.orthodon.com/reportserver/
Deploying data source '/Data Sources/TfsSAS'.
Deploying data source '/Data Sources/TfsWarehouse'.
Deploying data source '/Data Sources/TfsWIT'.
Deploying report '/Dev_Team_Mgmt/Cade - Active Work Items'.
Deploying report '/Dev_Team_Mgmt/Warehouse Report'.
Deploy complete -- 0 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Cade Roux

reply 5