"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]

My pleasure.  Take care.

[Kirk_Landwehrm2]

We are experiencing the same issue and have been for a long time.  I'm curious did you configure something in your system that made the COMException error go away?  BTW, our first line support vendor told us that this error is harmless and not to worry about it.  thanks!

[AdamShaneHyland · Accepted solution]

To Robs point, after further research with a number of customers it has been determine that this issue is often caused by user groups having the SID History attribute populated (link).  As Rob mentioned, this is typically the case when performing a domain migration from an old domain to a new domain in order to reference the old domains user group SID. 

As for a resolution, while it is possible to remove the values once the migration has been completed (link), this is not always the case for domains which are currently in the migration phase.  Currently there is an SCR:# 240686 has been created (though not implemented as of OnBase 16) to further investigate if there are ways of differentiating the type of SID value so we don't attempt to resolve the SID History user group SIDs.