Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Installing CRM 2011 Reporting Extensions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have two servers:  one running CRM 2011 Rollup 12 (call it A), the other SQL Server 2012 SP1 (call it B).  I have SRSS working properly on B, i.e. both the web service URL and the report manager URL work fine.  However, installing CRM Reporting Extensions on B always gives me...

    |  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.

    ... with no indication as to why in the log.

    How can I troubleshoot this?  I.e. where is the reason for this logged?

    Thanks.


    • Edited by tuyoix Monday, March 11, 2013 7:57 PM
    Monday, March 11, 2013 7:51 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    As my luck would have it, I was being misled into believing that the installation files I was using were from Rollup 12, when in fact they predated even Rollup 4.  Correcting this and a few other things allowed me to successfully install the connector.  I am now left with a much smaller glitch that will be resolved when the fix for KB2825497 is released.

    Thanks to all who responded, and sorry for the noise.

    Saturday, March 23, 2013 3:06 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please go through following links which will be helpful to you,

    http://weblogs.asp.net/pabloperalta/archive/2011/07/12/unable-to-validate-sql-server-reporting-services-report-server-installation-error-while-installing-srs-data-connector.aspx

    http://community.dynamics.com/crm/b/pabloperalta/archive/2011/07/12/unable-to-validate-sql-server-reporting-services-report-server-installation-error-while-installing-srs-data-connector.aspx#.UT6yttZHJKY

    http://www.martinfiala.net/archive/2012/05/18/unable-to-validate-sql-server-reporting-services-report-server-installation.aspx

    http://social.microsoft.com/Forums/en-US/crm/thread/31210802-711c-4fa7-8560-d0ec7db4a5ab/

    Thanks & Regards, MS CRM Consultant, V.Surya. My Blog: http://inventcrm.wordpress.com/

    Tuesday, March 12, 2013 4:49 AM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've already tried all of those, and then some.  The patch mentioned is for CRM 4.0, not CRM 2011, let alone Rollup 12, and the /config trick simply doesn't fix anything.

    I've already spent days Google'ing this thing to death, and simply repeating some of the suggestions in those searches isn't at all productive.

    So I'll ask again:  Where, IN A *LOG*, can I find what it is really complaining about?  Or is this just another one of those generic thou-canst-investigate-this-no-further messages?  Simply saying "an error occurred" just doesn't cut it.

    Thanks.

    Tuesday, March 12, 2013 2:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Try this,

    http://www.jaydien.com/blog/servers/installing-crm-2011-reporting-services-on-sql-2012.html

    http://support.microsoft.com/kb/2223769

    https://plus.google.com/100076956951768563759/posts/TkADBJar2pE

    Wednesday, March 20, 2013 11:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

    Please go on SQL Server => SQL Server configuration manager => SQL SERVER Network configuration => Protocols for MSSQLSERVER(Instance) => Change status to ENABLE for 'Named Pipes' protocol.

    Start installation again after rebooting system once.

    OR you can mention IP Address instead machine name in URL like for URL 'http://sys_name/reportserver' you can mention 'http://IP_Address/reportserver' 

    Verify this once in browser. 

    Thanks!

    Pradeep.

    Thursday, March 21, 2013 7:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As my luck would have it, I was being misled into believing that the installation files I was using were from Rollup 12, when in fact they predated even Rollup 4.  Correcting this and a few other things allowed me to successfully install the connector.  I am now left with a much smaller glitch that will be resolved when the fix for KB2825497 is released.

    Thanks to all who responded, and sorry for the noise.

    Saturday, March 23, 2013 3:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Modify the Install-config.xml file

    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:    
      <var>drive</var>:\Server\i386
          The <var>drive</var> placeholder represents the CD drive.
    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.
      • 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
    3. If the server that is running SQL Server 2005 Reporting Services has a named instance, modify the instancename tags.
    4. After you complete steps 3 and 4, click Save on the File menu, and then close the Install-config.xml file.
    5. Open a Command Prompt window, and then locate the folder in which you copied the installation files in step 1.
    6. At the command prompt, type the following command, and then press ENTER:    

      C:\SrsDataConnector> SetupSrsDataConnector /CONFIG <var>path of the folder that contains the Install-config.xml file</var>\install-config.xml

    This might be helpful, if so mark this as "Answer" or "Vote as helpful"

    • Proposed as answer by nrodriEditor Thursday, April 4, 2013 9:28 AM
    Monday, April 1, 2013 6:20 AM