case where the database server was renamed resulting in reporting service unavailability

Case Environment:

Operating system version: Windows Server R2 Standard

Database version: SQL Server Edition SP2

Case Description:

In fact, it is the second time that this situation has been encountered, or decided to record this case. The first time is to do database migration encountered, there is no time to collate records, the second preparation of a test environment, from the virtual machine a server cloned a test server GETESTNT30, the server name has changed, but SQL Server inside @ @SERVERNAME and SERVERPROPERTY (' servername ') is inconsistent.

The phenomenon is as follows:

The report server cannot open a connection to the report server database. A connection to the database are required for all requests and processing. (rsreportserverdatabaseunavailable) Get Online Help
Login failed for user ' xxxx\gettestnt30$ '.

The report server cannot open a connection to the report server database. A connection to the database are required for all requests and processing. (rsreportserverdatabaseunavailable)

If you want to see more detailed error messages, you can go to the installation directory of SQL Server, such as this test server C:\Program Files\Microsoft SQL Server\msrs11. View verbose logging under Mssqlserver\reporting services\logfiles.

As shown below, in reporting Services Configuration Manager, the SQL Server name shown in the database option is the original server GETNT59, and the report Manager The URL is GETTESTNT30

Workaround:

Open the Configuration Manager for the reporting service to rename the database server.

After completion, you must also delete the encrypted contents (delete enrypted content) for proper access to the URL address of the reporting service.

case where the database server was renamed resulting in reporting service unavailability