Thursday, November 13, 2008 9:04 AMHello Everyone
We are runnung on CRM 3 and are about to upgrade to 4 now. For this reason I installed the DMM on our frontend server and tried to login to http://crm:5555. Somehow this is not working. First I thought the server policy is preventing this, but I am able to call the CRM using internet explorer. I saw that quite some people have this problem, but I couldnt find any solution to this.
If someone could help me out here would be great.
Thursday, November 13, 2008 1:51 PMOwner
Check out these two links and see if they help. You will want to try and load the DMM on a machine other than the CRM server. You may experience a better result if you load the DMM on a client machine using SQL Express. Also, you may need to wait until after you upgrade to CRM 4 to Configure and Run the tool.
Friday, November 14, 2008 12:27 PMThanks.
I thought that I can run DMM to upgrade crm3 data to 4 but as I found out in the links you gave me DMM is only able to connect to a crm 4.0. So I tried to run the server installer pointing it to our existing db but he always claims that he cannot find a crm-database. When I have a look at the server I see Stiki_MSCRM and cdf_mscrm, so it should find it.
Friday, November 14, 2008 1:15 PMOwner
You don't need to upgrade your CRM 3 data to CRM 4. Do the upgrade to CRM 4 by using the option to connect to an existing database. Uninstall DMM until after the upgrade and you can re-install it if you have new data to import.
Friday, November 14, 2008 2:35 PMThats what I am trying...the setup cannot find my existing database. It sais " no configuration database found"
Friday, November 14, 2008 3:12 PMOwner
Ok, don't worry about the uninstall for now. Complete your CRM 4 upgrade and when you are ready to use the DMM, locate the configuration exe and run it. You can reconfigure the DMM to connect to the CRM 4 database after it is upgraded. Here is the file path
c:\program files\microsoft dynamics crm data migration manager\dmclient\configwizard\Microsoft.Crm.DMClient.Config.exe
One additional note, you may need to open SQL and delete the existing data migration database if the configuration wizard complains. Be sure that you do not delete the wrong database. You only want to get rid of the Data Migration database which will have a name like MSCRM_Migration. Complete a full backup before making changes to SQL.
- Proposed As Answer by Donna EdwardsMVP, Owner Tuesday, June 09, 2009 1:59 AM