Freigeben über

TIP: Moving Reporting Servers between domains

  • Artikel

 

I recently had to move some development SRS machines from one domain to another at work. This consisted of two cluster web boxes, and one SQL Server, using SQL auth.

 

After doing so, I received the following error:

 

Reporting Services Error

  • The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help
    • Login failed for user '<domainname>\<servername>$'.

 

The fix for this (thanks to the SRS team!) is as follows:

 

  • Create a new SQL login for the new machine account.
  • Add the new SQL account to the RSExec role in the following DBs:
    • ReportServer
    • ReportServerTempDB
    • msdb
    • master

Of course, if you set up your SQL box to use non-standard DB names, replace ReportServer and ReportServerTempDB with the names you have used.

 

I hope that someone out there finds this useful.

 

cheers,

~stuart

Comments

  • Anonymous
    November 17, 2004
    Similar scenerio, but getting a slightly different error. When my server was moved to another domain, the name of the server was changed as well. This is what I suspect is the reason.. I saw some DB settings in REReportServer.config, but all of them are encrpted. Any clues??

    The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help
    SQL Server does not exist or access denied.

    Thanks
    Advait

  • Anonymous
    November 18, 2004

    You should be able to use the rsconfig utility to reset the connection information.

    Hopefully this documentation will prove useful:

    Configuring a Report Server Connection
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/arp_configserver_v1_0yci.asp

  • Anonymous
    November 22, 2004
    Thanks for the tip. I'm not sure why we started getting that error (our SQL Server might be having some issues), but I just Googled rsReportServerDatabaseUnavailable and your tip came up. After rebooting and running the rsConfig we stopped getting the error.

  • Anonymous
    November 25, 2007
    PingBack from http://feeds.maxblog.eu/item_254835.html

  • Anonymous
    January 21, 2009
    PingBack from http://www.keyongtech.com/2187065-installation-on-2003-login-failed

  • Anonymous
    June 13, 2009
    PingBack from http://thestoragebench.info/story.php?id=6114