UserRightsAssignment : SendConfigurationApply function did not succeed.

[goforebroke]

The following is error is thrown adding when adding a domain group to Perform Volume Maintenance user rights assignment.

The SendConfigurationApply function did not succeed.
+ CategoryInfo : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 1
+ PSComputerName : XXXXXXXXX

The local configuration manager on the target node shows the following error...

[[UserRightsAssignment]PerformVolumeMaintenanceTasks] Error processing S-1-5-80-2242208429-2985175502-2274617606-174877781-2598220866. Error message: Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated.""},
{"time": "2017-12-20T08:35:46.983-7:00", "type": "verbose", "message": "[XXXXXXXXX]:

The domain group is added, so I am not sure why the error is being thrown.

Here is the code DSC code...

        UserRightsAssignment ($Node.NodeName + "PerformVolumeMaintenanceTasks")
        {
            Policy = "Perform_volume_maintenance_tasks"
            Identity = "DOMAIN\DOMAINGROUP"
            DependsOn = ("[SqlSetup]" + $Node.NodeName)
        }

Any help appreciated.

[hackjammer]

This is due to lack of error handling in ConvertTo-NTAccount - see e.g. #74

Depending on the exact cause (missing translation or orphaned sid) you may be able to temporarily get around this by removing any orphaned sids from user rights assignment

[johlju]

This is being discuessed in issue #78 and proposed fix in PR #74.

[dd8]

We have also experienced this issue - Translate was throwing an exception due to an orphaned SID in some Local Policies/User Rights Assignment settings. Took several weeks to diagnose be because none of the logging messages showed the problem SID

If any of the user rights contain an unresolved SID with the format of "*S-1-…" then all of UserRightsAssignment changes fail

[meizenga]

We have also experienced this issue - Translate was throwing an exception due to an orphaned SID in some Local Policies/User Rights Assignment settings. Took several weeks to diagnose be because none of the logging messages showed the problem SID

If any of the user rights contain an unresolved SID with the format of "*S-1-…" then all of UserRightsAssignment changes fail

We also had this issue. @dd8 Your solution really helped!