Partilhar via

Initializing a Report Server

  • Artigo

In Reporting Services, an initialized server is one that can encrypt and decrypt data in a report server database. Initialization is a requirement for report server operation. Initialization occurs when the Report Server Windows service is started for the first time. It also occurs when you join the report server to the existing deployment, or when you manually recreate the keys as part of the recovery process. For more information about how and why encryption keys are used, see Managing Encryption Keys and Storing Encrypted Report Server Data.

Encryption keys are based partly on the profile information of the Report Server Windows service. If you change the user identity used to run the Report Server Windows service, you must update the keys accordingly. If you are using the Reporting Services Configuration tool to change the identity, this step is handled for you automatically.

If initialization fails for some reason, the report server returns an RSReportServerNotActivated error in response to user and service requests. In this case, you may need to troubleshoot the system or server configuration. For more information, see Troubleshooting Initialization and Encryption Key Errors.

Overview of the Initialization Process

The initialization process creates and stores a symmetric key used for encryption. The symmetric key is created by the Microsoft Windows Cryptographic Services and subsequently used by the Report Server Windows service to encrypt and decrypt data. The symmetric key is itself encrypted with an asymmetric key.

In a Reporting Services installation, only the Report Server Windows service can perform encryption operations. When the Report Server Web service requires encryption or decryption, it calls the Report Server Windows service to perform the operation.

The following steps describe the initialization process:

  1. At initial start up, the Report Server Windows service reads the RSReportServer.config file to get the installation identifier and database connection information.
  2. The Report Server Windows service requests a public key from Cryptographic Services. Windows creates a private and public key and sends the public key to the Report Server Windows service.
  3. The Report Server Windows service connects to the report server database and stores the installation identifier and public key values.
  4. The Report Server Windows service calls into Cryptographic Services again, this time to request a symmetric key. Windows creates the symmetric key.
  5. The Report Server Windows service connects to the report server database again, and adds the symmetric key to the public key and installation identifier values that were stored in step 3. Before storing it, the Report Server Windows service uses its public key to encrypt the symmetric key. Once the symmetric key is stored, the report server is considered initialized and available to use.

Initializing a Report Server for Scale-out Deployment

Reporting Services supports a scale-out deployment model that shares a single report server database among multiple report server instances. To join a scale-out deployment, a report server must create and store its copy of the symmetric key in the shared database. Although a single symmetric key is used by servers that use the database, each report server has its copy of the key. Each copy varies in that it is uniquely encrypted using the public key its owner.

The first set of steps for initializing a report server for scale-out deployment are identical to the first three steps that describe initialization for a single server and database combination.

The initialization process for a scale out deployment differs in how the report server gets the symmetric key. When the first server is initialized, it gets the symmetric key from Windows. When the second server is initialized during configuration for scale-out deployment, it gets the symmetric key from the Report Server Windows service that is already initialized. The first report server instance uses the public key of the second instance to create an encrypted copy of the symmetric key for the second report server instance. The symmetric key is never exposed as plain text at any point in this process.

How to Initialize a Report Server

Note

RSKeymgmt is a console application that you run from a command line on a computer that hosts a report server instance that is already part of a scale-out deployment. When you run the utility, you specify arguments to select a remote report server instance that you want to initialize.

A report server will be initialized only if there is a match between the installation identifier and the public key. If the match succeeds, a symmetric key is created that permits reversible encryption. If the match fails, the report server is disabled, in which case you may be required to apply a backup key or delete the encrypted data if a backup key is unavailable or not valid. For more information about encryption keys used by a report server, see Managing Encryption Keys.

Note

You can also use the Reporting Services Windows Management Instrumentation (WMI) provider to initialize a report server programmatically. For more information, see Reporting Services WMI Provider.

How to Confirm a Report Server Initialization

To confirm report server initialization, ping the Report Server Web service by typing http://<servername>/reportserver in the command window. If the RSReportServerNotActivated error occurs, the initialization failed.

See Also

Tasks

Troubleshooting Initialization and Encryption Key Errors

Concepts

Backup and Restore Operations for a Reporting Services Installation
Administering Reporting Services
Storing Encrypted Report Server Data

Other Resources

Deploying Reporting Services

Help and Information

Getting SQL Server 2005 Assistance