Wrong Database name showing up in the Deployment Manager RRS feed

  • Question

  • Hi,

    Before upgrading CRM 4.0 to 2011, we built a CRM 2011 staging environment. Then during the upgrade we moved MSCRM_CONFIG from the STAGINGSQL database server to another SQL server (CRMSQL) following the steps in http://technet.microsoft.com/en-us/library/hh699772.aspx. Then we imported the CRM 4.0 organization.

    Everything is working fine.

    Nevertheless, when we open the deployment manager, we see the following:


    Name               Status       Version               Role

    STAGINGSQL   Enabled   5.0.9690.3557  SRS Data Connector, SQL Server

    CRMSVR          Enabled    5.0.9690.3557   Front End Server…

    CRMASYNC     Enabled    5.0.9690.3557   Back End Server …

    REPORTING     Enabled   5.0.9690.3557  SRS Data Connector


    STATINGSQL is the name of our old SQL Server. The entry should be:

    CRMSQL           Enabled   5.0.9690.3557  SQL Server


    How do we change this information in the deployment manager?

    We could go to MSCRM_CONFIG and modify the entry in the table 'server', but we don't like to modify the DB directly and we don't know if this info is used someplace else.



    Christian J. Betrisey

    Tuesday, June 10, 2014 6:38 PM

All replies

  • I haven't ever moved the MSCRM_CONFIG from one server to another. Importing the organization DB into a new deployment has always worked best for me as the necessary entries to the MSCRM_CONFIG are made by the Deployment Manager.

    I would suggest 1 of 2 options:

    1. Repeat Import process of DB WITHOUT manually restoring MSCRM_CONFIG (on a fresh DB).
    2. Reimport the existing 4.0 DB, AFTER changing the organization GUID.

    Hope this helps. If you need clarification, I can try.


    Tuesday, June 10, 2014 8:37 PM
  • Thanks James,

    We cannot really do what you are suggesting because we upgraded from 4 to 2011 over one month ago and it is in production. 

    Looks like this wrong name is not affecting anything. CRM works fine.

    We still would like to change it for clarity.

    BTW I have tried to rename the server name in a test environment and this did not affect it.

    Christian J. Betrisey

    Wednesday, June 11, 2014 1:12 PM