Keep following things in your mind if you are upgrading from MS CRM 3.0 to CRM 4.0
Perquisites
- SQL Server 2005 with SP 2 should be up and running.
- Back Up of Metabase Database (OrgName_METABASE Database)
- Back Up of MSCRM Database (OrgName_MSCRM Database)
Restore Production Database
.Bak files
- Create new Databases (one for MSCRM and another one for Metabase) on the given server
- Note: – Name of the databases should be same as it is in previous instance for e.g. MSTVCRM_METABASE, MSTVCRM_MSCRM.
- Restore the databases with the backup database accordingly.
.sls files (Sql Light Speed)
- Install SLS tool from products web(third party tool) as per installed OS (32bit or 64bit)
- Run – xp_sqlitespeed_version – to know SQL Light Speed version.
- Note – Version mismatch will not restore the DB properly
- Restore the METABASE and MSCRM Database using SQL Light Speed tool.
Run CRM 3.0 Redeployment Wizard and Take back up.
- Install the CRM 3.0 Redeployment tool if it not installed on the machine from products web.
- Before running the redeployment wizard set one of the users setupuser value should be 1 in systemuser entity. If not, update the value of setupuser to 1 for one of the record in systemuser entity.
SELECT * FROM Systemuserbase WHERE Setupuser = 1
Note – If the above query returns any records then no need to run the below query. Run update statement only if the above select query returns Zero records.
UPDATE Systemuser
SET Setupuser = 1
WHERE domainname = ‘domain\alias’ —– Provide the valid user alias whom you want to set setupuser = 1
- After this run Redeployment Wizard of Microsoft Dynamic CRM 3.0.
- Provide the SQL Server name and Select MSCRM Database and click next
- Provide the appropriate Organization name (Usually taken from Prod DB back up file name after removing MSCRM DB name) and Click next
- User Mapping section will be displayed with following options[1. Keep the existing user mapping, 2. Manually Map the Users, 3. Automap the user].
- Select the appropriate user mapping depending upon the instance or project and click next.
- Note – If you select keep the existing user mapping option then map the install user with one of the user in the list displayed to new user column by double clicking.
- It starts installing Microsoft CRM server components along with the database transformation will start.
- Click on Finish button once redeployment is over
- Take the Data base back after CRM 3.0 Redeployment and rename the file accordingly.
Install CRM 3.0
- Launch CRM 3.0 Installer ( executable file serversplash.exe) from Products Web (Archive).
- Provide the Valid License Key and click Add (before that query – Select * from License).
- Accept the Terms and Conditions and Click Next.
- Installer will install all the required components (MSXML 4.0 Hot fix) and Click Next
- Provide the Valid Organization Name and Click Next
- Click Next on Help CRM us to improve the customer experience window
- Select the Website (There are 2 options Select any one of them) [1. Select the Default website, 2. Create new Website with Port Number 5555]
- Select SQL Server Name [1. Select the SQL Server Name, 2. Select the Option to Connect to existing Data base option (it will show both METABASE and MSCRM Database. Click Next.]
- Reporting Server – Provide the Valid URL to connect to Report Server (Before running this step make sure that Report server working by browsing the URL you get in this step).
- Specify the Network Account – Select the default option and Click Next
- Specify the Exchange Server Setting (Leave it blank and click Next). A warning will popup and click on OK on the warning Message.
- CRM 3.0 Installation will start after displaying summary of settings selected.
- Click finish button on successful installation of CRM 3.0
- Take the back up of CRM 3.0 (both MSCRM and METABASE) after installation.
- Restart the Server
- After restarting stop the Microsoft Workflow Manager Service.
- Browse the MS CRM application and verify the redeployed application.
- Publish all the customization.
- For further assistance refer the attached MicrosoftCRMv3Redeployment.pdf file
Upgrade CRM 3.0 to CRM 4.0 on existing DB
Note: – To improve server performance before starting Upgrade processes do the following steps
In registry add under MSCRM DWORD Hexadecimal value
ExtendedTimeout – 90000000
OLEDBTimeout – 1500
- Go to Run
- Type regedit
- Navigate to HKEY_LOCAL_MACHINE | SOFTWARE | MICROSOFT | MSCRM
- On the File Menu | Click on Edit | NEW | DWORD Value
- Add first Parameter “ExtendedTimeout”
- Double click on the parameter to add hexadecimal value and set 90000000 as its hexadecimal value
- Follow the same steps for adding OLEDBTimeout Parameter.
Steps for up gradation of MSCRM 3.0 to MSCRM 4.0
- Start the SQL Server Agent.
- Stop Microsoft Workflow Manager service.
- To Start the MSCRM 4.0 Server installations run the splash.exe executable file.
- It will ask for Update Installation file. Click on that it will copy MSCRM set up files to temporary folder.
- After copying all these files click on Next.
- Give the License Key and click on Next.
- Accept the terms and conditions and click on Next.
- It will ask for the Installation of the required component like MS Visual C++ Runtime. Install this and click on Next
- Start Up grading Microsoft Dynamic CRM 4.0 from 3.0. Click on Next.
- Organization name will come automatically.
- Select the currency as Dollar ($) USA and click next.
- Before proceeds further check the Report server running or not. It should be in a running condition.
- Give the Email Router name (Provide the Name of the Server) and click next.
- Install system required component.
- To upgrade click on Upgrade button.
Upgrade Fails then follow the below mentioned Steps
- Uninstall the MSCRM 4.0 instance
- Delete the MSCRM related databases from the server and restore the MSCRM 3.0 databases once again.
- Remove the Microsoft Dynamic CRM website from the IIS.
- Edit the registry for the Local Machine. Delete MSCRM registry under the Microsoft.
- Redeploy and install the Microsoft Dynamic CRM 3.0 and try to run the Upgrade Process.
