The Desktop and Laptop Option (DLO) Administration service fails to start and displays the error "service did not respond to the start or stop control command within the specific timeout period."

book

Article ID: 100011159

calendar_today

Updated On:

Description

Error Message

Event Viewer Application log on DLO server shows following error events:

Log Name:      Application
Source:        DLOAdminSvcu
Event ID:      50030
Level:         Error

Description:
The description for Event ID 50030 from source DLOAdminSvcu cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

735
shadow\Server\consolesvc\consolesvc.cpp
0x80004005: ADODBError-_com_error: foundationerror=80004005, comerr=80004005, nativeerror=916, conn=Provider=SQLOLEDB;Data Source=Servername\DEDUPE;Initial Catalog=master;Integrated Security=SSPI;Connect Timeout=120, query=EXEC sp_detach_db N'dedupedb', msg=Unspecified error, src=Microsoft OLE DB Provider for SQL Server, desc=The server principal "Domain\User" is not able to access the database "dedupedb" under the current security context.


 &

Log Name:      Application
Source:        DLOAdminSvcu
Event ID:      50030

Description:
The description for Event ID 50030 from source DLOAdminSvcu cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

502
shadow\Server\consolesvc\consolesvc.cpp
0x80040E09: ADODBError-_com_error: foundationerror=80040e09, comerr=80040e09, nativeerror=229, conn=Provider=SQLOLEDB;Data Source=Servername\DLO;Initial Catalog=master;Integrated Security=SSPI;Connect Timeout=120, query=     if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_create_share]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_create_share'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_create_dir]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_create_dir'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_get_domain_groups]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_get_domain_groups'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_get_report_list]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_get_report_list'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_get_report_params]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_get_report_params'     if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_start_report]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_start_report'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_set_report_param]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_set_report_param'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_run_report]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_run_report'    if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_browse_backup]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_browse_backup'     if exists (select * from master.dbo.sysobjects where id = object_id(N'[master].[dbo].[sp_shadow_post_notify]'))        exec master.dbo.sp_dropextendedproc 'sp_shadow_post_notify'    if exists (select * from master.dbo.sysobjects w쳌쳌쳌쳌쳌쳌쳌쳌쳌쳌쳌쳌쳌ɚ

Cause

DLO Service Account does not have 'Public' and 'SysAdmin' rights on SQL instance of DLO.

Resolution

1. Launch SQL Management Studio or SQL Management Studio Express.

2. Connect to the DLO instance.

3. Expand Security, Logins.

4. If DLO Service account is already added then make sure it has Public and SysAdmin rights.

5. If it's not added, right click on Logins, click New Login.

6. Add the account and assign it Public and SysAdmin rights.

 


 

Issue/Introduction

The Desktop and Laptop Option (DLO) Administration service fails to start and gives error "service did not respond to the start or stop control command within the specific timeout period."