Report Server Windows Service Problem

Hello,

I am my department's Sys Admin and a relativelty Noobie when it comes to SQL server. So I recently Installed SQL Server 2005 on a Win2003 Server. During install I set my domain account as the service account login. After the DB and Web Application were setup and running good I realized that the SQL service accounts were logging in as my domain account. Not a good thing right? So in SQL Server Configuration Manager I changed the services from logging on as my domain account to the local system account instead.

Enter the problem: now I notice in application event viewer the Report Server Windows Service is erroring every minute. The error reads "Report server windows service cannot connect to the report server database." Im sure this was caused by me changing what account the report server service logs in as and local system account not having appropriate permissions. So what account should the report server windows service log in as? I see where to change the windows report service identity in Configure Report Server but I am not able to backup an encryption key? Thanks in advance!

If everything is installed locally I'd suggest you use LocalSystem although the setup suggests you use a domain account. Use the Reporting Services Configuration Manager (found under the Configuration Tools program group in the Microsoft SQL Server 2005 program group) to reset the Windows Service account. Since you don't have a backup of the encryption key, you may need to delete the encrypted content (Encryption Keys section) before you can reset the account. The following info may help. The moral of this story is that you should always back up the encryption key (you can use the config utility) as a last step after RS is set up.

Report server times out with error "report server is not responding"

Hi. We have RS2005/SP1 installed on Win2003/SP1. When we first installed it and it was running under Windows Authentication, we did not notice any slowness or timeouts while working with Report Manager or Management Studio. However, after we switched to Forms Authentication and set up the security extension sample provided, both the Report Manager and Management Studio (connected to Reporting Services) started to time out very often (even when simply browsing through the folders). It seems that Report Manager is timing out more often than Management Studio, however. After Report Manager times out, if I click the "Home" link or hit the "Back" button and try the same operation again, it usually works. The next few clicks work fine and I get a quick response, then it times out again.

Any help would be appreciated. Thanks

- Mark

Hi Mark,

We have not seen this problem reported before. I will take a look and if there is anything we can do about it, I will let you know.

|||

Hi Brad.

Have you been able to gather any information on this? Any suggestions as far as things to try to troubleshoot the issue?

Thanks

- Mark

|||

Hi Mark,

I did not get very far with this one. One person I talked to said to make the timeout in the Web.config file longer for SessionState. I looked and found the following in my web.config

<sessionState mode="InProc" cookieless="false" timeout="20" />

You could try changing this value to 100 or changing cookieless to true.

Otherwise I have not heard of anything to help on this one.

One other item to look at is the Web.Config settings in the following link.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp

Report server spawning multiple w3wp.exe threads

We have Win2003 SP1, SQL 2000 SP4, RS 2000 SP2 installed on our dev
machine and it works ok - having problems using anonamous access under
IIS but that is another issue.....
On our production server ( win2003 SP1, SQL 2000 SP4 ) we installed RS
2000 and SP2, accepting all the default installation options accept
SSL, and we have the following problems....
When we try to access http:\\servername\reports it takes a good few
minutes to load the web page, after asking for a domain user account,
and then the whole server runs like a dog.
Just getting to the first web page creates 12-15 copies of w3wp.exe,
each of which swallow between 20 and 130 MB of memory, and ramps up the
CPU usage.
I you try to upload a report, or access an existing report it spawns
off another 8-10 copies of w3wp.exe and eats more memory, and seriously
slows the server down.
The only way to release the resources it has useems to be to restart
IIS.
I "think" that this may be due to some hardening or lock down of
production server, but I am struggling on what to do next.
The RS logs do not seem to show any problems, but the Win App log shows
"ID 124 ReportServer Service has been activated" 5-6 times for every
action you take against reporting services.
I have been through the "checking reporting services is installed"
guides and it all seems ok, so there is something key I am missing here
!!!
Anyone else had similar problems and found the solution, or could at
least point me in the right direction to progress this issue !An update...
Thanks our freinds at the hosting company, it turns out this was all
due to .Net framework and IIS
We have apps running under 1.1 and 2.0 frameworks, and RS was set to
use default app pool on the IIS config.
Created a new app pool, and let both RS directories use that instead -
bingo !
Lots of w3wp.exe still created, but not hosing the box, and the number
goes up and down as usage changes.
Advice has been to create a new app pool just for reporting services,
as it is a hungry beast !

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
>