web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Cannot upgrade DB from 2016 versions due to invalid SYSTEM account

(1) ShareShare
ReportReport
Posted on by 222

I'm upgrading my production environment from CRM 2016 0.1 to 1.0 to arrive to D365.
I cannot upgrade the data DB. The error is:

Microsoft.Crm.CrmException: The user Id(s) [GUID Number] is invalid. 

The GUID Number refers to the hidden CRM System account. 

We used this SYSTEM account to move the data from a disabled user to an existent user.

Where could I look for some misconfigurations in my DB?

Graziano.

*This post is locked for comments

I have the same question (0)
  • Andreas Cieslik Profile Picture
    9,267 on at

    You should never touch or remap the SYSTEM or INTEGRATION user of Dynamics CRM as they are built-in.

    So during the update process when you do the user mapping you should not remap those two users.

    I would recommend to leave the mapping as it is and do the reassignment of user data within the CRM UI as described here:

    crmbusiness.wordpress.com/.../crm-2016-how-to-reassign-all-records-of-a-user

  • Graziano Tartari Profile Picture
    222 on at

    No Andreas... you didn't understand my issue.

    I never tried to remap SYSTEM or INTEGRATION users. I followed your suggestion in past to reassign the records from a user to another and now I have noticed SYSTEM is in "modified by" field og many records. But I cannot think this is the issue. I have to know other type of investigation to understand because the account seems invalid to the upgrade.

    A year ago I installed 2016 version and after a while I upgraded to 0.1. Now I'm trying to upgrade from 0.1 to 1.0 of CRM 2016, minor upgrade to arrive to D365 but I cannot upgrade the DB.

  • Verified answer
    Graziano Tartari Profile Picture
    222 on at

    I think I have discovered the solution. In my domain I disable administrator user for security policy and I yet had report server running as administrator. I change the report accounting with a new administrator and restore the key. After that my upgrade went like a charm. 

    I think the message refers not directly to the hidden CRM system account but to a real administrative account that lost some persmissions. Then I had to search the issue not in SYSTEM account but in another real accont outside the CRM.

    I think this could help you.

    Regards,

    Graziano.

  • Suggested answer
    Gustaf Westerlund Profile Picture
    on at

    I found that desipte using a user that I thought had all the right, that was suffiecient to install the 0.1 update but not upgrade the org. However, if I switched to the user that was used to install CRM, that worked. Not sure exactly what rights the first user was missing, but obviously something. So, try to remember which user and go back to using that.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans