Showing posts with label ssl. Show all posts
Showing posts with label ssl. Show all posts

Friday, March 9, 2012

Problem Deploying Reports when using SSL

Here is my current setup. I have Report Services sp1 installed on a Windows
2000 machine with SQL Server 2000. We have successfully configured RS to
produce reports over the internet via SSL. The actual viewing of the report
over the internet works great. However, in Visual Studio I receive the
following error when trying to deploy the reports...
"The underlying connection was closed. Could not establish trust
relationship with remote server"
The only work around I have found so far is to modify the
rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
Then I am able to deploy the reports and do not receive this message.
Because SSL is a must, I then have to change the secureconnectionlevel= back
to 2.
Users externally are accessing the report server via
http://FQDN/reportserver. I had gone into the rswebapplication.config file
and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl> to
<ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck. My
certificate name uses the FQDN as the site name.
My question is why I am not able to deploy my reports when the SSL is turned
on?
I hope this makes sense and I am sure I left something out. Please let me
know your thoughts. Thanks!Sounds like you're hitting the issue in this KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;823177. Are you
specifying the FQDN in VS when deploying the reports?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:B42B3849-C5FA-45AB-AEDA-D769D49ED57D@.microsoft.com...
> Here is my current setup. I have Report Services sp1 installed on a
> Windows
> 2000 machine with SQL Server 2000. We have successfully configured RS to
> produce reports over the internet via SSL. The actual viewing of the
> report
> over the internet works great. However, in Visual Studio I receive the
> following error when trying to deploy the reports...
> "The underlying connection was closed. Could not establish trust
> relationship with remote server"
> The only work around I have found so far is to modify the
> rsreportserver.config file and change secureconnectionlevel= from 2 to 0.
> Then I am able to deploy the reports and do not receive this message.
> Because SSL is a must, I then have to change the secureconnectionlevel=> back
> to 2.
> Users externally are accessing the report server via
> http://FQDN/reportserver. I had gone into the rswebapplication.config
> file
> and changed <ReportServerUrl>http://server/reportserver<ReportServerUrl>
> to
> <ReportServerUrl>http://FQDN/reportserver<ReportServerUrl> but no luck.
> My
> certificate name uses the FQDN as the site name.
> My question is why I am not able to deploy my reports when the SSL is
> turned
> on?
> I hope this makes sense and I am sure I left something out. Please let me
> know your thoughts. Thanks!
>

Problem deploying reports from VS.NET with SSL

Hi.
I'm using Reporting services for my company's web site and it worked fine
until I tried to activate SSL : now when I try to deploy new reports from
VS.NET I'm asked to login to https://www.mysite.com/reportserver and no
credentials are accepted.
Debugging from VS.NET I can see a call without SSL (http instead of https),
although I changed http in https everywhere.
Can somebody give me some help ?
ThanksNot sure if this solves your problem, but have you tried running rsconfig?
It would be something like:
rsconfig -c -s https://www.mysite.com -d ReportServer -a Windows -u
domain\username -p password
Pieter van Maasdam
Macaw B.V.
"Moreno" <movendra@.yahoo.com> wrote in message
news:eMXvt6ThEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi.
> I'm using Reporting services for my company's web site and it worked fine
> until I tried to activate SSL : now when I try to deploy new reports from
> VS.NET I'm asked to login to https://www.mysite.com/reportserver and no
> credentials are accepted.
> Debugging from VS.NET I can see a call without SSL (http instead of
https),
> although I changed http in https everywhere.
> Can somebody give me some help ?
> Thanks
>

Problem deploying reports

Apologies in advance, newbee to SQL Server and Reporting Services...
Installed Reporting Services in TEST environment (without SSL). I can author
a report, view the data from the data source and preview successfully.
However, I receive the following error message when trying to Deploy a
Solution from within Visual Studio Report Designer..."The underlying
connection was closed: Unable to connect to the remote server."
I can navigate to both the Report Manager and Report Server pages
successfuly using IE. Following the deployment failure the Report Manager
contains the new folder to which I was attempting to deploy the report but
it's empty (no report).
Any help would be appreciated.
Thanks,
Chris.In Report Manager, can you simply click on Upload File? Then you can upload
an RDL file manually.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Chris W, AgriBank" <ChrisWAgriBank@.discussions.microsoft.com> wrote in
message news:96862E2B-8F7C-422F-8A6E-71C86897BB60@.microsoft.com...
> Apologies in advance, newbee to SQL Server and Reporting Services...
> Installed Reporting Services in TEST environment (without SSL). I can
> author
> a report, view the data from the data source and preview successfully.
> However, I receive the following error message when trying to Deploy a
> Solution from within Visual Studio Report Designer..."The underlying
> connection was closed: Unable to connect to the remote server."
> I can navigate to both the Report Manager and Report Server pages
> successfuly using IE. Following the deployment failure the Report Manager
> contains the new folder to which I was attempting to deploy the report but
> it's empty (no report).
> Any help would be appreciated.
> Thanks,
> Chris.|||hey chris,
i m having the same issue .. are u able to resolve it ..
Please post ur comments if u know the solutions..
Thanks
SR
"Chris W, AgriBank" wrote:
> Apologies in advance, newbee to SQL Server and Reporting Services...
> Installed Reporting Services in TEST environment (without SSL). I can author
> a report, view the data from the data source and preview successfully.
> However, I receive the following error message when trying to Deploy a
> Solution from within Visual Studio Report Designer..."The underlying
> connection was closed: Unable to connect to the remote server."
> I can navigate to both the Report Manager and Report Server pages
> successfuly using IE. Following the deployment failure the Report Manager
> contains the new folder to which I was attempting to deploy the report but
> it's empty (no report).
> Any help would be appreciated.
> Thanks,
> Chris.

Monday, February 20, 2012

Problem consuming SQL Server SSL Endpoint

I try to consume a SSL Endpoint that is locate in localhost, but i get the follow error msg:

The underlying connection was closed: An unexpected error occurred on a receive.

m_safeCertContext is an invalid handle.

I do not know what gone wrong with my VS2005, i tried in IE with https://localhost/test?wsdl, and it was okay and display the wsdl document successfully. Beside i also tried with CLEAR port, everything is ok and i managed to consume the web service too.

any suggestion would be appreciated. Thank q

You might have more luck asking in the Visual Studio Forum for this. Seems to be a VS issue. However, looking at some of the forums, I was able to find http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=232760&SiteID=1.

HTH

Riyaz

|||

I would also recommend specifying the machine name in the URL in your VS2005 application. I would imagine that the SSL certificate installed on the SQL Server machine is issued to the machine name and not "localhost". One possibility is that since you specified "localhost" in the URL, Visual Studio may be trying to validate the SSL certificate info (machine name) against "localhost" which do not match; thus causing the error.

Jimmy