locked
Cannot install CRM 4.0 Connector for SSRS RRS feed

  • Question

  • Server A is 2008 R2 and has CRM 4.0 installed.

    Server B is 2008 R2 with SQL Server 2008 and SQL Reporting Services installed.

    SRS is working.  From a client PC, Server A or Server B I can open a browser and run reports by typing in the URL.

    If I try to install the SSRS Connector on Server B, It fails validation with the following error:

    Unable to validate SQL Server Reporting Services Report Server installation. Please check that it is correctly installed on the local machine.

    The full error from the log is:

    16:39:00|   Info| === Setup bootstrap logging started 20/10/2011 16:39:00 ===
    16:39:00|   Info| Bootstrap version: 4.0.7333.3.
    16:39:00|   Info| User: administrator.
    16:39:01|   Info| .NET version found is 3.0.30729.4926
    16:39:01|   Info| IsDotNetInstalled=1
    16:39:01|   Info| IsDrWatsonInstalled=0
    16:39:01|   Info| Installer path for Microsoft Application Error Reporting set to F:\Server\amd64\SrsDataConnector\DW\watson.msi
    16:39:01|   Info| Installer path for Microsoft Visual C++ Runtime set to F:\Redist\amd64\VcRedist\vcredist_x64.exe
    16:39:03|   Info| .NET version found is 3.0.30729.4926
    16:39:03|   Info| IsDotNetInstalled=1
    16:39:03|   Info| IsDrWatsonInstalled=0
    16:39:03|   Info| Installer path for Microsoft Application Error Reporting set to F:\Server\amd64\SrsDataConnector\DW\watson.msi
    16:39:03|   Info| Installer path for Microsoft Visual C++ Runtime set to F:\Redist\amd64\VcRedist\vcredist_x64.exe
    16:39:05|   Info| Installing Microsoft Application Error Reporting
    16:39:05|   Info| Log file: C:\Users\administrator.SARNT\AppData\Roaming\Microsoft\MSCRM\Logs\watson.log
    16:39:06|   Info| Installation of Microsoft Application Error Reporting has completed. Exit code: 0. Result: Version installed: 11.0.5510
    16:39:06|   Info| Installing Microsoft Visual C++ Runtime
    16:39:07|   Info| Installation of Microsoft Visual C++ Runtime has completed. Exit code: 0. Result: Version installed: 8.0
    16:39:09|   Info| === Setup bootstrap logging ended 20/10/2011 16:39:09 ===
    16:39:11|   Info| === Managed setup logging started: 20/10/2011 16:39:11 ===
    16:39:11|Verbose| Method entry: Microsoft.Crm.Setup.SrsDataConnector.SrsDataConnectorSetup.Initialize
    16:39:11|Verbose| Method entry: Microsoft.Crm.Setup.Common.SetupBase.Initialize
    16:39:11|Verbose| Method exit: Microsoft.Crm.Setup.Common.SetupBase.Initialize
    16:39:11|Verbose| Method exit: Microsoft.Crm.Setup.SrsDataConnector.SrsDataConnectorSetup.Initialize
    16:39:11|Verbose| Method entry: Microsoft.Crm.Setup.SrsDataConnector.SrsDataConnectorSetup.Run
    16:39:11|Verbose| Method entry: Microsoft.Crm.Setup.Common.SetupBase.Run
    16:39:11|Verbose| Method exit: Microsoft.Crm.Setup.Common.SetupBase.Run
    16:39:11|Verbose| Installing version component: F:\Server\amd64\SrsDataConnector\PFiles\MSCRM\Setup\crmversrsdataconnector.dll
    16:39:11|Verbose| Installing version: 4.0.7333.3
    16:39:11|Verbose| Installing lcid: 1033
    16:39:14|   Info| Window Left: 428
    16:39:14|   Info| Window Top: 233
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNG.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GathererCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GathererCollection.Constructor()
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNG.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Clear
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Clear
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Constructor
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.Constructor
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunAll(False)
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolResults.Clear
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.Run(False, (null))
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.PropagateContext
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GroupCollection.Constructor()
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.GathererCollection.Constructor()
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.GathererCollection.Constructor()
    16:39:17|Verbose| Built gatherer and sniffer collections.
    16:39:17|Verbose| Cleanup completed.
    16:39:17|Verbose| Calling sniffer collect.
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions RunModes
    16:39:17|Verbose| After env var substitutions RunModes
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions Setup
    16:39:17|Verbose| After env var substitutions Setup
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Calling sniffer collect.
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions RunModes
    16:39:17|Verbose| After env var substitutions RunModes
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions Setup
    16:39:17|Verbose| After env var substitutions Setup
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Collection ran.
    16:39:17|Verbose| Collection completed.
    16:39:17|Verbose| Gatherers ran.
    16:39:17|Verbose| Gathering completed.
    16:39:17|Verbose| Calling sniffer process.
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions RunModes
    16:39:17|Verbose| After env var substitutions RunModes
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions Setup
    16:39:17|Verbose| After env var substitutions Setup
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Calling sniffer process.
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions RunModes
    16:39:17|Verbose| After env var substitutions RunModes
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions Setup
    16:39:17|Verbose| After env var substitutions Setup
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Processing ran.
    16:39:17|Verbose| Processing completed.
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions RunModes
    16:39:17|Verbose| After env var substitutions RunModes
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| After context key substitutions Setup
    16:39:17|Verbose| After env var substitutions Setup
    16:39:17|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:17|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunSnifferValidate Microsoft SQL Server™
    16:39:17|Verbose| Calling BaseGroup.Validate
    16:39:17|   Info| Check SqlInstanceNameValidator: Success
    16:39:17|   Info| Check CrmSqlDomainValidator: Success
    16:39:18|   Info| Check SqlServerValidator: Success
    16:39:18|Verbose| BaseGroup.Validate completed
    16:39:18|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunSnifferValidate
    16:39:18|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:18|Verbose| After context key substitutions RunModes
    16:39:18|Verbose| After env var substitutions RunModes
    16:39:18|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:18|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:18|Verbose| After context key substitutions Setup
    16:39:18|Verbose| After env var substitutions Setup
    16:39:18|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.SNGBuilder.ProcessSubstitutions
    16:39:18|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunSnifferValidate Environment Checks
    16:39:18|Verbose| Calling BaseGroup.Validate
    16:39:18|  Error| Check ReportServerValidator : Failure: Unable to validate SQL Server Reporting Services Report Server installation. Please check that it is correctly installed on the local machine.
    16:39:18|   Info| Check ConfigDatabaseExistsValidator: Success
    16:39:21|Verbose| Retrieving config database version Provider=SQLOLEDB;Data Source=ST-STI-DB-01;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI ...
    16:39:21|   Info| Config database version: 4.0.7333.3.
    16:39:21|   Info| Check ConfigDatabaseVersionValidator: Success
    16:39:22|   Info| Check PrivReportingGroupActiveDirectoryRightsValidator: Success
    16:39:22|Verbose| BaseGroup.Validate completed
    16:39:22|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunSnifferValidate
    16:39:22|Verbose| Validation ran.
    16:39:22|Verbose| Validation completed.
    16:39:22|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.Run
    16:39:22|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWTool.RunAll
    16:39:22|Verbose| Method entry: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Clear
    16:39:22|Verbose| Method exit: Microsoft.Crm.Tools.EDW.Framework.EDWToolCallbacks.Clear
    16:43:11|   Info| Do you really want to cancel out of Setup?, Question, YesNo, Option2
    16:43:13|   Info| InputResult: Yes
    16:43:13|   Info| Microsoft Dynamics CRM Connector for SSRS Setup Completed.
    16:43:13|   Info| The installation of Microsoft Dynamics CRM Connector for SSRS Setup has been successfully completed.

    There are no errors in the event logs of either server that give me any kind of clue as to what is going on.

    Thanks

    Thursday, October 20, 2011 3:45 PM

