Novell Home

My Favorites

Close

Please to see your favorites.

User sync failed in Mobility

This document (7012824) is provided subject to the disclaimer at the end of this document.

Environment

Novell Data Synchronizer Mobility Pack

Situation

WebAdmin | Mobility Connector Settings | User with Sync State Failed
Unable to add user to Mobility, other users add fine
Adding user to DataSync Sync State Failed
WebAdmin | Users | reports LDAP DN with a '\' character, such as 'cn=user\ ,o=novell'
Application User Name also displays incorrectly

Resolution

Although there are other reasons for a user to Fail during sync, the below is a resolution to one found situation preventing sync for a specific user with the Mobility server. Otherwise, see the Resolution steps provided in TID 7012677 for a common fix.

  1. Remove user from the Mobility server (see documentation for Managing Users)
  2. Completely remove all references of the user from Mobility databases (see TID 7008852)
  3. The user object has a space at the end of the name. Rename the user-object - eliminate the trailing space.
    From ConsoleOne, right-click the user-object and select Rename.
  4. Synchronize the user-object.
    From ConsoleOne, right-click the user-object | GroupWise Utilities | Synchronize
  5. Add user to the Mobility server (see documentation for Managing Users)

Cause

LDAP DN of user had a space at the end showing up in datasync as 'cn=userid\ ,ou=users,o=organization'. Rename user and remove the space, then resync with Mobility corrects this issue.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7012824
  • Creation Date:10-JUL-13
  • Modified Date:10-DEC-13
    • NovellData Synchronizer
      GroupWise

Did this document solve your problem? Provide Feedback