Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 4 - Data Migration Manager "Encountered an error" RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Having real trouble getting DMM to work with a fresh CRM install.

    Installed DMM and initially it just bounced back to the login button.  Then I got a lengthy "...encountered an error" paragraph.

    - Installed Rollup 14 on the web server (didn't seem to require 6 and 7 as prerequisites!!)

    - For DMM I had to install 6, followed by 7 and then 14.

    - We have a domain user as the App Pool identity.  As I saw in another post, I gave this full control of the CRM Program Files - Install directory.  (At this stage I had an Event Log error which discussed an Outlook Offline component - assumed this was a component that was reused for DMM rather than having anything to do with Outlook).

    Now I am getting a short "DMM has encountered an error" message when I click on Login.  Not very informative at all.  Seems to happen during the sync part.

    The server is W2008 R2 and I have tried DMM on 2 laptops with XP and W7.

    The only unusual aspect to the CRM installation was that the client installed as the Domain Admin.  I have gone through and added the CRM Admin user and CRM Security User to all the correct places as far as I can tell (as per the white paper).  CRM and Reporting Server are working fine so that reinforces that everything is correct.

    Also have reinstalled DMM with SQL Express and SQL Server 2005 a few times.  Tables are built but the thing can't seem to sync (No data yet so presumably the customizations).

    Any suggestions in getting to the bottom of this.

    • Edited by Gordon Johnston Thursday, January 27, 2011 9:14 AM Typing errors
    Thursday, January 27, 2011 9:06 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Well it is now working.

    I turned up, uninstalled the previous instance, installed the new one and immediately applied Rollups 6, 7, and 14.

    I started the application, configuring it for local SQL Express and it worked.

    No idea why it didn't work the previous 6 times I tried to run it.

    Some thoughts:

    - Perhaps the CRM Server Rollup 14 had installed but (although not requiring a reboot) somehow, some aspect of the new schema hadn't been reflected in its interaction with DMM.  The server admin wasn't aware of a web server reboot but I can't rule that out.

    - Perhaps I hit on the correct order to do the install.  I installed the DMM Rollups before attempting to connect and configure (sure I did that in a previous attempt though)

    - Perhaps the client had been rebooted and that caused an update.

    - Perhaps DMM just needed a rest!

    Still doesn't work with SQL Server but I have read there is an issue where the DB files are stored on a different drive (in this case "D:" on the remote SQL Server).

    So, sorry I can't provide a better answer.  Someone can feel free to attach their experiences to the thread as it may save someone hours of frustration and help pinpoint the likely solution for the next victim.

    Wednesday, February 2, 2011 9:31 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Gordon, you've given a detailed run down of what's installed, which is helpful but unfortunately you are encoutering an error after doing everything right! (Usually the problem comes when DMM is installed on the CRM server).

    The only thing I can suggest at this point is to install DMM on a PC that doesn't have the Outlook client installed as the authentication mechanisms might be conflicting. Or try and find some kind of DMM trace log.

    Neil

    Neil Benson, CRM Addict and MVP at Customery Ltd. You can reach me on LinkedIn or Twitter. Join over 10,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Friday, January 28, 2011 11:22 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the advice. I will be back on site early next week so my plan of action is:

    - I will use the CrmDiagTools4 to turn on tracing on the web server.

    - I will then try DMM again and hope that it logs a trace file.

    Presumably DMM doesn't have it's own trace, it will simply try to get something from CRM and cause the server to spawn a trace, hopefully containing the real error!!

    - I will see if I can get a fresh client also.

    It seems odd that DMM can't return a meaningfull error. I mean, all the systems involved are Microsoft so surely they can crack open their own SOAP massages etc and provide an Event Log item or something on either the client or the server. This isn't the first time I have approached DMM as being an easy install (compared to CRM for example) and then been, seemingly, surrounded by frustrating dead ends as I try to make it work. I will report back on what I find.

    • Edited by Gordon Johnston Friday, January 28, 2011 11:31 AM formatting went wonky!
    Friday, January 28, 2011 11:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Both CRM 4 Web Server and DMM Client have trace logs:

    http://rc.crm.dynamics.com/rc/regcont/en_us/op/articles/migrationtroubleshooting.aspx#o31750

    I will turn those on when I attempt the install again later today.

    Tuesday, February 1, 2011 8:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well it is now working.

    I turned up, uninstalled the previous instance, installed the new one and immediately applied Rollups 6, 7, and 14.

    I started the application, configuring it for local SQL Express and it worked.

    No idea why it didn't work the previous 6 times I tried to run it.

    Some thoughts:

    - Perhaps the CRM Server Rollup 14 had installed but (although not requiring a reboot) somehow, some aspect of the new schema hadn't been reflected in its interaction with DMM.  The server admin wasn't aware of a web server reboot but I can't rule that out.

    - Perhaps I hit on the correct order to do the install.  I installed the DMM Rollups before attempting to connect and configure (sure I did that in a previous attempt though)

    - Perhaps the client had been rebooted and that caused an update.

    - Perhaps DMM just needed a rest!

    Still doesn't work with SQL Server but I have read there is an issue where the DB files are stored on a different drive (in this case "D:" on the remote SQL Server).

    So, sorry I can't provide a better answer.  Someone can feel free to attach their experiences to the thread as it may save someone hours of frustration and help pinpoint the likely solution for the next victim.

    Wednesday, February 2, 2011 9:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Should have also said that, in this case

     

    - Outlook was on the machine

    - Since the install worked first time, I never got the opportunity to see the Trace Logs fill up.

    Wednesday, February 2, 2011 9:34 AM