Does this stack trace really comes from a failed sync procedure? By looking at it it seems that the problem comes from the profile maangement UI...