December 7, 2007 at 12:19 pm
[font="Arial"]I recently installed SQL Server Reporting Services 2005 along with SQL Server 2005 on a new server that is being dedicated to SSRS support for our enterprise. This is the replacement server for a similar instance we're retiring due to hardware obsolecence.
I performed my standard installation I've done countless times. All aspects of SQL were behaving properly and I just finished deploying a report from my previous SSRS server to the new SSRS server after making minor changes in BIDS. When I progressed with setting up my first subscription on the new SSRS instance I noticed that I had not yet launched the Reporting Services Configuration tool because I did not have the option of delivering the report via email.
I launched the SSRS Config tool and made only 2 changes:
I configured the Email Settings with the Sender Address, Current Delivery Method, and SMTP Server settings that matched my existing instance of SSRS. I also configured the Execution Account to match my existing instance of SSRS.
That was it.
I navigated back to the Report Manager URL and received the following message:[/font]
[font="Courier New"]The report server is not responding. Verify that the report server is running and can be accessed from this computer[/font]
[font="Arial"]I cleared my temporary internet files in IE, I've restarted all SQL Services followed by the IIS service and I've even rebooted the server. Nothing has cleared up the error. I've gone so far as to back out the changes and then restarted all SQL and IIS services and still get the error.
Any help is appreciated?[/font]
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
December 9, 2007 at 6:54 pm
You mentioned you changed an account. At the very least, make sure the account has an SQL login & necessary rights to the database in question (it needs to be in the RSExecRole in master, msdb, ReportServer & ReportServerTempDB databases), and that it has any NTFS permissions required to read/write to folders/files.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
December 9, 2007 at 8:28 pm
It is not only a member of the SysAdmin server role in the SQL instance, but is also assigned to the AD group that has local administrator rights on the server. The account setting was for the unattended user in SSRS.
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
December 10, 2007 at 3:31 pm
Moving Reporting Services is not a simple task because the Master of the new Server is not aware of your old ReportServerDB and ReportServerTempDB. So I don't think your minor changes are relevant to your problem but here is a detailed guide for migration from Microsoft Support.
http://support.microsoft.com/kb/842425/en-us"> http://support.microsoft.com/kb/842425/en-us
Kind regards,
Gift Peddie
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply