Monday, January 11, 2010

Error message in the Environmental Diagnostic wizard when you try to install the Microsoft Dynamics CRM Connector for SQL Server Reporting Services

When MS CRM and SQL Server are installed on separate server machines, we need to install MS CRM Connector on the server running SQL reporting services. While installing this, I faced an error saying “Unable to validate SQL Server Reporting Services Report Server installation” in the Environmental diagnostic wizard.

As stated by Microsoft support, this issue comes in the following scenarios:
1. You try to install the Microsoft Dynamics CRM Connector for SQL Server Reporting Services on a server that is not running Microsoft SQL Server 2005 Reporting Services (SSRS).
2. You try to install the Microsoft Dynamics CRM Connector for SQL Server Reporting Services on a named instance of SQL Server 2005 Reporting Services.
3. You try to install the Microsoft Dynamics CRM Connector for SQL Server Reporting Services on a SQL Server 2005 Reporting Services installation that uses a nondefault Web site.

In my case, the issue was due to named instance of SQL server 2005.
To resolve this issue:-

For the first scenario above, install the Microsoft Dynamics CRM Connector for SQL Server Reporting Services on a server that is running SQL Server 2005 Reporting Services.

For the second and third scenarios, follow these steps:

1. Copy all the files in the SrsDataConnector folder on the installation CD to a folder on drive C. For example, copy the files to the following folder:
C:\SrsDataConnector
Note The SrsDataConnector folder is located in the following folder on the installation CD:
drive:\Server\i386

2. Locate the folder in which you copied the installation files. Right-click the Install-config.xml file, and then open the file in Notepad.
3. Add the following information to the Install-config.xml file:

• The reportserverurl tags
• The URL for the server that is running SQL Server 2005 Reporting Services

For example, if the server that is running Reporting Services has a named instance of Titan, the reportserverurl tags resemble the following example.
http://servername/Reportserver$Titan
4. If the server that is running SQL Server 2005 Reporting Services has a named instance, modify the instancename tags.

For example, if the server that is running Reporting Services has a named instance of Titan, the instancename tags resemble the following example.
Titan
5. After you complete steps 3 and 4, click Save on the File menu, and then close the Install-config.xml file. The Install-config.xml file should resemble the following example.
<crmsetup>
<srsdataconnector>
<configdbserver></configdbserver>
<autoupdateconfigdb>1</autoupdateconfigdb>
<reportserverurl>http://servername/Reportserver$Titan</reportserverurl>
<autogroupmanagementoff>0</autogroupmanagementoff>
<instancename>Titan</instancename>
<configsku>OnPremise</configsku>
<!-- Set enabled = true for DB webstore integration. Set configdb="true" for config db webstore integration-->
<webstore enabled="false" configdb="false" />
<monitoring>
<!-- Monitoring service account name and password. It can not be local system or network service account -->
<serviceaccountname></serviceaccountname>
<serviceaccountpassword></serviceaccountpassword>
</monitoring>
</srsdataconnector>
</crmsetup>

6. Open a Command Prompt window, and then locate the folder in which you copied the installation files in step 1.
7. At the command prompt, type the following command, and then press ENTER:
C:\SrsDataConnector> SetupSrsDataConnector /CONFIG path of the folder that contains the Install-config.xml file\install-config.xml

That’s it! I hope it helps.

1 comment:

  1. Thanks for the sharing of such information.This is a great stuff of reading. I will pass it on to our audience. Thanking you,CRM Services

    ReplyDelete