Jean-Sébastien DUCHENE Blog's

Actualité, Tips, Articles sur l'ensemble des Technologies Microsoft (Microsoft Intune, ConfigMgr, Microsoft Defender, Microsoft Purview, Microsoft Azure, Windows...)

L’équipe DPM vient de publier un article dans la base de connaissances concernant un problème survenant lors de la mise à jour de System Center 2012 Data Protection Manager SP1 vers 2012 R2. La mise à jour échoue en renvoyant le message suivant :

Error : DPM Setup failed to add a user to the local group. Review the error details, take the appropriate action, and then run DPM Setup again.
ID: 4323. Details: A member could not be added to or removed from the local group because the member does not exist

Dans le fichier Setup.log, vous pouvez observer :

[10/23/2013 11:07:42 AM] Information : Start configuration.
[10/23/2013 11:07:42 AM] Information : Starting Service:MSSQL$MSDPM2012 on machine:DPMServerName flag restart:False
[10/23/2013 11:07:42 AM] Information : Starting Service:SQLAgent$MSDPM2012 on machine:DPMServerName flag restart:False
[10/23/2013 11:07:42 AM] Information : Starting Service:ReportServer$MSDPM2012 on machine:DPMServerName flag restart:False
[10/23/2013 11:07:42 AM] Information : Create a registry containing sql agent account information
[10/23/2013 11:07:42 AM] Information : Querying WMI Namespace: \\DPMServerName\root\cimv2 for query: SELECT * FROM Win32_Service WHERE Name='SQLAgent$MSDPM2012'
[10/23/2013 11:07:42 AM] Information : Sql Agent account name = domain-old\DPMServerName$
[10/23/2013 11:07:42 AM] Information : Create a registry containing the trigger job path information
[10/23/2013 11:07:42 AM] Data : TriggerJobPath = D:\Microsoft System Center 2012\DPM\DPM\bin\
[10/23/2013 11:07:42 AM] Information : Add user: domain-old\DPMServerName$ to local group: Distributed COM Users on server: DPMServerName
[10/23/2013 11:07:42 AM] * Exception :  => DPM Setup failed to add a user to the local group.Review the error details, take the appropriate action, and then run DPM Setup again.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.NativeConfigHelper.AddAccountToLocalGroup(String accountName, String localGroupName, String machineName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.RemoteDatabaseConfiguration.AddSqlAgentAccountToLocalGroups(String sqlAgentAccountName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.MachineSpecificConfiguration(Boolean existingDB, Boolean upgrading, Boolean isRemoteDb, String sqlServerMachineName, String sqlInstanceName, Boolean isRemoteReporting, String reportingMachineName, String reportingInstanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.Configure(Boolean existingDB, Boolean upgrading, String databaseLocation, String sqlServerMachineName, String sqlInstanceName, String reportingMachineName, String reportingInstanceName, Boolean oemSetup)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.ConfigurePostMsiUpgrade()
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.UpgradeDpm()
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: AddUserToLocalGroupFailed; 1387; WindowsAPI
[10/23/2013 11:07:44 AM] *** Error : DPM Setup failed to add a user to the local group. Review the error details, take the appropriate action, and then run DPM Setup again.
ID: 4323. Details: A member could not be added to or removed from the local group because the member does not exist
[10/23/2013 11:07:44 AM] Information : The DPM upgrade failed.
For more details, click the Error tab.
 To troubleshoot this issue, see http://go.microsoft.com/fwlink/?LinkID=164487.

Ce problème survient si un environment a un espace de nom disjoint (Nom NetBIOS et DNS différents).

Pour résoudre le problème, suivez la KB2912500 - System Center 2012 R2 Data Protection Manager upgrade fails with ID: 4323 and "A member could not be added"

Facebook Like