Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Active Directory synching for SGN 5.50.8.13 error

I setup a scheduled task to synchronize SGN with our Active Directory daily. It was working fine until a couple days ago and now I'm getting this error:

-CBIERR_BAD_KEY on _DeleteEntry()

Anyone know what that means and how to fix it?

If I manually run the synchronize through the Management Center - it shows "The import failed. Additional Information: The import failed." and lists -CBIERR_BAD_KEY on _DeleteEntry() in the synchronization information area.

:8473


This thread was automatically locked due to age.
Parents
  • Finally got a response back from tech support yesterday after complaining to our sales guy about no response for a week and a half.  Simple fix, which is annoying and SHOULD have been made available on the website. I’’’’m gonna write documentation for Sophos and bill them accordingly….

    This issue has to do with our Sophos/Active Directory synchronization and how we need to synchronize the entire AD tree at some point during the night so it has a baseline. We currently have scheduled tasks setup to sync only certain OUs every 30 minutes because we are rolling this out to a few groups at a time who are not physically located in our office.

    The fix is to download SGNKeyTester (specific to the version of SGN you are using) – we use 5.50.8 so if you need that one, I can provide it otherwise Sophos will have to direct you to their FTP site to download it (good luck with that). So, you download the SGNKeyTester, run it on your Sophos server – login as the MSO account (not one that you elevated, it has to be the actual MSO account). I have a screen shot of the SGNKeyTester but it won't let me paste it here.

    Select “All Objects” radio button and click “Check only structure keys”, it will display any “Wrong Entries” in the bottom part of the screen, select one of the wrong entries and click “Additional Infos” (gotta love that misspelling!) and then “Repair Selected” (continue selecting the wrong entries listed and clicking “Repair Selected” until they are all fixed). Then click on “Check group and structure keys” and continue the “Additional Infos” and “Repair Selected” until those are all fixed.  Continue with the same process for “Check user and structure keys” and “Check computer and structure key”. Once you have done that, your problem is fixed and your AD syncs should work again.

    The key to prevent it from happening again is to setup a scheduled task to run at say 1:00AM to synchronize your entire AD structure. That way it has a baseline – at least that’’’’s what tech support said. Then you can sync just the OUs that are using Sophos as necessary during the day.

    :8919
Reply
  • Finally got a response back from tech support yesterday after complaining to our sales guy about no response for a week and a half.  Simple fix, which is annoying and SHOULD have been made available on the website. I’’’’m gonna write documentation for Sophos and bill them accordingly….

    This issue has to do with our Sophos/Active Directory synchronization and how we need to synchronize the entire AD tree at some point during the night so it has a baseline. We currently have scheduled tasks setup to sync only certain OUs every 30 minutes because we are rolling this out to a few groups at a time who are not physically located in our office.

    The fix is to download SGNKeyTester (specific to the version of SGN you are using) – we use 5.50.8 so if you need that one, I can provide it otherwise Sophos will have to direct you to their FTP site to download it (good luck with that). So, you download the SGNKeyTester, run it on your Sophos server – login as the MSO account (not one that you elevated, it has to be the actual MSO account). I have a screen shot of the SGNKeyTester but it won't let me paste it here.

    Select “All Objects” radio button and click “Check only structure keys”, it will display any “Wrong Entries” in the bottom part of the screen, select one of the wrong entries and click “Additional Infos” (gotta love that misspelling!) and then “Repair Selected” (continue selecting the wrong entries listed and clicking “Repair Selected” until they are all fixed). Then click on “Check group and structure keys” and continue the “Additional Infos” and “Repair Selected” until those are all fixed.  Continue with the same process for “Check user and structure keys” and “Check computer and structure key”. Once you have done that, your problem is fixed and your AD syncs should work again.

    The key to prevent it from happening again is to setup a scheduled task to run at say 1:00AM to synchronize your entire AD structure. That way it has a baseline – at least that’’’’s what tech support said. Then you can sync just the OUs that are using Sophos as necessary during the day.

    :8919
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?