• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 261
  • Last Modified:

Reinstalling a named instance of Dynamics CRM SSRS Data Connector

I need to repair (after change of service account and loosing encryption settings) one of the CRM Reporting named instances running of an SQL 2012 Server.
During the repair process, only one instance (alphabetically) is visible to SrsDataConnector, the one I don't want to change.
I read that the command line option is available but how to use it for repair?

SetupSrsDataConnector /Q /CONFIG folderpath\install-config.xml
Thanks in advance!
  • 3
  • 3
1 Solution
Feridun KadirPrincipal ConsultantCommented:
I'm confused by your question, because I thought the SSRS Data Connector could only be installed once on a server and therefore only configured for one instance of SSRS.

The fact that your are only seeing one instance during repair is expected.
IT-NYCAuthor Commented:
After i posted the question, I discovered this in the MS document.
So, I went to another server and tried to install it fresh (there are 2 instances of SSRS but that is Ok, right?). Ran it as Reports account. Installed a new organization, it went smooth but I still cannot see the reports. The error is "Error occurred while fetching the data extension"
The reporting server URL is correct, I can browse all of the default reports. I granted the Reports account Sysadmin and publisher right inside of SSRS site but no luck.
I have a few questions.
1. Which account should be used to run SSRS service?
2. Which account should be used as service account inside of SSRS Configuration page?
The account has the rights to the databases (config, CRM, Reports).
Any advice is appreciated.
Feridun KadirPrincipal ConsultantCommented:
I'm not sure I've followed the sequence of events in your case but this is the usual procedure:
  1. Install SQL Server using a domain account (if not already installed)
  2. Install SSRS using a domain account (on the same server as SQL or a different server, it doesn't matter for CRM
  3. Install CRM Server - during the install you specify the SQL Server and SSRS server to use
  4. After CRM Server is installed, install Reporting Extensions on the server that was specified for SSRS during the install of CRM Server. If more than instance of SSRS is installed on the server, select the one that was used for CRM.

A regular domain account should be used for SQL and SSRS, CRM doesn't care what these accounts are. You should not need to assign any rights to databases manually. All of that is taken care of during the install of SQL, SSRS and CRM.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

IT-NYCAuthor Commented:
Thanks for the information.
In my case, we are trying to use Reporting Services that are different from the original Reporting Services    Server, say, SQl2 instead of SQL1.
So, currently, there is a mix of several organizations. One of them points to SQl1, Two of them point to SQL2. The idea is to move it to SQL2 altogether.
Reports don't work in any of the organizations.
Is it possible that the cause of this is that, in the deployment guide, it says:
"Although, in a multiple organization deployment of Microsoft Dynamics CRM, you can specify different Reporting Services servers or server instances when you create or edit an organization, only one instance of Reporting Services is supported for all organizations in the deployment. "
And I have to move all of them before any other troubleshooting steps will take place?
Feridun KadirPrincipal ConsultantCommented:
Well I guess it is possible that is the reason.
I think I would backtrack and start again.
  1. By this I mean uninstall the CRM Reporting Extensions from all SQL Servers.
  2. Determine which SSRS instance you will use, sounds like SQL2 from your previous comment and make sure the SSRS isntance is working
  3. Then in CRM Deployment Manager, review the properties for each organization and ensure that the SQL Server Reporting Services URL is pointing to the correct (SQL2) SSRS instance.
  4. If it isn't, disable the organization, and then edit the organization to correct the SSRS URL, but don't change the SQL Server value - that is where the CRM database is stored. Enable the organization.
  5. Finally, install Reporting Extensions on the server running the SSRS instance.
If reports still don't work you might need to set Service Principal Names for some service accounts but that is another story. See if the above works first.
IT-NYCAuthor Commented:
I appreciate your effort. After moving all of the organizations SSRS settings to SQL2 (one org db and MSCONGIG db are still on SQL1), in one of the organizations, reports started to work!
Then, they stopped with Web service request GetParameters to Report Server failed. Error: The attempt to connect to the report server failed.  Check your connection information and that the report server is a compatible version.
I will close this question and open a new one in a few days.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now