All replies

  • CAUSE
    This error will occur if you install the 64-bit Microsoft Dynamics CRM Connector...This error will occur if you install the 64-bit Microsoft Dynamics CRM Connector for SSRS on a 64-bit machine and Microsoft SQL Reporting Services is a 32-bit installation.

    RESOLUTION
    You will need to install the 64-bit version of SQL Reporting Services on the ser...You will need to install the 64-bit version of SQL Reporting Services on the server in order to install the Microsoft Dynamics CRM Connector for SSRS on a 64-bit operating system.

    Hope this Help.


    Shai Bar-Lev
    Thursday, October 20, 2011 5:18 PM
  • HI

     

    Very helpful, thanks.  The SQL Server has to run the 32 bit version of SQL as it also hosts a database for Microsoft Office Accounting, which doesn't support 64 bit SQL.  Is it possible to install the 64 bit version of SSRS on this server when it has the 32 biot version of SQL?  If this is not possible, can SSRS be installed elsewhere?

     

    Thanks

    Gordon

     

    Friday, October 21, 2011 8:54 AM
  • If the SQL Server is 32 bit , so make sure you install the SSRS Connector 32-bit version.

    You can get it from http://www.microsoft.com/download/en/details.aspx?id=4680 , download DynamicsCRMServer_1033_i386.exe , run it and extract it to a folder for example Server. then look at server\srsdataconnector folder and install from there.


    Shai Bar-Lev
    Friday, October 21, 2011 9:25 AM
  • Can't do this, I'm afraid.  I get an error message that I can't install the 32 bit SSRS connector on a computer running a 64 bit OS.
    Friday, October 21, 2011 9:36 AM
  • You right.

    You'll need another SQL 2008 R2 64 instance/server (see this for side by side possibility if you don't have another machine) http://msdn.microsoft.com/en-us/library/ms143694.aspx.

    on this instance/server you can install the SSRS and then the SSRS connector 64-bit version.


    Shai Bar-Lev
    Friday, October 21, 2011 10:32 AM