Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Upgrading crm 3 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello

    I'm trying to upgrade a simple CRM 3 deployment to CRM 2011. As I understand it I have to first install CRM 4 on my CRM 3, and then import the result database into CRM 2011.

    So I've got a virtual machine, running Windows Server 2003 + SQL 2000 for the first step. I've installed CRM 3 and it looks like it works. I have also restored both the METADATA and the MSCRM databases on the server.

    The problem is that I'm unable to import the production database - I expected to be able to do it in the Deployment Manager (as it's done in CRM 4), but it lacks the Organizations element. When I try to go to Server Manager -> r-click on server -> Configure SQL Server and select the other DB it's not on the list. Similarly it was not available to use when I was installing CRM 3 in the first place - trying to select an existing database resulted in a message saying that none of the databases on the server is compatible.

    As far as I can tell both my production and test servers are running the same version of CRM - 3.0.5300.0, so I don't think it's a problem with rollups.

    I've red something about a redeployment tool, but apparently it's only used if I install to another domain, which is not the case here.

    Please let me know, what I'm doing wrong here, because I'm pretty much banging my head against a wall here.


    Thursday, June 6, 2013 12:50 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Because CRM3 isn't multi-tenanted, you are essentially changing the database for you CRM3 server.

    Follow the steps here :

    http://support.microsoft.com/kb/917948

    You will need to make sure that your two CRM3 servers are in the same domain.

    hth

    Scott Durow
    Blog: www.develop1.net    Follow Me
    Rockstar365  Profile
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Thursday, June 6, 2013 2:44 PM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the answer, the link was pretty helpful. It turned out that I if I restored the databases as MyBase_MSCRM than the organization had to be called MyBase too to be visible on the list.

    Unfortunately I got another problem - during the pre-installation check I get the following error:

    "One or more Microsoft CRM groups are not valid. The group scope must be Domain Local or Global. The group type must be Security."

    I checked the CRM-related groups (UserGroup, PrivUserGroup, SQLAccessGroup, ReportingGroup, PrivReportingGroup) in the AD and they are all Global or Domain Local and their type is Security (with the exception of the PrivReportingGroup, which I assume was not present in CRM 3?). What am I missing here?

    Monday, June 10, 2013 10:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    A little update here: after changing all related groups to Universal I now have this:

    The current user does not have required permissions (read/write) for the following Active Directory group: <GUID=262fce7f-5436-4d7e-b45c-86db015ace90>

    The guid does not fit any CRM group I can see in the AD.

    Monday, June 10, 2013 12:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Been a while since ive done this, but here are the basic steps:

    1: restore backups of your crm 3 dbs

    2. Run the redeployment wizard

    3. Install crm 3, pointing to reatored dbs

    4. Install crm 4, upgrading in place

    5. Back up crm 4 upgraded db

    6 restore to clean 2011 server

    7. Import in to deployment manager in 2011

    You have to do the redeployment wizard, otherwise your dbs will point to your crm 3 production environment. I have seen people trash their prod environment this way.

    Also, I would recommend considering whether or not you should do an upgrade or if you should do a migration. If someone is on crm 3 still, chances are there is a lot of cruft in their database, and the upgrade process contains a lot of risk traveling over two versions. The nice thing about a migration is it gives you an opportunity to leave out old data and entities that you dont want to bring to 2011.

    Wednesday, June 12, 2013 3:29 AM
    Moderator