Tribridge Connections

A Technology, Cloud Solutions & Industry Expertise Blog


How to Migrate CRM 4 SQL 2005 32 bit to SQL 2008 64 bit Environment

Published: June 14, 2011

Dynamics CRM 4 Migration from Windows Server 2003 to 2008

I recently migrated a Dynamics CRM 4 implementation installed on a Windows Server 2003, 32 bit environment to a Windows Server 2008, 64 bit environment. I decided to document the process in the event that the information might be helpful.

Please keep in mind that CRM environments vary and the steps you take to complete a similar migration might vary depending on the environment that you’re migrating.

  • Review the article “Support for running Microsoft Dynamics CRM 4.0 together with Microsoft SQL Server 2008
    • Save the link for later use as needed
  • Install Windows Server 2008 64-bit OS
  • Review
  • From the SQL media, right-click the setup application and select run as administrator
  • If you see the following, select the option to check for run the program
    • You’ll need to install SQL 2008 SP 2 after you finish the install
              CRM 4 SQL
  • If you receive the following message
        Microsoft Dynamics CRM 4 error message
  • You must enable .Net Framework 3.5.1 from server manager
  • Select features, add features
        Add CRM SQL required features
  • Select to add required features
    Add features to .NET Framework 3.5.1
  • Select next & install
  • From the SQL media, right-click the setup application and select run as administrator
  • If you see the following, select the option to check for run the program
  • You’ll need to install SQL 2008 SP 2 after you finish the install
  • Review through the articles & run the tools from the SQL Installation Center (at a minimum)
  • Security documentation
  • Online release notes
  • System configuration checker
        CRM 4 SQL media
  • Select “Installation” from the left navigation menu of the SQL Installation Center window
  • Select “New SQL Server……."
        SQL Server installation center
  • Walk through the installation setup wizard
  • Complete the installation by selecting the correct options
  • Open SQL management studio and ensure the settings are as expected
  • Download & install SQL 2008 SP2 or the latest SP for SQL 2008
  • Ensure you can access the report server
  • Install .Net Framework 3.5 feature if it is not already added
    • Open server manager
    • Select features
    • Select add features
    • Select .Net Framework 3.5.1
    • Select install
  • Install IIS 7 if it is not already added
  • Install IIS 6 compatibility components if they are not already added
    • Open server manager
    • Select roles
    • Right-click web server (IIS)
    • Select add role services
    • Select IIS 6 metabase compatibility and IIS 6 management console
    • Select install
  • See Support for Microsoft Dynamics CRM 4.0 on Windows Server 2008-based computers for a list of all 2008 server roles required and troubleshooting tips
  • Download & install the CRM application
    • Select the option to run as administrator by right-clicking setupserver.exe.
      • Be aware that the user login used to install CRM 4 will, by default, be assigned a system admin user account
      • This will help to minimize any unexpected rights issues
      • Select update installation files when you receive the prompt
    • Open CRM from the IE browser to confirm everything is working as expected
    • Follow-up with any final changes need documented
      • Support for Microsoft Dynamics CRM 4.0 on Windows Server 2008-based computers
    • Apply the update rollups that match your current CRM installation
      • This is a good time to get your CRM applications updated to the latest or close to the latest update rollup release for all components
        • SSRS, E-mail Router, Server…
    • Open CRM and ensure everything is working
    • Check the event viewer and address any errors in the application log
  • Review the steps in this article to move your CRM application from one server to another and save for reference as needed
    • See the section, “Redeploy the Microsoft Dynamics CRM deployment that includes the Microsoft Dynamics CRM Server within the same domain or to another domain”
  • Prep work before attempting the import
    • Ensure all custom code to include plug-ins and other customization is removed from the database. This will increase your chances of having a successful import. The current Organization database should be in a fully supported state.
    • Ensure you have at least rollup 8 on both servers (your current CRM server and the server where you plan to run the import)
      • You may need to right-click the update rollup file and select run as administrator
    • Ensure the database on the new server is set to simple recovery mode and your log files are set to allow for growth
      • You can change these settings as needed after the import is completed
    • Set the registry key on the new CRM server as explained in KB Article 977867
    • Ensure the users who are performing the restore have full permissions on the SQL and CRM server directory files
  • Backup your current organization database and place the backup in a directory that you can access from the new CRM machine
    • You only need to back up the CRM organization database, OrgName_MSCRM.
      • Do not backup the MSCRM_CONFIG database
    • Restore the OrgName_MSCRM to the new SQL Server
      • I am not going into the restore steps in this article with the exception of mentioning that you should not select to overwrite the existing database when you do the restore of select any of the other checkmarks available on the options page
        • Once you have a successful organization import, you can come back to SQL and remove the initial (temp) database that was related to the initial Dynamics CRM 4 installation as you will no longer need it
      • Restart your SQL machine or the services to ensure everything is working as expected. I prefer to reboot the machine(s) to ensure everything is working as expected.
      • Ensure you can still access CRM from the web browser
        • Check the application log on the event viewer and resolve any issues
        • You want to ensure both your SQL and CRM environments are working as expected. If both applications are on machine then you have only one environment to check.
  • Open deployment manager on the CRM machine
  • Select organizations from the left navigation menu
  • Select import from the right navigation menu
        Deployment manager in Dynamics CRM 4.0
  • Walk through the import wizard. It is fairly self explanatory.
    • Select yes to create a new organization
    • Enter the SQL server name where you restored the OrgName_MSCRM backup
    • Select the organization database from the drop down
    • Select next and enter your display name
      • This will be your CRM organization name so you may want to keep it the same as your existing organization
    • Select next and enter your Report Server URL http://CRMSqlServerName/ReportServer
    • Select next and leave the default auto map users
      • Unless you need a different option
    • Select next and resolve any errors related to disabled users or users still in CRM but no longer in active directory
      • Review the user mappings as needed and select next
      • Select yes to this message unless you want to make additional changes to the user mapping
    • Select next and resolve any errors that display on the system requirements dialog window
      • You will receive the warning, “The organization database selected for import is a different version than the organization database that is currently deployed”
        • It is ok to ignore it
    • Select next and review the settings to confirm it is what you want
    • Select import and wait for the import to complete
  • Timeout errors
    • How to resolve a timeout issue related to the following errors
    • Always reboot the CRM server after these types of changes and check to ensure everything is working as expected when the server comes back online
      • Open the CRM application to ensure it is working, check the application log for errors, etc. This helps to ensure you are working with a stable environment
    • Certain custom reports can sometimes result in the error “The connection’s state is closed”

There you have it! The steps needed to migrate SQL 2005 32 bit to an SQL 2008 64 bit environment. If you have any questions on this migration process, please feel free to comment below.

Share Your Thoughts With Us

Load more comments
Thank you for the comment! Your comment must be approved first