You’re offline. This is a read only version of the page.
2,100
Greetings,
I've just completed a CRM 4.0 implementation at a client site and the system is in production and working well.
However, a new requirement from the company's IT department states that all CRM instances must use the existing centralized SRS server. (I know, great for them to change that now!)
Technically you wouldn't think that switching to the centralized reporting server would be a problem, but there's a catch -- the company already has another CRM 4.0 instance up and running and the Data Connector was installed on the SRS server.
One more thing, they don't want to enable Kerberos authentication. It's a big company and they have their standards... you know the story.
My question, then, is whether there's any way to support their requirement to use the same SRS instance for two separate CRM instances (different web and sql servers). From what I've read about the Data Connector, once you install it and point it at a SQL Server instance then you've committed to that one SQL server -- you can't (I don't think) run the Data Connect setup again and point another instance of it at a different SQL server. Nor can the existing Data Connecto point at multiple SQL servers -- that wouldn't make sense.
I think the answer is to tell the client that they either need to 1) uninstall the Data Connect and enable Kerberos (and work through the double-hop issues) or 2) keep SRS where it is for the second CRM instance and bend the rules.
Have any of you faced a similar server configuration and come up with any way to support this? I thought I'd check before finalizing my report back to our client.
Thanks!
-Tim
Altriva Solutions, LLC / Bellevue, WA
*This post is locked for comments
I have the same question (0)
Hi Tim,
did you get a solution for that problem in the meanwhile? I've exactly the same situation. I've performed this steps but did not test it completed.
1. Go to the SRS server that holds the data connector installation.
2. Open regedit and navigate to HKLM\SOFTWARE\Microsoft\MSCRM
3. Change the parameter of configdb to your different database server
example
from
Data Source=SERVERNAME\INSTANCENAME;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI
to
Data Source=NEWSERVERNAME\INSTANCENAME;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI
4. Start the installation wizard which is prompt you to uninstall or repair the installation.
5. Click on repair and follow the steps, at the end you can find that he is trying to repair the NEWSERVERNAME
6. Finish the repair and change the registry settings back.
This updates the MSCRM_CONFIG Database and allows you to keep your Reporting Server. I hope you have a better solution because I guess my way is not really a solution :-/
Thanks.
Christian
Share
Report
All responses (
Answers (
