"No such object" error on webserver

[Joe_Pineda]

Windows 2003, IIS 6, Hyland Server Components 8.2.2139.

Does anybody know how to get rid of this error below? It's being reported on our web server, but the source in the Windows (OnBase) event log is the Hyland Application Server. We are troubleshooting excessive paging by the ww3 service on the app server, and I'm trying to determine if there is any relation at all between these 2 issues on two different servers.

This error below (from what I have researched so far) appears to be tied to getting (or not getting) an object reference in Active Directory services.

Exception Type: System.DirectoryServices.DirectoryServicesCOMException ExtendedError: 8333 ExtendedErrorMessage: 0000208D: NameErr: DSID-031001E5, problem 2001 (NO_OBJECT), data 0, best match of:  ''

ErrorCode: -2147016656 Message: There is no such object on the server.

Data: System.Collections.ListDictionaryInternal TargetSite: Void Bind(Boolean) HelpLink: NULL Source: System.DirectoryServices

StackTrace Information *********************************************    at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)    at System.DirectoryServices.DirectoryEntry.Bind()    at System.DirectoryServices.DirectoryEntry.get_AdsObject()    at System.DirectoryServices.PropertyCollection.Contains(String propertyName)    at Hyland.Core.ADSILogin.getAdsiGroupNamesWithDeepDiscovery(String userName)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[AdamShaneHyland]

Hi Jose,

Hope that you are doing well.

This issue is typically related to authentication when using Windows NT with Nested Group discovery method.  Essentially, OnBase is attempting to look for a user in AD which doesn't get returned.  This can sometimes be caused by the account running the OnBase Application Server (ie the Application Pool Identity account or the Impersonation account) not having the necessary permission to query AD.  You can enable the LDAP/NT mailslot in the Application Server web.config which will allow more logging in the Diagnostics Console. 

If you need further assistance, I would contact your first line of support.

Take care.

[Joe_Pineda]

Thanks Adam

[David_Juhlin]

Installing OnBase 16 on Server 2012 R2 and saw this same error. Based on the additional logging in the Diagnostics Console (thanks Adam!), it turns out that not all the found groups have sAMAccountName entries, and this was (apparently) causing the error. OnBase wants to match the sAMAccountName with the OnBase group name, and if it cannot find the name in AD, it throws this (harmless) message.

[Rob_Keberdle]

Another possibility is that you have performed one or more domain migrations and OnBase cannot iterate through the SID History of your accounts and group objects. We had to remove the SID History of basically all of our AD objects before we totally got rid of these messages.