Showing posts with label connection. Show all posts
Showing posts with label connection. Show all posts

Monday, March 12, 2012

Report Manager Error

I am getting following error when trying to load the Report Manager:
The underlying connection was closed: Unable to connect to the remote
server.
This appears to be related to using SSL. If I point the config files
(RSReportServer.config & RSWebApplication.config) to http instead https and
set the SecureConnectionLevel to 0 I don't get this error; however, I need
use SSL
Does anyone have any ideas on what the problem could be?
Here is the stack trace from the log file:
w3wp!ui!b14!8/26/2004-06:56:32:: e ERROR: The underlying connection was
closed: Unable to connect to the remote server.
w3wp!ui!b14!8/26/2004-06:56:32:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Unable to
connect to the remote server.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!b14!8/26/2004-06:57:19:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)You may need to put in the full domain name of the server in the url in
RSWebApplication.config.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jason Nissen" <Jason.Nissen@.cunamutual.com> wrote in message
news:OUaZY02iEHA.556@.tk2msftngp13.phx.gbl...
> I am getting following error when trying to load the Report Manager:
> The underlying connection was closed: Unable to connect to the remote
> server.
> This appears to be related to using SSL. If I point the config files
> (RSReportServer.config & RSWebApplication.config) to http instead https
and
> set the SecureConnectionLevel to 0 I don't get this error; however, I need
> use SSL
> Does anyone have any ideas on what the problem could be?
> Here is the stack trace from the log file:
> w3wp!ui!b14!8/26/2004-06:56:32:: e ERROR: The underlying connection was
> closed: Unable to connect to the remote server.
> w3wp!ui!b14!8/26/2004-06:56:32:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Unable to
> connect to the remote server.
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
> asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!b14!8/26/2004-06:57:19:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
>

Saturday, February 25, 2012

Report in SSRS using cube in SQL 2000

I want to create reports in SSRS that use cube in SQL 2000, I don't know which type of connection that i have to use,

I tested it with Microsoft SQL Analysis Services, means I connect to my cube with this type , everything is ok in developpement (create MDX query , make reports...), but in production It gives me this error message (cannot connect to the datasource),

so I don't know how to solve this problem,

Thanks in advance for your help...,

Regards

Posting the full error message would help.

Posting it in the Reporting Services forum would help even more.

-Jamie