Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 5 subscribers
  • Views 33648 views
  • Users 0 members are here
Options
Suggested
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

JuJo

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
  • 0

    I have had this error for a couple weeks now. It is not new but it has been a problem with safeguard for several versions now. Sophos does not like to admit it but there is a sync issue and they do not know how to fix it. The key tester tool does not always work. I have worked with Sophos on this and the solution they come up with is to delete the object with a problem from the sg database and re sync so it syncs up. This can be an issue as I can only trrack it down to a container not to the individual computer

    While this does usually fix the issue does not fix the probem that caused it in the first place. It also deletes all the keys for the ou out of safeguard so you have to make sure you back it up first in case you have a problem with a computer and have to challenge/response it.

    To me this is not a fix but as I have been using safeguard enterprise since 5.2 and this issue has been around almost as long I don't expect them to be able to fix it.  I don't think they really know what causes it but they always says it will be fixed in the next version. :smileymad:

    :9371
Reply
  • 0

    I have had this error for a couple weeks now. It is not new but it has been a problem with safeguard for several versions now. Sophos does not like to admit it but there is a sync issue and they do not know how to fix it. The key tester tool does not always work. I have worked with Sophos on this and the solution they come up with is to delete the object with a problem from the sg database and re sync so it syncs up. This can be an issue as I can only trrack it down to a container not to the individual computer

    While this does usually fix the issue does not fix the probem that caused it in the first place. It also deletes all the keys for the ou out of safeguard so you have to make sure you back it up first in case you have a problem with a computer and have to challenge/response it.

    To me this is not a fix but as I have been using safeguard enterprise since 5.2 and this issue has been around almost as long I don't expect them to be able to fix it.  I don't think they really know what causes it but they always says it will be fixed in the next version. :smileymad:

    :9371
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?