Initialization (Reporting Services Configuration)

An initialized report server describes a server that can encrypt and decrypt sensitive data that is stored in a report server database (for example, stored credentials and connection strings). Report server initialization is a requirement for report server operations.

Use this page to view the initialization status for a scale-out deployment or to join a report server to a scale-out deployment. This page does not show initialization status for a single server installation. A single server installation is initialized automatically when you set the database connection.

For a report server that is currently part of a scale-out deployment, this page shows initialization status for all of the report server instances that share the same report server database. When viewing status for a scale-out deployment, it does not matter which server you are connected to. The status information for each node will be available on this page regardless of the instance you connect to.

There are three possible initialization states for a scale-out deployment. Each state is indicated by a color-coded icon next to Initialization on the page selection pane in the Reporting Services Configuration tool:

• A grayed-out status icon appears if the database connection is not set or if you are using an edition that does not support scale-out deployment.

  Note

  Scale-out deployment is not supported by SQL Server 2005 Express Edition with Advanced Services, SQL Server 2005 Workgroup Edition, or SQL Server Standard Edition. For more information about feature availability in the Express edition, see Reporting Services in SQL Server 2005 Express Edition with Advanced Services in SQL Server Books Online.

• A green check indicates that the current report server instance is initialized. The green check appears when you configure the report server database connection and the report server instance has a copy of the symmetric key in the database.

• A red X indicates that a server is not initialized. A red X will always appear for a report server that has been removed from a scale-out deployment and does not yet have a report server database dedicated for its exclusive use. This condition will resolve itself when you create a new report server database for the report server.
  A red X will also appear if the report server database is offline or unavailable. To verify whether this is the case, use SQL Server Management Studio to connect the Database Engine instance that hosts the report server database.
  In all other cases, a red X indicates that the server cannot encrypt or decrypt data in the report server database. You should restore a backup copy of the symmetric key to resolve this issue. If a red X appeared after you changed a service account (and you did not use the Reporting Services Configuration tool to change the account), and you do not have a backup of the key, you should temporarily change the server to run under the old account so that you can obtain a backup of the key. For more information, see Managing Encryption Keys and Configuring Service Accounts and Passwords in Reporting Services.

Options

• Machine
  Shows the name of the computer that hosts the report server instance. If you upgraded a report server, and this entry is missing, you can add the computer name to the Keys table in the report server database.

• Instance
  Shows the report server instance name. Report server instances are based on SQL Server instances.

• ID
  Shows a GUID created during report server setup. You can use this value with the rskeymgmt -n argument to initialize a remote report server instance that is in a state where it cannot encrypt or decrypt data in the report server database.

• Initialized
  Indicates whether the report server is initialized.

• Initialize
  Click Initialize to configure a report server to use a symmetric key in a shared report server database. You can use Initialize to add a report server instance to a scale-out deployment or to troubleshoot a migration or installation problem.

  To configure a scale-out deployment, select the report server instance you want to add, and then click Initialize. A report server instance is only available if you have previously configured a connection to the shared report server database. In addition, you must perform the initialization from a report server that is already initialized to use the report server database.

• Remove
  Click Remove to remove the encryption keys of the selected report server instance from the report server database. You can remove keys to remove a report server from a scale-out deployment or to troubleshoot a migration or installation problem. With this option, only the encryption keys for the specified report server instance are removed. Encrypted data in the report server database is not affected.

  As a precaution, be sure to create a backup copy of the symmetric key before you remove it. Once you remove the encryption keys of the last report server in the list, you introduce new requirements for any subsequent report server initialization for that database. The new requirement is that after you initialize a report server you must restore a backup copy of the symmetric key. Restoring the symmetric key is necessary if you want to access the encrypted data that is currently in the report server database.

  If you no longer need the encrypted data or if you do not have a backup copy of the key, you must delete the encrypted data. For more information, see Encryption Keys (Reporting Services Configuration).

Change History

See Also

Other Resources

Configuring a Report Server Scale-Out Deployment
Upgrading a Report Server Web Farm
rskeymgmt Utility
Initializing a Report Server
Managing Encryption Keys
How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration)

Help and Information

Getting SQL Server 2005 Assistance