CRM 4.0 Data Migration Manager in Multi-tenant Environment

You have installed CRM 4.0 and you want to migrate data using the data migration manager into the Organization.

OK, You know what to do!

Install Data Migration Manager on one of the workstations > Configure it for the Organization and continue your migration using DMM (Data Migration Manager)

Now, you created another Organization in CRM (Multi-Tenant) and you want to migrate data into the new Organization. The good news is you can do it, the how is what you have to live with. Install DMM on another workstation > This time configure it with the new Organization you just created and proceed with the migration

or

Completely uninstall DMM and reinstall it. This time configure it for the other Organization. Before reinstalling the application, you need to manually delete the database or rename it. The setup will create a new database for the new installation of DMM, and will fail if the database already exists. The database that needs to be deleted is MSCRM_MIGRATION.

Microsoft Dynamics CRM 5.0

Too early to have such a title. Did you think the same?

Well, Microsoft has announced the next release of CRM around the end of 2009. You might want to check out for yourself.

I'm looking forward to it, are you?

Thank you MVPs & other Community Members

Way to go!

MSCRMAsync error in Event Viewer

Lately I encountered another interesting error during CRM implementaion. After installing Update Rollup 4, I noticed MSCRMAsync Service in the Event Viewer throwing an error at regular intervals.

Google looked around the world wide web and brought to me that .Net Framework 3.0 SP1 was missing. I downloaded and before it could finish installation, it threw another error and took everything down (including SQL Server 2005). I un-installed Update Rollup 4 for CRM, .Net Framework 3.0 and .Net Framework 2.0. Re-installed them again in this manner

• .Net Framework 2.0
• .Net Framework 2.0 SP1
• .Net Framework 3.0 &
• .Net Framework 3.0 SP1
• Update Rollup 4

after which everything seem'd to be perfect. Event viewer was error spotless.

If you've received a similar error but had a different solution, I'm sure you want to share it as a comment.

Microsoft Dynamics CRM Server Setup did not complete successfully

Microsoft Dynamics CRM Server install failed.

Action Microsoft.Crm.Setup.Server.MsiInstallServerAction failed. This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

I was very close to completing the CRM v4.0 installation on the server during a client implementation when I received a dialog box just as one displayed below. I've done plenty of implementations before but never came across any such error during installation. It made me think for a while, what different did I do during this installation and I noticed it was the recommended update. (The first step during a CRM installation)


After a while of thought and reading the error over and over again, I thought let me try this.

I simply cleared the IE cache, increased the cache size to almost 2 GB and re-installed CRM from the beginning, including the recommended update during the installation steps. The CRM installation glided to finish.

A happy ending!