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

Sophos AD Sync error

Just recently I've encountered the following error:

Error making a request over LDAP. Please review the connection settings you specified. The LDAP server returned the following error: 0000208D: NameErr: DSID-03100238, problem 2001 (NO_OBJECT), data 0, best match of: 

Followed by a OU path that that really shouldn't be a issue, there has been no changes in the sync configuration. This is on-premise with Sophos AD Sync Utility v3.3.40.0.
Before the issue, the sync worked as expected. Has anyone been met with the same error?

Any help is greatly appreciated.



This thread was automatically locked due to age.
Parents
  • Hello  

    Please check if the OU referenced still exists in your AD. You will need to review any filters you have set up under the AD Filters tab and Define Filters button. Remove any filters referencing objects removed from your Active Directory. More information on the AD sync and possible issues here. Here is a related Community post that may also help.

  • The OU that the error indicated, has now been changed to nested OUs that does have users within.

    So, the OUs with Region1-4 is now defined instead of the department OU. However, the previous error still persists. Even though it's not even defined.
    Department OU (with error that was removed from define)
            Region1 OU
            Region2 OU
            Region3 OU
            Region4 OU

    Only thing I can imagine is that there something cached and the new define rules aren't refreshed or updated. Any solutions?

  • Hello  

    You can try re-doing the AD Sync filter settings again to see if that should resolve the error. 

    If the issue persists, we will need to review the logs and also a screenshot of the tab in the AD Sync tool that shows the filters.

    You may also raise a support ticket with logs and let us know the ticket number so we can post any updates here as well.

  • I removed the previous user define filters and re-entered it. And still the program gets an error about a OU that doesn't even exist, it's not in the user define filters. The OU exists in the AD but it looks like this:

    AD

    Department 1
    Department 2
    Department 3
    Department 4
       Users <---- program gets error because of this one, and it isn't even added in user define filter.
            Region 1
                    Users <- added to user define filter
            Region 2
                   
    Users <- added to user define filter
           
    Region 3
                    Users <- added to user define filter
           
    Region 4
                    Users <- added to user define filter
           
    Test user (within department 4 OU)

    Department 5

    I need a fix for this ASAP.

Reply
  • I removed the previous user define filters and re-entered it. And still the program gets an error about a OU that doesn't even exist, it's not in the user define filters. The OU exists in the AD but it looks like this:

    AD

    Department 1
    Department 2
    Department 3
    Department 4
       Users <---- program gets error because of this one, and it isn't even added in user define filter.
            Region 1
                    Users <- added to user define filter
            Region 2
                   
    Users <- added to user define filter
           
    Region 3
                    Users <- added to user define filter
           
    Region 4
                    Users <- added to user define filter
           
    Test user (within department 4 OU)

    Department 5

    I need a fix for this ASAP.

Children