The user services are not automatically started after a reboot of the server
search cancel

The user services are not automatically started after a reboot of the server

book

Article ID: 86613

calendar_today

Updated On: 06-11-2024

Products

CA Automic Dollar Universe

Issue/Introduction

After a reboot of the Windows server, some user services that use Domain User accounts appear as stopped, as a result the jobs submitted with that user account Abort.

The following errors appear on the universe.log when trying to launch some jobs with the submission account whose associated user service is stopped.

|ERROR|X|IO |pid=p.t| owls_io_user_sys_user | service user associated with submission account [username] not started
|ERROR|X|DQM|pid=p.t| o_CallServiceUser | CallNamedPipe / [2]/[\\.\pipe\COMPANY_univ_username]
|ERROR|X|DQM|pid=p.t| o_dqm_lanc_batch | error [0] [XXX] calling service user for entry [YYY] 

Environment

OS: Windows

Cause

System issue: the system is not able to start right after the reboot the services that use a domain account.

Resolution

In order to fix the issue, please do the following:

1. Go to the windows services menu ( services.msc).

2. Go to the properties of the user service that could not be started after the reboot.

3. Modify the Startup Type: Automatic by " Automatic (Delayed Start)"

4. Then restart the services to take into account the modification.