KB: System Center 2012 R2 Data Protection Manager upgrade fails and generates ID: 4323: "A member could not be added" - System Center: Data Protection Manager Engineering Team Blog - Site Home - TechNet Blogs

KB: System Center 2012 R2 Data Protection Manager upgrade fails and generates ID: 4323: "A member could not be added"

KB: System Center 2012 R2 Data Protection Manager upgrade fails and generates ID: 4323: "A member could not be added"

  • Comments 2
  • Likes

KBHere’s some information on a new KB article we just published. The issue here is that when you try to upgrade Microsoft System Center 2012 Data Protection Manager (DPM) 2012 Service Pack 1 (SP1) to System Center 2012 R2 Data Protection Manager (DPM) 2012 R2, the upgrade may fail with the following error message:

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

Additionally, you see entries that resemble the following in the Setup.log file:

[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.

This issue can occur if the environment has a disjointed namespace (i.e. the domain has different NetBIOS and DNS names).

For additional details and a work around, please see the following:

KB2930276 - System Center 2012 R2 Data Protection Manager upgrade fails and generates ID: 4323: "A member could not be added" (http://support.microsoft.com/kb/2930276)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Wouldn't QA pick that type of thing up?