RS2005 Standard install error..

I am installing SQL 2005 and RS 2005 on a new W2k3 server. I have tried to
install to a default instance and to a named instance and continue to get the
following error when I try to retrieve the reports page or connect to the
reporting services thru Microsoft SQL server Management Studio.
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version.
In the Log file ReportServerWebApp__01_03_2006_13_51_00.log I see:
w3wp!ui!7!1/3/2006-12:01:32:: e ERROR: The attempt to connect to the report
server failed. Check your connection information and that the report server
is a compatible version.
w3wp!ui!7!1/3/2006-12:01:33:: e ERROR: HTTP status code --> 500
--Details--
Microsoft.SqlServer.ReportingServices2005.RSConnection+MissingEndpointException:
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version. -->
System.Net.WebException: The request failed with HTTP status 404: Not Found.
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at
Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
methodname)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
-- End of inner exception stack trace --
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
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.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!7!1/3/2006-12:01:34:: 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)Did anyone find a solutions to this issue, i have encountered the same
problem, and cannot seem to get it to work.
Thanks
Jim wrote:
> I am installing SQL 2005 and RS 2005 on a new W2k3 server. I have tried to
> install to a default instance and to a named instance and continue to get the
> following error when I try to retrieve the reports page or connect to the
> reporting services thru Microsoft SQL server Management Studio.
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version.
>
> In the Log file ReportServerWebApp__01_03_2006_13_51_00.log I see:
>
> w3wp!ui!7!1/3/2006-12:01:32:: e ERROR: The attempt to connect to the report
> server failed. Check your connection information and that the report server
> is a compatible version.
> w3wp!ui!7!1/3/2006-12:01:33:: e ERROR: HTTP status code --> 500
> --Details--
> Microsoft.SqlServer.ReportingServices2005.RSConnection+MissingEndpointException:
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version. -->
> System.Net.WebException: The request failed with HTTP status 404: Not Found.
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
> at
> Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
> methodname)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> -- End of inner exception stack trace --
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> 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.Page.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> w3wp!ui!7!1/3/2006-12:01:34:: 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)|||I'm experiencing the same problems, you might think it has something to do
with SSL, but it is not necessary to use it, is it?
I would be very pleased with some help regarding this subject!|||Why are no microsoft people responding to these posts? Thought that was the
deal with this support option via msdn?
I'm having the same issue and have yet to get report manager to work via
http://servername/reports.
--
Thanks,
Chris.
"Ruud0011" wrote:
> I'm experiencing the same problems, you might think it has something to do
> with SSL, but it is not necessary to use it, is it?
> I would be very pleased with some help regarding this subject!|||I've had this same issue. I installed RS2005 and VS2005 on a new Windows
2003 server. This was not an upgrade. I am using an SSL certificate and
edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportManager\RSWebApplication.config file by removing the entry for
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
The ReportURL entry looks like this
ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
it says "reportserver" and not reports which is why I kept getting the same
error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportServer\RSReportServer.config file was edited to reflect the
SecureConnectionLevel Value 3 and the URLRoot was
https://localhost/reportserver
All is well. No more error messages.
WMH
"whoopdaddy" wrote:
> Why are no microsoft people responding to these posts? Thought that was the
> deal with this support option via msdn?
> I'm having the same issue and have yet to get report manager to work via
> http://servername/reports.
> --
> Thanks,
> Chris.
>
> "Ruud0011" wrote:
> > I'm experiencing the same problems, you might think it has something to do
> > with SSL, but it is not necessary to use it, is it?
> >
> > I would be very pleased with some help regarding this subject!|||Thanks WMH - I had same problem - just spent a few very frustrating days
trying to fix this until I spotted your advice.
Paddy
"WMH" wrote:
> I've had this same issue. I installed RS2005 and VS2005 on a new Windows
> 2003 server. This was not an upgrade. I am using an SSL certificate and
> edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager\RSWebApplication.config file by removing the entry for
> <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
> The ReportURL entry looks like this
> ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
> it says "reportserver" and not reports which is why I kept getting the same
> error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportServer\RSReportServer.config file was edited to reflect the
> SecureConnectionLevel Value 3 and the URLRoot was
> https://localhost/reportserver
> All is well. No more error messages.
> WMH
>
> "whoopdaddy" wrote:
> > Why are no microsoft people responding to these posts? Thought that was the
> > deal with this support option via msdn?
> >
> > I'm having the same issue and have yet to get report manager to work via
> > http://servername/reports.
> > --
> > Thanks,
> > Chris.
> >
> >
> > "Ruud0011" wrote:
> >
> > > I'm experiencing the same problems, you might think it has something to do
> > > with SSL, but it is not necessary to use it, is it?
> > >
> > > I would be very pleased with some help regarding this subject!|||I feel certain that I missed some important documentation that Microsoft
provided us on this issue, but your "removing the entry for
<ReportServerVirtualDirectory>" is the best information on this error
message. I don't have SSL and the Configuration Tool doesn't fix this problem
when you move the virtual directories to another website. I have wasted
entirely too many hours on this and have actually reloaded our 2003 server
twice. Simply remove the <ReportServerVirtualDirectory> tag and all is well.
Thank you very much for your post!!!
Thanks,
Chris
"WMH" wrote:
> I've had this same issue. I installed RS2005 and VS2005 on a new Windows
> 2003 server. This was not an upgrade. I am using an SSL certificate and
> edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager\RSWebApplication.config file by removing the entry for
> <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
> The ReportURL entry looks like this
> ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
> it says "reportserver" and not reports which is why I kept getting the same
> error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportServer\RSReportServer.config file was edited to reflect the
> SecureConnectionLevel Value 3 and the URLRoot was
> https://localhost/reportserver
> All is well. No more error messages.
> WMH
>
> "whoopdaddy" wrote:
> > Why are no microsoft people responding to these posts? Thought that was the
> > deal with this support option via msdn?
> >
> > I'm having the same issue and have yet to get report manager to work via
> > http://servername/reports.
> > --
> > Thanks,
> > Chris.
> >
> >
> > "Ruud0011" wrote:
> >
> > > I'm experiencing the same problems, you might think it has something to do
> > > with SSL, but it is not necessary to use it, is it?
> > >
> > > I would be very pleased with some help regarding this subject!