I have confirmed that, nothing is changes on the AD side, its still the same as last week when I did the AD sync first time to populate the user database. However, one thing that I can tell is that our hot backup server is in wescost and when I was trying to run the directory back tool, it was failing, then one of our operations guy is still trying to copy to the hotback up using secure FTP.
I had this (or similar) error when I renamed a User group in the MEE database. I had to rename the User group back in the DB and the error went away in the Connector.
To me it almost seemed as if once you use the Connector to put a user in a User Group it is tied somewhere internally by the User Group name. Change the name of the User Group (rename it) and the Connector has issues.
Yes it was the issue, I rename the group in the DB and then when I ran the AD connector I was getting the error message. But you don't have to rename the group back to what it was, I just simple went to the AD connector Group Mapping settings and update the the option "Create a new group with configuration based on" by dropping down the menu and selecting the renamed group. So this means that you are rename the group in the database but you need to update the group mapping settings in the connector to get it working again.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.