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"?