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 :
Service | Customer Service, Contact Center, Fie...
Unanswered

Upgrade of on-prem from 9.1.14.17 to 9.1.17.29 and Organizations Update issues

(1) ShareShare
ReportReport
Posted on by 4
I'll admit right from the start that I'm not overly familiar with Dynamics 365. I was brought in to the IT Systems team and one of the first responsibilities was to get patching status up to date.  One thing this meant was applying the 9.1.17.29 update to the on-prem Dyanmics 365 installations.  Starting on the Development Dynamics instance, the installation itself succeeded but apparently it was not able to update the databases for all of the Organizations.  Some of them are showing the correct version in the Dynamics 365 Deployment Manager, but others are still showing 9.1.14.17.  The account I am using to log directly in to the server and launch the Deployment Manager is a manager of ever group in AD that starts with /privuser/ as I read someplace that was a potential reason why the update fails, but that didn't change anything for my attempts. I've also confirmed that my account is in the sysadmin Server Role in the SQL instance that houses the databases for Dynamics.
2023-06-21 08:02:41.018|  Error| Update Organization with Id=5f1d2625-b9f9-e911-a2f9-0050568e83a9 failed with Exception:
Microsoft.Crm.CrmException: Encountered non-terminal failures during DBUpdates. Failing actions are: CustomControlsCore, BaseCustomControlsCore, SolutionHistoryAPIs, CRMSettingsAPIs, DataModelingExtensions, ApiMessagesExtension, LocalizationExtensionApps, DataServicesExtensions, AppModuleExtensions, ODatav4DataProvider, WebResourcePages, msdyn_PowerConnectors, EnvironmentVariables, MicrosoftFlowExtensionsAnchor, PowerPlatformConnectionReferencesAnchor, msdyn_ContextualHelpAnchor, msdynce_CustomerCareIntelligenceBots_Anchor, msdynce_ClientUtility, msdynce_AppCommonAnchor, msdynce_Activities, msdynce_ServiceLevelAgreementAnchor, msdynce_KnowledgeManagementAnchor, ActivitiesInfra, ServerSideSync, CDSApiExtensions, CustomAPIExtensions, AsyncServiceExtensionsApp, SampleEditorCustomControl, msdyn_CustomControlsExtended, CRMDesigners, msdyn_AISolutionAnchor, msdynce_LeadManagementAnchor, msdynce_ProductManagementAnchor, Scheduling_Anchor, msdynce_MarketingAnchor, msdynce_ServiceAnchor, msdynce_SalesAnchor, msdynce_MarketingServiceAnchor, msdynce_MarketingSalesAnchor, msdynce_SalesServiceAnchor, msdynce_CRMExtensionsAnchor, msdyn_SalesIntegrationsAddOns, msdynce_SalesInsightsAnchor, ActivityFeedsCore, AppforOutlook, SkypeForBusiness, msdynce_OfficeProductivityAnchor
   at Microsoft.Crm.Tools.Admin.OrganizationDBUpdateInstaller.ProcessFailedActions()
   at Microsoft.Crm.Tools.Admin.OrganizationDBUpdateInstaller.<>c__DisplayClass19_0.<Execute>b__0()
   at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable`1 additionalCustomProperties)
   at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
   at Microsoft.Crm.Tools.Admin.OrganizationDBUpdateInstaller.Execute()
 
Does anyone have any suggestions on what I can try next?
Thank you in advance
I have the same question (0)
  • PhilipK Profile Picture
    613 on at
    Hi Scott.

    The user(account) you you're logged in as and are running the upgrade via needs to be a "member" of the PrivUserGroup used for the installation/deployment along with it being a Deployment Administrator.
    Making it a "manager" of a security group(e.g. PrivUserGroup) in Active directory is just an attribute to the group and provide nothing in this scenario.
    The error "non-terminal failure" is something you will get if your user is not a member of this group, and iirc if you look earlier into the crmsnapin.log you would actually see that this validation of this requirement failing.

    So, open SQL SSMS and open the SQL\instance hosting your D365 deployment databases you want to upgrade, expand MSCRM_CONFIG and go to security - Users and check the PrivUserGroup_<GUID> (generated if not using pre-generated groups during initial install).
    Find the PrivUserGroup_<GUID> in Active Directory, open it and under Members tab, add the users your running as a member.

    A best practice would be to perform a restore of the databases prior to performing the upgrade attempt(that failed) and restoring them to the same SQL\Instance and then run an Import from Deployment Manager which will apply the latest update.

    Hope this helps.
    Philip 
  • Scott_D Profile Picture
    4 on at
    Thank you for the suggestionPhilipK. 
    I went in to Active Directory and the account I'm using to run the Deployment Manager is a member of a security group that is a member of all groups starting with "privUserGroup'. Just to be thorough I added my account directly to each group and tried again but I still get the same error.

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 > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 75 Super User 2025 Season 2

#2
Siv Sagar Profile Picture

Siv Sagar 52 Super User 2025 Season 2

#3
Daniyal Khaleel Profile Picture

Daniyal Khaleel 42 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans