• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 581
  • Last Modified:

Troubles migrating CRM v3.0 DBs to staging environment

Staging environment suffered major AD failure.  I am rebuilding it.

This is not SBS environment. We were a CRM 1.2 shop, upgraded to v3.0 two weeks ago.  Databases reside on a separate server.

Backed up databases and restored to staging SQL server and DB import was successful.  Did not name SQL instance (default).  Production and Staging server names are different hostnames.

When attempting to install CRM v3.0 PRO; I point it to the staging SQL box and when it attempts to attach to the existing DB's, I get the following error:

"The existing databases are not compatible with this installation of Microsoft CRM"

And setup silently exits at this point.  I would post the setup log, but really, it's right at the end of the log it simply refuses to think the DBs are compatible.  I've done some initial research and found what could be a multitude of issues causing this:

Different named SQL instance.  Anyone come across this before?
Restored DB's have different names (preface DB's with STGDB_Name_Date).  Anyone come across this before?

I read some other theories but they all applied to SBS installations and are not applicable to my environment.  

So my question is, should I bother with trying to recreate the exact environment? (Sans machine name) Or, do any of you have any experience with going from v1.2 -> v3.0 and STILL have the primary issue of "The existing databases are not compatible with this installation of Microsoft CRM"?

  • 2
  • 2
1 Solution
Did you restore JUST the _mscrm and _metabase db's and not the model db? If so, the security is out of whack. In that case, you'll need to run the Redeployment Wizard (located on the crm server CD) which will reconfigure all security related mappings.
dennybvmcAuthor Commented:

Correct, I only restored the _mscrm and _metabase DB's from the production server to the staging server.

While waiting for input from the community here, I decided to back out on the install and do a "Fresh Install" into brand new databases in staging, but when I imported the customizations from our production CRM v3.0 we got an error message stating the customizations were also incompatible with this version of CRM v3.0.

Our next step is to uninstall v3.0, install v1.2, then upgrade the beast in staging and see where we get.

dennybvmcAuthor Commented:
Mark this as resolved.

Resolution was not to use my script to import the database; simply use the 'restore' in SQL feature to allow MS CRM installer to continue beyond DB version check.

Thanks all.
PAQed with points refunded (500)

Community Support Moderator
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now