locked
Upgrade CRM 4 to CRM 2011 with dashes in the db-name RRS feed

  • Question

  • I'm currently upgrading a customer's CRM 4.0 to CRM 2011 and have some strange problems. Database names that have dashes, "-", in them doesn't seem to upgrade. I have two different problems with this. One is a migration upgrade that clearly states that dashes, and several other characters are unsupported in the database name. This is somewhat strange since the database from CRM 4.0 does work with the dash in the name so that must have been supported in CRM 4.0, I don't remember anything about dashes not been allowed, but my memory can be murky here.

    The other problem is an in-place upgrade of the test environment where the upgrade simply halted with the error that I didn't have enough permissions on database XX_YY_MSCRM or that the database didn't exist. This is even stranger since I am db owner and sysadmin on the sql server AND the fact that the database is named XX-YY_MSCRM. How come the CRM 2011 upgrade changes the dash to an underscore, how can I upgrade this environment, I really want to do the in-place upgrade since I will do an in-place upgrade of the production environment, this however doesn't have a database name with any illegal characters. Is the sollution for my problem to move the CRM to a "new" database which really is the current database renamed, if that's even possible.

    Thanks.


    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se

    Wednesday, June 20, 2012 2:52 PM

Answers

  • What about:

    1. Disable offending Organisation
    2. Delete offending Organisation
    3. Rename DB
    4. Import offending Organisation

    Then you should be able to continue with your in-place upgrade


    --pogo (pat) @ pogo69.wordpress.com

    Monday, June 25, 2012 10:53 PM

All replies

  • Rename the databases prior to Upgrade/Import.  It is of no consequence to CRM what you name the DB, so you can change it as you wish.

    --pogo (pat) @ pogo69.wordpress.com

    Thursday, June 21, 2012 12:03 AM
  • Thanks Pogo. One question though. Wouldn't renaming the db make CRM confused and unable to use the org-db that it is installed for?

    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se

    Thursday, June 21, 2012 8:11 AM
  • Yes, you're quite right.  I missed in your second paragraph that you are performing an in-place upgrade.  The CRM Configuration DB MSCRM_CONFIG will contain references to the specific CRM Org DB Name, so renaming is insufficient.

    My advice (what I would do), is:

    1. Backup the Organisation DB
    2. Un-install CRM 4.0
    3. Install CRM 2011
    4. Restore Organisation DB to a "non-dashed" DB Name
    5. Import

    In other words, ditch the in-place upgrade.


    --pogo (pat) @ pogo69.wordpress.com

    Friday, June 22, 2012 12:44 AM
  • If you have more than one org and not all have the dash-name problem, you could just back up the problem ones, drop them from deployment manager in CRM 4 (disable then delete, this does NOT remove the databases), do an in place upgrade of the ones that are left, then rename and import the problem ones.

    But to be honest, a 'migration' install of everything as outlined by pogo69 might simply be easier in the end (ie import each organisation from its [renamed] database). You will have to rename / remove the MSCRM_CONFIG database from the SQL server so it does not confuse the CRM2011 installation.


    Hope this helps. Adam Vero, MCT

    Friday, June 22, 2012 8:41 AM
  • That is exactly how I would do it. Unfortunately that's not an option in this case since I have to do the in-place upgrade.

    Thank you for the input even if I can't use the advice at this time.


    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se

    Monday, June 25, 2012 7:03 AM
  • What about:

    1. Disable offending Organisation
    2. Delete offending Organisation
    3. Rename DB
    4. Import offending Organisation

    Then you should be able to continue with your in-place upgrade


    --pogo (pat) @ pogo69.wordpress.com

    Monday, June 25, 2012 10:53 PM
  • That's the solution I had to use in the end and wanted to avoid since the database is large-ish. The re-import took 4-6h which is time I wanted to use for the upgrade.

    Thanks for all the imput and ideas, I really appreciate it.


    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se

    Tuesday, June 26, 2012 10:41 AM