Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 3 to CRM 4 Upgrade Error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    HI

    I have been trying to upgrade our CRM 3 Staging enviroment for the last week with various issues when installing CRM 4,everytime i try to upgrade now it gives an error,i first Redeploy our CRM 3 and then try to upgrade,about 30 minutes into the instal i get this error

    Action Microsoft.Crm.Setup.Server.AddLicenseAction failed.

    Cannot upgrade to specified license type.

    I used CRM 3 pro msdn key to install crm 3 and now using the crm 4 pro key
    The only license in the database is the crm 3 key.

    Any suggestions as i now have rollback and do it again

    Kind Regards

    Friday, May 8, 2009 9:50 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Found the problem on this. On the SQL cluster there was another mscrm_config database from another crm 4 Install that was never removed.
    After this the sintall gave another error with the indexing on the kbarticle tabel that was the issue
    Friday, June 12, 2009 8:29 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Could be because the license key is in a table in the database.

    Perhaps removing it will help.
    Friday, May 29, 2009 3:04 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi what I normally do is:

    in  crm 3.0 thekey is in the lisence table on the db.
    use that on the re-deployment tool for crm 3.0.
    it will come up with a warning statig that the key already exists.
    do the redeploy.
    Try the entterprise key for crm 4.0
    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Friday, May 29, 2009 3:18 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Found the problem on this. On the SQL cluster there was another mscrm_config database from another crm 4 Install that was never removed.
    After this the sintall gave another error with the indexing on the kbarticle tabel that was the issue
    Friday, June 12, 2009 8:29 AM