Troubleshooting Active Directory Services

This section provides known problems, limitations, and resolutions for troubleshooting the use of Microsoft Active Directory Domain Services (AD DS) and Active Directory Lightweight Directory Services (AD LDS) with ESI supported applications.

Symptom

Prevention, resolution, or workaround

The following error occurs when you add systems to ESI Applications that use AD LDS:

"ERROR: EMC.WinApps.Fx.Common.Directory.EsiDirectoryException: Protocol ='Ldap', Result = 'NotExist'. NoSuchAttribute 00000057: LdapErr: DSID-0C090D11, comment: Error in attribute conversion operation, data 0, v23f0 -System.DirectoryServices.Protocols.DirectoryOperationException: The requested attribute does not exist."

Confirm that you configured the AD LDS instance schema with msDS-App-Configuration and msDS-Settings. If not, extend the AD LDS instance to get these, and retry the operation.

The following error occurs when you add systems to ESI Applications that use AD DS:

"ERROR: EMC.WinApps.Fx.Common.Directory.EsiDirectoryException: Protocol ='Ldap', Result = 'NotExist'. NoSuchObject 0000208D: NameErr: DSID-03100213, problem 2001 (NO_OBJECT), data 0, best match of: 'DC=EMC,DC=Storage,DC=Integrator,DC=COM'

---> System.DirectoryServices.Protocols.DirectoryOperationException: The object does not exist."

  • For ESI, MMC, and ESI PowerShell Toolkit, confirm the container for the user exists.

  • For ESI Service, confirm a container exists for each ESI Service machine name.

  • For ESI Exchange HA Extension, confirm a container exists for each DAG.

Setting up Directory Services integration provides more details.