The error “Failed to Load Configuration Settings” on the Desktop and Laptop Option (DLO) Agent when using Active Directory Policy to add users through Automated User Assignment

Problem

While trying to add the users using the Active Directory Policy using Automated User Assignment, DLO  Agent throws an error "Failed to Load Configuration Settings"

Error Message

DLOClientu.log shows the following error:

============

07/24/12 15:46:47 dloclientu.exe 3160: T> adocommand.cpp( 603 ) executing ADO command: SELECT @@IDENTITY AS 'IDENTITY'
07/24/12 15:46:47 dloclientu.exe 3160: E> client.cpp( 3846 ) error loading database ADODBError-_com_error: foundationerror=80040200, comerr=80004005, nativeerror=4294967295, conn=, query=, msg=Unspecified error, src=Microsoft OLE DB Provider for SQL Server, desc=Failure 0x80004005 querying active directory container LDAP://OU=Users,OU=DDI Germany,DC=de,DC=DDI,DC=NET - Unspecified error
07/24/12 15:46:47 dloclientu.exe 3160: T> ../client/include/testoffline.h( 237 ) Shadow::OfflineFailure : 80004005 is not an offline code, returning false
07/24/12 15:46:47 dloclientu.exe 3160: E> Client.h( 1076 ) CClientApp::_HandleError() : displaying error message: Failed to load configuration settings.
07/24/12 15:46:47 dloclientu.exe 3160: E> Client.h( 1093 ) CClientApp::_HandleError() : m_pMainWnd is NOT NULL. using DontShowDlg...
07/24/12 15:47:27 dloclientu.exe 3160: E> Client.h( 1109 ) CClientApp::_HandleError() : error shown. returning.
07/24/12 15:47:27 dloclientu.exe 3160: E> client.cpp( 2340 )  CClinetApp::StartupThread : InitializeDB FAILED result=80004005 - THROWING res.
07/24/12 15:47:27 dloclientu.exe 3160: W> client.cpp( 2509 )  CClientApp::StartupThread : Caught param error exception, m_id=80004005, ClientApp::StartupThread.InitializeDB - Unspecified error
07/24/12 15:47:27 dloclientu.exe 3160: T> client.cpp( 2519 )  CClientApp::StartupThread : EXITING 0.
============

Note: See the related article section for article on how to enable debugging for DLO to get the DLOClientu.log

Solution

Workaround:

1. Manually add the users

2. Add users through Automated User Assignment using the policy "Assign using Domain and Group"