How to switch your Reporting Services server
Published: October 6, 2006
You might want to move a Microsoft SQL Server Reporting Services database that Microsoft Dynamics CRM 3.0 uses from one computer to another computer for several reasons. For example, you use Reporting Services to create and run Microsoft CRM reports on a computer that is used in a development environment, and you want to move these reports to a computer that is used in the production environment.
On This Page
To change the Reporting Services server, you must first copy the Microsoft CRM reports to the new Reporting Services server, update the server information in Microsoft CRM, and then republish the reports. The following sections describe each step.
You should already have Reporting Services installed and running on the computer where you want to move the Microsoft CRM reports. For information about how to install and configure SQL Server Reporting Services, see the Related Links section.
Step 1: Copy the reports to the new Reporting Services server
At a command prompt on the Microsoft Dynamics CRM 3.0 Server computer, run the DownloadReports.exe command. When you run this command, a file will be created for each report (ReportName.rdl), together with a configuration file that is named publish.config. This configuration file includes the metadata for the report, such as the report description, the categories the report belongs to, and where the report will appear in Microsoft CRM. When you run DownloadReports.exe, specify a folder to store the report files. Note that if there are already report files or a publish.config file in the folder, these files will be overwritten.
The DownloadReports.exe file must be run from the Microsoft Dynamics CRM 3.0 Server computer in the c:\Program Files\Microsoft CRM\Reports folder, where CRM_Organization_Name is the Microsoft CRM organization name and FolderName is the name of the folder where the reports will be copied. For example:
c:\Program Files\Microsoft CRM\Reports>downloadreports.exe “CRM_Organization_Name” c:\FolderName
You can find the organization name in SQL Server Enterprise Manager. To do this, click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager. Expand Microsoft SQL Servers, expand SQL Server Group, expand local, expand Databases, and then locate the OrgName_MSCRM database. OrgName is the Microsoft CRM organization name.
Step 2: Update Microsoft CRM to point to the new Reporting Services server
Start Microsoft CRM Deployment Manager. To do this, follow these steps:
1. | On the computer where Microsoft Dynamics CRM 3.0 Server is installed, click Start, point to Programs, point to Microsoft CRM, and then click Deployment Manager. |
2. | Click Server Manager, and in the right pane, right-click the Microsoft CRM server name, and then click Specify Reporting Server URL. |
3. | In the Reporting Server URL box, type the new address, for example, https://NewReportServerName/ReportServer. |
Step 3: Republish the reports
At a command prompt on the new Reporting Services server where you want to run Microsoft CRM reports, run the PublishReports.exe command. To run this command, you must have the System Administrator security role in Microsoft CRM and the Content Manager role on the root folder of Report Manager. By default, members of the local Administrators group on the Reporting Services server have the System Administrator role.
The PublishReports.exe file is located in the c:\Program Files\Microsoft CRM\Reports folder on the Microsoft Dynamics CRM 3.0 Server computer.
For example, from the C:\Program Files\Microsoft CRM\Reports folder on the Microsoft CRM Server computer, run the following PublishReports.exe command where Domain is the Active Directory directory service domain name and (GUID} is the identifier for the ReportingGroup group in Active Directory:
c:\Program Files\Microsoft CRM\Reports>publishreports.exe “CRM_Organization_Name” “Domain\ReportingGroup {GUID}”
To find the GUID for the ReportingGroup group, start Active Directory Users and Computers and view the GUID that is appended to the ReportingGroup group name.
Depending on the Internet Information Services (IIS) CRMAppPool application pool identity configuration, the account name may be required by the PublishReports.exe command. For example, if Microsoft CRM Server and SQL Server Reporting Services are running on the same computer and the NT Authority Network Service is used as the CRMAppPool application pool identity, you must run the following command:
c:\Program Files\Microsoft CRM\Reports>publishreports.exe “CRM_Organization_Name” “Domain\ReportingGroup {GUID}” “NT AUTHORITY\NETWORK SERVICE”
Alternatively, if Microsoft CRM Server and SQL Server Reporting Services are running on different computers and the Network Service is used as the CRMAppPool application pool identity, you must run the following command where CRMComputerAccount$ is the name of the computer appended with “$” where Microsoft CRM Server is installed:
c:\Program Files\Microsoft CRM\Reports>publishreports.exe “CRM_Organization_Name” “Domain\ReportingGroup {GUID}” “DomainName\CRMComputerAccount$”
Or, if the CRMAppPool application pool identity is running under a user account, you must run the following command, where UserAccountName is the name of the user account configured as the identity for the CRMAppPool application pool:
c:\Program Files\Microsoft CRM\Reports>publishreports.exe “CRM_Organization_Name” “Domain\ReportingGroup {GUID}” “DomainName\UserAccountName”
To find the CRMAppPool application pool identity, start Internet Information Services (IIS) Manager, expand the computer where Microsoft CRM Server is installed, expand Application Pools, right-click CRMAppPool, click Properties, and then click the Identity tab.
