If SQL Server Reporting Services (SSRS) is setup in Native mode along with SQL Server database engine, the configuration is automatically done and SSRS is ready for use. SSRS Setup options can be reviewed at
In scenarios where SSRS is installed separately from SQL Server database engine, or the option to setup but not configure is selected, SSRS needs to be configured before first use. After configuration, SSRS can be verified using the steps mentioned in Verify a Reporting Services Installation at http://msdn.microsoft.com/en-US/library/ms143773.aspx
In this article we will review the steps that have to be completed for a Native mode SSRS installation.
1. Verify setup folders - SSRS is usually installed to the location <DesiredPath>\Microsoft SQL Server\MSRS11.<instancename >\Reporting Services\. File Locations for Default and Named Instances of SQL Server at http://msdn.microsoft.com/en-us/library/ms143547.aspx shares this info -
The registry hive is created under HKLM\Software\Microsoft\Microsoft SQL Server\<Instance_ID> for instance-aware components. For example,
•
HKLM\Software\Microsoft\Microsoft SQL Server\MSRS11.MyInstance
The registry also maintains a mapping of instance ID to instance name. Instance ID to instance name mapping is maintained as follows:
•
[HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names\RS] "InstanceName"="MSRS11"
In HKLM\Software\Microsoft\Microsoft SQL Server\MSRS11.MyInstance\Setup we can find SQLPath which will show the location of the installed components.
http://support.microsoft.com/kb/938245 has this tip regarding 32 bit installations - If you are running a 32-bit version of SQL Server 2005 Reporting Services on a 64-bit Windows operating system, locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server\MSSQL.X\Setup
2. Check whether the instance is shown when Reporting Services Configuration manager is opened. The contents of the registry in Instance Names\RS mentioned above will be shown. How to: Start Reporting Services Configuration Manager at http://msdn.microsoft.com/en-us/library/ms159644.aspx shows how to invoke it.
3. Use the Reporting Services Configuration manager to ensure valid values are present in each of the tabs on the left side. Reporting Services Configuration Manager (Native Mode) at http://msdn.microsoft.com/en-us/library/bb934490.aspx covers the common tasks. The essential ones are "Service Account", "Web Service URL", "Report Manager URL", and "Database".
Service Account -
Local Service is the least privileged, Local System is highly privileged. For that reason, we can avoid both. When deciding between NetworkService and domain accounts, check whether Kerberos delegation is going to be needed and what are the SPNs present
for that. Refer
http://social.technet.microsoft.com/wiki/contents/articles/1406.kerberos-for-microsoft-bi-en-us.aspx for Kerberos setup.
Web Service URL, Report Manager URL -
Pick a site/name that does not conflict with existing ones. If the server has multiple NIC cards, use Advanced option to bind with specific IP addresses rather than All Assigned, if it did not work at first. Before implementing certificates, ensure
it works without SSL.
When implementing certificates, Configure SSL Connections on a Native Mode Report Server at http://msdn.microsoft.com/en-us/library/ms345223(v=sql.110).aspx and http://support.microsoft.com/kb/2418246 could be used.
Once these have been set, use this from the command prompt to verify that SSRS is listening on the correct server name and port - netsh http show urlacl
Database -
While creating a SSRS catalog database. ensure existing database is not selected, unless sure of the operation being performed. Change Database is used to provide server name, create or select existing database and provide the credentials to be used
for the connection.
Encryption Keys - When all the buttons are enabled, the SSRS instance is connected to its database and is usually working fine. When only Restore and Delete options are enabled, it indicates either a database connectivity issue or an issue with the encryption
key. In case of new databases, if the database connectivity seems alright, Delete option can be taken from the Encryption Key tab. Deleting encrypted content would not be advisable on anything but new installs of Reporting Services –
Delete and Re-create Encryption Keys at
http://msdn2.microsoft.com/en-us/library/ms156010.aspx indicates this -
Deleting the encryption keys removes all symmetric key information from the report server database and deletes any encrypted content. All unencrypted data is left intact; only encrypted content is removed. When you delete the encryption keys, the report
server re-initializes itself automatically by adding a new symmetric key. The followinare enabled, the SSRS instance is connected to its database and is usually working fine. Wg occurs when you delete encrypted content:
•
Connection strings in shared data sources are deleted. Users who run reports get the error "The ConnectionString property has not been initialized."
•
Stored credentials are deleted. Reports and shared data sources are reconfigured to use prompted credentials.
•
Reports that are based on models (and require shared data sources configured with stored or no credentials) will not run.
•
Subscriptions are deactivated.
Once you delete encrypted content, you cannot recover it. You must re-specify connection strings and stored credentials, and you must activate subscriptions.
Scale-out Deployment:
Lists all the SSRS servers that are connected to the same catalog database. It also includes key information from a Encryption Key restore operation. Multiple keys are only okay when scale-out architecture is in use.
Issues?
Troubleshooting Configuration Problems at
http://msdn.microsoft.com/en-us/library/ms159704.aspx helps solve some known issues. Report Server Service Trace Log and Report Server HTTP Log can provide clues, if still stuck.
Thanks
Hope this helps configure SSRS in Native mode. Do share your questions or if there's any area needing more attention or references, please add those topics to the comments below. Thanks for choosing Microsoft.
