Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2011: SSRS Extension Installation does not display SSRS Instance RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    I'm trying to install the SSRS extension on the SSRS server for CRM 2011.

    This is an existing instance upgraded from 4.0. So it used to have the 4.0 connector installed.

    I've uninstalled the existing 4.0 connector, then gone to install the 2011 extension. I get to select the SQL Server instance, but then I'm confronted with an empty box where I'm to select the SSRS instance.

    I know the selected SQL server does have SSRS running on it. Also it did already have the 4.0 connector installed.

    SQL Server/SSRS Version: SP1 (10.0.2531)

    Any ideas?

    Monday, July 18, 2011 5:10 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ken,

    I did get this solved in the end but not in the ideal way. When I was working with our infrastructure team on this issue, they assumed that they would simply rebuild the server as their standard fix to any issue. Once it was rebuilt (and I reinstalled all the CRM components again), all is well. My guess (knowing the history of the server) is that the SSRS instance may not have been a supported instance. Ensure that the SQL Server and SSRS instance both mees the minimum requirelts of CRM 2011.

    • Marked as answer by SiN_1 Sunday, August 26, 2012 10:37 PM
    Sunday, November 20, 2011 9:05 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Can you type in the SSRS instance (i.e. "servername\instance") in the text field and proceed?

    If so, do the system checks (aka EDWs) pass with the specified instance?

    Thanks,
    Michael


    Monday, July 18, 2011 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No. The installer only provides option to select on from an auto detected list.
    Tuesday, July 19, 2011 2:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes, you are right. I forgot that Reporting Extensions setup handles this a bit differently than Server setup. Reporting Extensions takes the config db SQL server name on one page and then the SRS instance name on the next page. Please note that the Reporting Extensions will only look for local instances of SSRS.

     

    Since the drop down is behaving oddly, another thought is to run Reporting Extensions setup with a config file.

    1. Prepare a config file and specify your instance name in the config file. Here is a sample config file:

    <crmsetup>

    <srsdataconnector>

    <configdbserver />

    <autoupdateconfigdb>1</autoupdateconfigdb>

    <autogroupmanagementoff>0</autogroupmanagementoff>

    <instancename>MSSQLSERVER</instancename>

    <patch update="false" />

    </srsdataconnector>

    </crmsetup>

     

    2. Run Reporting Extensions setup from the command line with the config file that you just created.

    cmd> SetupSrsDataConnector /Q /CONFIG folderpath\install-config.xml /L c:\logfiles\crm\log.txt

     

    For more information on using the command prompt to install Reporting Extensions, here are some helpful TechNet links.

    http://technet.microsoft.com/en-us/library/gg554828.aspx

    http://technet.microsoft.com/en-us/library/gg554829.aspx

    Let us know if this helps.

     

    Thanks,
    Michael

    Thursday, July 21, 2011 5:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sin_1

    I had the same issue recently running SQL 2k8 R2.  I was running the installer from an application server and pointing it to the SSRS server.

    I fixed my problem by running the installer from the SSRS report server where the instance is running.. this resolved the SSRS instance ..

    Also, I have read that an install of SQL service pack 2 resolves this issue.  however I cannot confirm that as it was not my solution (SQL service pack 2 cannot be applied to R2).

    Cheers

    Brett

     

     

     

    Thursday, July 21, 2011 11:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks guys,

    I did consider using the config xml install option, but I'm not really confortable with going around a problem with the risk of hitting another problem as a result. I'd rather confirm the issue and resolution as we won't have options to play around like this when we move to production.

    Brett, good see you :) I did also hear elsewhere that SP2 helped. But considering SP1 is the minimum requirements in the IG, I'm going to have a hard time convincing the infrastructure team to upgrade with no promise that it will help.

    Kia

    Monday, July 25, 2011 1:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    can you ensure that the user login that you are using to install the reporting extensions has full rights on the sql machine.  Also, ensure that the reporting service account login has rights to the sql server.

    Regards, Donna

    Friday, July 29, 2011 2:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the installing user who is Sys admin and so is the SSRS service account.

    They're both also Local admin account.

    There's been a recent update to the installed. I noticed that this morning when I tried to install it again. So the installer no longet asks for the SSRS instance. Instead it installs "successfully" but CRM still complains that the SSRS Extension is not installed.

    So I tool a closer look at the successful install's log file and the only suspicious thing I see is the following warning:

    • 12:32:27|Warning| Instance Name needs to be escaped. Management Exception: Invalid namespace
      12:32:27|   Info| Escaped Instance Name is RS_MSSQLSERVER
      12:32:28|   Info| Window Left: 548
      12:32:28|   Info| Window Top: 308

    My SSRS instance is at MSSQLSERVER.

    I don't know what's going on as the installer doesn't ask for the SSRS instance name any more.

    Monday, August 1, 2011 4:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    so is SQL Report Server on the SQL machine or on its own machine?  Were you able to configure the Report Server without issue?  Are you able to access the report server form a URL http://ReportServerName/reportserver

    Also, I am not clear on what you mean by the installer is not asking for the SSRS instance.  Do you mean it is not asking for the SQL instance name?

    Regards, Donna


    Thursday, August 4, 2011 1:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I get this same thing, totally confused on what to try next.  Without this we can't add organizations into crm 2011?  Did anyone solve this?
    ken
    Saturday, November 19, 2011 9:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Before proceeding with the Reporting Extensions setup, make sure there is no existing installation. Open Add/Remove Programs and uninstall Microsoft Dynamics CRM Reporting Extensions if present.

    Some things to note:

    1. Make sure you run Reporting Extensions setup from the server running SQL Server Reporting Services. If you have split the Reporting Services component from the SQL Server hosting the Reporting Databases, you must run the Microsoft Dynamics CRM Reporting Extensions setup on the server running the SSRS service, not SQL Server.
    2. During Reporting Extensions setup, make sure you point to the SQL Server hosting the MSCRM_CONFIG database of CRM 2011.
    3. If you use separate SQL Servers for hosting the CRM 2011 databases and for the SQL Server Reporting Databases, you must use a setup config file as outlined by Michael Guthmann above.

    If the above doesn't help, please outline exactly what the environment looks like (how are the CRM components, the SQL Servers, and SSRS layed out) and the steps taken to install the Reporting Extensions.

    Thanks,

    Matios

    Saturday, November 19, 2011 10:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ken,

    I did get this solved in the end but not in the ideal way. When I was working with our infrastructure team on this issue, they assumed that they would simply rebuild the server as their standard fix to any issue. Once it was rebuilt (and I reinstalled all the CRM components again), all is well. My guess (knowing the history of the server) is that the SSRS instance may not have been a supported instance. Ensure that the SQL Server and SSRS instance both mees the minimum requirelts of CRM 2011.

    • Marked as answer by SiN_1 Sunday, August 26, 2012 10:37 PM
    Sunday, November 20, 2011 9:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    BTW, the RTM and RC versions of 2008 are not supported.
    Sunday, November 20, 2011 9:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Brett,

    I have the exact same issue with sql 2008 r2. I coppied the Reporting Extensions setup files to the sql server, and try to run it from there, but still I get a blank list.

    can you please explain me how exactlly did you run the setup?

    regards,

    Sharona

    Tuesday, December 13, 2011 9:30 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Please see second statement of this article: http://msdn.microsoft.com/en-us/library/hh699807.aspx

    It does state that the Data Connector setup is required to be run on the host of Report Instance (SQL Server). If you try and run the Reporting Setup Wizard on the server hosting the CRM services this will not work.

    In my case, I have a two server integration. CRM on one, SQL on the other. Running the setup for this connector on the SQL server allowed the SSRS Instance to show. Hope this helps 

    • Proposed as answer by blue-bullet Friday, August 24, 2012 12:08 PM
    Friday, August 24, 2012 12:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I had this problem trying to install it in the CRM Server, I needed this installed because I couldn't create a CRM Organization with this error: "Microsoft Dynamics CRM Reporting Extensions must be installed on SQL Server Reporting Services for reports to work"

    What I have done is copy the SrsDataConnector folder to the SQL Server and install there.

    The installation finish well and now I can create the CRM Organizaion. 

    Hope this helps!

    • Proposed as answer by Brennan Lynch Sunday, April 21, 2013 4:28 PM
    Wednesday, November 14, 2012 4:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Install SQL Server 2008 SP2 for Reporting Services

    Microsoft Certified Solution Specialist

    Wednesday, February 27, 2013 11:41 AM