Trying to run the DLO (Desktop and Laptop Option) client for the first time only shows "Connecting to the media server", but does not actually connect the server, and no other errors are seen, unless debugging is enable

Article:TECH63674  |  Created: 2008-01-29  |  Updated: 2013-10-31  |  Article URL http://www.symantec.com/docs/TECH63674
Article Type
Technical Solution


Issue



Trying to run the DLO (Desktop and Laptop Option) client for the first time only shows "Connecting to the media server", but does not actually connect the server, and no other errors are seen, unless debugging is enable


Error



DLOClient.log debug shows "FAILED ASSERTION: shadow\client\ClientUI\client.cpp( line: 3683 ): false && "CClientApp::InitializeDB() res == DB_SEC_E_AUTH_FAILED"

By enabling debug from the registry at HKEY_CURRENT_USER\Software\Symantec\Components\debugstream\dloclientu.exe = FFFFFFFF and  trying to run the DLO Client again will result in the following error in C:\Documents and Settings\USERNAME\Local Settings\Application Data\Symantec\DLO\.settings\DLOClient.log :

09/29/08 10:23:16 dloclientu.exe 2872:  > client.cpp( 1547 )  -- LANGID == ENU --
09/29/08 10:23:16 dloclientu.exe 2872:  > client.cpp( 1773 )  BUILD INFO: DLO 330B14a 9/29/2008 10:23:16.865AM
09/29/08 10:23:18 dloclientu.exe 3148:  > adoutil.h( 70 ) Connection error: 80040E4D( 00004818 ) : Login failed for user '<DOMAIN NAME>\<User Name>'.
09/29/08 10:23:18 dloclientu.exe 3148:  > errorreport.cpp( 294 ) FAILED ASSERTION: shadow\client\ClientUI\client.cpp( line: 3683 ): false && "CClientApp::InitializeDB() res == DB_SEC_E_AUTH_FAILED"

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
 

Solution



Granting specific SQL rights to the "Domain Users" group can resolve the issue.  These rights can be granted by running the below commands from the media server's command line:
 
osql -E -S SERVERNAME\bkupexec -d BE_DLO -Q "sp_grantdbaccess 'DomainName\Domain Users'"
 
osql -E -S SERVERNAME\bkupexec -d BE_DLO -Q "sp_grantlogin 'DomainName\Domain Users'"
 
NOTE:  Before running the above commands one at a time, replace "SERVERNAME" with the actual media server name and "DomainName" with the actual domain name. Where bkupexec is SQL instance and BE_DLO is the name of DLO database which could be user defined.
  
Once the above command has been run, any user in the "Domain Users" group will have the specified permission granted.
 
NOTE:  Remember to turn of debugging by setting the value to "0" once the trouble-shooting has completed.
 



Legacy ID



309034


Article URL http://www.symantec.com/docs/TECH63674


Terms of use for this information are found in Legal Notices