?
Solved

Troubles migrating CRM v3.0 DBs to staging environment

Posted on 2006-06-29
6
Medium Priority
?
576 Views
Last Modified: 2013-11-24
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"?

/denny
0
Comment
Question by:dennybvmc
  • 2
  • 2
5 Comments
 
LVL 16

Expert Comment

by:Redwulf__53
ID: 17016375
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.
0
 

Author Comment

by:dennybvmc
ID: 17020362
Redwulf:

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.

0
 

Author Comment

by:dennybvmc
ID: 17034299
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.
0
 
LVL 16

Expert Comment

by:Redwulf__53
ID: 17601385
agreed.
0
 

Accepted Solution

by:
CetusMOD earned 0 total points
ID: 17633453
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Salesforce.com is a cloud-based customer relationship management (CRM) system. In this article, you will learn how to add and map custom lead and contact fields to your Salesforce instance.
Let’s face it: one of the reasons your organization chose a SaaS solution (whether Microsoft Dynamics 365, Netsuite or SAP) is that it is subscription-based. The upkeep is done. Or so you think.
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question