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.

Comments

Post a Comment

Popular posts from this blog

IFD Implementation for custom web pages and Anonymous Access

-
When deploying my custom web pages for an IFD deployment, I got a FileLoadException (Exception from HRESULT: 0x80131401) on accessing the page in the browser. Basically, this issue arose since anonymous access was somehow disabled for the “ISV/CustomPages” application in IIS while by default it is enabled for the Microsoft Dynamics CRM website. This implied that my custom web site was using Windows NT Authentication, while the Microsoft Dynamics CRM Website was enabled for anonymous access. Hence, I got “Loading this assembly would produce a different grant set from other instances” on accessing any of my web pages from within MS CRM. Simply turning on anonymous access for my custom website did the trick and rendered all my custom web pages correctly :)
Read more

Using CRM Services to create or update records in large numbers

-
Recently, I implemented a plug in code which invoked auto creation of records from a contacts list (rather marketing lists based on MS CRM contacts) for my custom entity. The code worked well but it hanged whenever I considered a marketing list of more than 3000 contacts. The error logged read: Only one usage of each socket address (protocol/network address/port) is normally permitted. Basically, the error was thrown when the creation process exhausted the limit of socket connections allowed by the IIS and the SDK still polled for another connection and consequentially timed out after a certain number of records were created. A quick workaround for this is to change the following entries in the registry: HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort to 65534AndHKLM\System\CurrentControlSet\Services\Tcpip\Parameters\TCPTimedWaitDelay to be 30 The link : http://dmcrm.blogspot.com/2008/07/updating-records-in-mass-via-sdk.html also mentions a resolution of this by us...
Read more

Issues after Re-Naming MS CRM Servers computer/machine name

-
Currently I faced a scenario where the machine on which MS CRM 4.0 was installed was required to be renamed on LAN. My deployment had the SQL Server installed on another machine on LAN. After changing the MSCRM Server machine name, MS CRM browser stopped working and started showing error “SqlException: Login failed for user [Domain Name]\[New Machine Name] .” This error comes when the MS CRM server related entries in registry and database (that refer to the server name) have not yet been changed to the new server name This problem could be solved by 'Repairing’ the MS CRM 4.0 installation on the machine after renaming it. Go to the Control Panel -> Add or Remove programs-> Microsoft Dynamics CRM Server. Repair the installation. Repair installation internally performs the following actions: a. In the registry, ServerURL key value at HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MSCRM is updated with the new machine name (example: the value would be like “http:// :5555/MSCRMServices”...
Read more