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!

RS2005 cant'connect to server

Hi. Like some others here, I'm struggling to get a production install of
RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
database is on a separate SQL 2005 (SP2) server. With the help of some posts
here I finally am able to browse to Report Manager and also deploy reports
from VS2005, but only when local to the report server. On my own
workstation, I get "cannot display the page" when I try to browse to Report
Manager , and "connection could not be made to the report server" when I try
to deploy reports. I checked local intranet sites in IE, and the whole
segment is allowed (set in GP) so that isn't th problem. Do you have any
ideas why I can't connect to RS from a workstation on my network? Thanks.Hi,
"cannot display the page" seems to be an IIS layer problem. To help
identifying your problem, can you
-verify url used to browse reports (http://<yourserver>/Reports)
-verify your web request reach IIS (chek logs at
c:\windows\system32\logfiles\)
-verify Http Status code send back by IIS
Jean-Pierre Riehl
http://blog.djeepy1.net
http://www.bewise.fr
"Coop" <Coop@.discussions.microsoft.com> wrote in message
news:48452325-3B31-4318-A3B5-B82F388A591A@.microsoft.com...
> Hi. Like some others here, I'm struggling to get a production install of
> RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
> database is on a separate SQL 2005 (SP2) server. With the help of some
> posts
> here I finally am able to browse to Report Manager and also deploy reports
> from VS2005, but only when local to the report server. On my own
> workstation, I get "cannot display the page" when I try to browse to
> Report
> Manager , and "connection could not be made to the report server" when I
> try
> to deploy reports. I checked local intranet sites in IE, and the whole
> segment is allowed (set in GP) so that isn't th problem. Do you have any
> ideas why I can't connect to RS from a workstation on my network? Thanks.|||If you can browse locally (when logged into the server) then everything is
setup correctly. I think the issue here is that you have not configured
roles properly. By default if you are a member of the local administrators
group then you are in the role that allows you to deploy. RS has its own
roles, totally separate from database security. Add your user for your
workstation to the local administrator group on the server. Then give it all
a try.
Also, try fully qualify your server (I assume when local you just used
localhost). For instance try
http://servername.whatever.com/reports
My guess is this is an issue with RS roles.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jean-Pierre Riehl" <jean-pierre.riehl@.b-e-w-i-s-e.fr> wrote in message
news:41E3F7CE-1559-41D5-B5BD-26129028BC7B@.microsoft.com...
> Hi,
> "cannot display the page" seems to be an IIS layer problem. To help
> identifying your problem, can you
> -verify url used to browse reports (http://<yourserver>/Reports)
> -verify your web request reach IIS (chek logs at
> c:\windows\system32\logfiles\)
> -verify Http Status code send back by IIS
>
> --
> Jean-Pierre Riehl
> http://blog.djeepy1.net
> http://www.bewise.fr
>
> "Coop" <Coop@.discussions.microsoft.com> wrote in message
> news:48452325-3B31-4318-A3B5-B82F388A591A@.microsoft.com...
>> Hi. Like some others here, I'm struggling to get a production install of
>> RS2005 (SP2). RS is installed on a dedicated W2K3 (SP2) server. The
>> database is on a separate SQL 2005 (SP2) server. With the help of some
>> posts
>> here I finally am able to browse to Report Manager and also deploy
>> reports
>> from VS2005, but only when local to the report server. On my own
>> workstation, I get "cannot display the page" when I try to browse to
>> Report
>> Manager , and "connection could not be made to the report server" when I
>> try
>> to deploy reports. I checked local intranet sites in IE, and the whole
>> segment is allowed (set in GP) so that isn't th problem. Do you have any
>> ideas why I can't connect to RS from a workstation on my network?
>> Thanks.
>

RS deactivated after upgrade from Win 2000 to W2k3

Hi,
After I have upgraded my server, RS stop working .
a.. The report server cannot decrypt the symmetric key used to access
sensitive or encrypted data in a report server database. You must either
restore a backup key or delete all encrypted content and then restart the
service. Check the documentation for more information.
(rsReportServerDisabled) Get Online Help
a.. Bad Data.
I have the Key (exported using the rskeymgmt utility)
But I can't reapply the key:
an "Unable to connect to the database" error appear when I try to reapply
the key.
I have lost a document on the Microsoft web site which explain the entire
process to reactivate RS.
Anyone has the link?
or can explain the procedure?
thanks
Jerome.You may need to use rsconfig to reset that database connection if it is
having issues:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_5f1e.asp
Here is an activation doc for the rsactivate utility:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_6yqq.asp
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>|||I think this is the key management article you are referring to...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/arp_dbadmin_v1_98xh.asp?frame=true
"Jéjé" wrote:
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>
>|||its ok
I'have found (or re-found ) the solution.
I have replaced the oledb32.dll file on the server by the 2.8 version
(instead-of the 2.7 version which is not upgraded during the Win2003
upgrade)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>