Error: "COMException (0x8007054B): The specified domain either does not exist or could not be con (75807)

The following error can be observed in the ArchiveManager Event Log when trying to log into the Retention Policy Editor

Source: Retention Server

BusinessLayer.Login: [4187136875-1241409107-0-0x0] Exception has been caught

Exception Source: System.DirectoryServices
Exception Type: System.Runtime.InteropServices.COMException
Exception Message: The specified domain either does not exist or could not be contacted.

Exception Target Site: Bind
Date and Time: 30/06/2011 12:23:22
Machine Name: AMSERVER
IP Address: 10.90.0.4
Current User: W2K3-QAM-S\qam_service
CLR Version: 2.0.50727.3603
Platform (version): Win32NT (5.2.3790.131072)
Application Domain: /LM/W3SVC/2/Root/RetentionInstance-1-129539065790876764
Assembly Codebase: file:///C:/Program Files/Quest Software/ArchiveManager/RetentionWebService/bin/AfterMail Common.DLL
Assembly Fullname: AfterMail Common, Version=4.4.2.165, Culture=neutral, PublicKeyToken=null
Assembly Version: 4.4.2.165
COMException HRESULT: -2147023541

---- Stack Trace ----
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_NativeObject()
at AfterMail.BusinessLayer.Login.LDAPAuthenticate(String user, String password, LoginDomain loginDomain)

Additionally the following will be logged in the C:\LM\W3SVC log file:

2011-06-30 12:23:18,228 [5] INFO AfterMail.Log.DataModelServer.Authentication - Performing an Database login as DOMAIN\USERNAME
2011-06-30 12:23:19,369 [5] DEBUG AfterMail.Log.BusinessLayer.Login - BL.Login.Authenticate Domain: DOMAIN Context: UserName USERNAME
2011-06-30 12:23:22,541 [5] ERROR AfterMail.Log.BusinessLayer.Login - [4187136875-1241409107-0-0x0] Exception has been caught

System.Runtime.InteropSe

The Application Pool that the RetentionInstance uses in the Archive Manager website has a local account set as the Application Pool Identity.
Local accounts will not be able to query AD.

For Windows 2003

1. Open an IIS Manager MMC
2. Navigate to the RetentionInstance node under the ArchiveManager website
3. Right click the "RetentionInstance" node and click Properties.
4. Click on the "Virtual Directory" tab.
5. Note the name of the Application pool that is being used and click Cancel.
6. Expand Application Pools in the left hand pane of the IIS Manager MMC
7. Right click the Application pool noted in step 5 and click Properties.
8. Click the Identity tab.
9. Enter an AD domain username and password that the application pool will run with and Click OK. For a default installation of Archive Manager this is normally named DOMAIN\ArchiveMgr_Service
10. Restart IIS by clicking Start | Run | IISRESET

For Windows 2008

1. Open an IIS Manager MMC
2. Navigate to the RetentionInstance node under the ArchiveManager website
3. Right click the "RetentionInstance" node and click Manage Application | Advanced Settings.
4. Note the name of the Application pool that is being used and click Cancel.
5. Click Application Pools in the left hand pane of the IIS Manager MMC
6. Right click the Application pool noted in step 4 and click Advanced Settings...
7. At the top of the "Process Model" box there will be a row called "Identity", click the ellipsis (...) button.
8. Enter an AD domain username and password that the application pool will run with and Click OK twice. For a default installation of Archive Manager this is normally named DOMAIN\ArchiveMgr_Service
9. Restart IIS by clicking Start | Run | IISRESET

The account that the application is set to use must be a member of the following local security groups on the Archive manager server:
Administrators
IIS_WPG

The account must also be granted the following right in the Local Security Policy:

"Log on as a batch job"