Using Field Mapping in AD Sync Profile will cause new users to not be synced properly. Existing users will be updated properly. UI will show a successful sync but errors in ProcessManager logs indicate a problem.
When field mappings are cleared out sync will be successful and new users will be synced.
The error below will be displayed in the ProcessManager log files:
[ADSyncProcess] Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
LogicBase.Ensemble.ADSyncProcess.ADUserSyncMonitoring.GetNewInstanceForADUsers(ActiveDirectoryServer server, ADMember aduser) in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\ADSync\ADUserSyncMonitoring.cs:line 790
LogicBase.Ensemble.ADSyncProcess.ADUserSyncMonitoring.SyncADUsers(ActiveDirectoryServer server, ADMember allusers) in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\ADSync\ADUserSyncMonitoring.cs:line 412
This issue can be worked around by nulling the ADSyncFieldMapping column in the ActiveDirectoryServer table.
This issue can be resolved by contacting Technical Support and obtaining a Rollup build that resolves this issue.
ServiceDesk 7.5 SP1
Imported Document ID: TECH215908
Subscribing will provide email updates when this Article is updated. Login is required.