Showing posts with label appreciated. Show all posts
Showing posts with label appreciated. Show all posts

Friday, March 9, 2012

Report Server Windows Service cannot connect to the report server

We are experiencing the error below on our SQL Server 2005 server. Any help
would be appreciated. Thank you.
Report Server Windows Service (MSSQLSERVER) cannot connect to the report
server database.
--
MikeMike,
Try using the Reporting Services Configuration tool to help troubleshoot.
Steve MunLeeuw
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:D25C9CD8-7279-428C-AEE6-C535157ED8D6@.microsoft.com...
> We are experiencing the error below on our SQL Server 2005 server. Any
> help
> would be appreciated. Thank you.
> Report Server Windows Service (MSSQLSERVER) cannot connect to the report
> server database.
> --
> Mike|||I assume this is your Report Server database you are referring to?
Does this correct itself or do you have to restart the sql server or
service?
I'm getting these errors a lot in our production environment. They seem
to occur when there are large, poorly performing reports running. Check
to see what's running at the time of the error to see if you have long
running queries running.
I also get this one a lot too--> Scheduled operations cannot be
created. SQL Server Agent is not running.
Reporting Services does not seem to be able to handle much of a
workload.
Mike wrote:
> We are experiencing the error below on our SQL Server 2005 server. Any help
> would be appreciated. Thank you.
> Report Server Windows Service (MSSQLSERVER) cannot connect to the report
> server database.
> --
> Mike

Saturday, February 25, 2012

Report Server - Access Error

Any help appreciated...
Installed Reporting Services on Win2003 machine with a SQL2000 db.
Reporting Services was installed with an IIS without default website, running
IIS5.0 Isolation mode.
When navigating to http://<hostheader>/reports I get the folllowing error...
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
When navigating to http://<hostheader>/ReportServer, the following error
occurs...
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
I have ensure the account running reports is included in the group running
the webservices. Also made the change to utilise <ReportServerURL> to the
http://<hostheader>/ReportServer.
Any assistance appreciated...
JamesHi, James
You either need to have the default website in IIS in order to use
Reporting Services, or you must specify a different website in which
the Reports and ReportService virtual directories will be created.
To use a different website than the Default IIS site, you will need to
change the configuration files for the report server app, service, and
report manager app. Please see the following article for more
information on how to setup RS for a non-Default website:
RS 2005 BOL => http://msdn2.microsoft.com/en-us/library/ms155921.aspx
couldn't find the equivalent BOL article for RS2000 in the MSDN, so
here is a link to an article on the web that will suffice:
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=3&rl=1
Have fun!
Regards,
Thiago Silva
JamesC wrote:
> Any help appreciated...
> Installed Reporting Services on Win2003 machine with a SQL2000 db.
> Reporting Services was installed with an IIS without default website, running
> IIS5.0 Isolation mode.
> When navigating to http://<hostheader>/reports I get the folllowing error...
> The report server is not responding. Verify that the report server is
> running and can be accessed from this computer.
>
> When navigating to http://<hostheader>/ReportServer, the following error
> occurs...
>
> The report server is not responding. Verify that the report server is
> running and can be accessed from this computer.
>
> I have ensure the account running reports is included in the group running
> the webservices. Also made the change to utilise <ReportServerURL> to the
> http://<hostheader>/ReportServer.
> Any assistance appreciated...
> James|||All resolved, needed to ensure that the web server was not running in IIS5.0
isolation mode.
Thanks.
"tafs7" wrote:
> Hi, James
> You either need to have the default website in IIS in order to use
> Reporting Services, or you must specify a different website in which
> the Reports and ReportService virtual directories will be created.
> To use a different website than the Default IIS site, you will need to
> change the configuration files for the report server app, service, and
> report manager app. Please see the following article for more
> information on how to setup RS for a non-Default website:
> RS 2005 BOL => http://msdn2.microsoft.com/en-us/library/ms155921.aspx
> couldn't find the equivalent BOL article for RS2000 in the MSDN, so
> here is a link to an article on the web that will suffice:
> http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=3&rl=1
> Have fun!
> Regards,
> Thiago Silva
> JamesC wrote:
> > Any help appreciated...
> >
> > Installed Reporting Services on Win2003 machine with a SQL2000 db.
> > Reporting Services was installed with an IIS without default website, running
> > IIS5.0 Isolation mode.
> >
> > When navigating to http://<hostheader>/reports I get the folllowing error...
> >
> > The report server is not responding. Verify that the report server is
> > running and can be accessed from this computer.
> >
> >
> > When navigating to http://<hostheader>/ReportServer, the following error
> > occurs...
> >
> >
> > The report server is not responding. Verify that the report server is
> > running and can be accessed from this computer.
> >
> >
> > I have ensure the account running reports is included in the group running
> > the webservices. Also made the change to utilise <ReportServerURL> to the
> > http://<hostheader>/ReportServer.
> >
> > Any assistance appreciated...
> >
> > James
>