How to forcefully terminate a hung service? Error 1053 refers to system services.
Found it))) Here are all the logs about failure and successful launches
Date, Source, Severity, Message
01/13/2019 09:03:30,Information, SQLServerAgent interrupted (normal)
01/13/2019 09:03:30,Error, Local node server is not running
01/13/2019 09:03:29,Error, Login to server "(local)" failed (SaveAllSchedules)
01/13/2019 09:03:29,Error, SQLServer error: 773
01/13/2019 09:03:29,Error, SQLServer error: 21
01/13/2019 09:03:28,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
01/13/2019 00:26:27,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
01/13/2019 00:26:27,Warning, Failed to start mail session.
01/13/2019 00:26:27,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
01/13/2019 00:26:27,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
01/13/2019 00:26:25,Information, There are 7 subsystems in the subsystem cache
01/13/2019 00:26:25,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
01/13/2019 00:26:25,Information, 16 processors and 32430 MB of RAM detected
01/13/2019 00:26:25,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
01/13/2019 00:26:25,Information, ODBC driver for SQL Server version 14.00.2002
01/13/2019 00:26:25,Information, SQL Server TES-SRV version 14.00.2002 (with a limit of 0 connections)
01/13/2019 00:26:24,Information,
01/13/2019 00:26:24,Information, Restoring the "msdb" SQL Server databases is expected...
01/13/2019 00:26:24,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
01/13/2019 00:26:24,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 8736
01/13/2019 00:26:24,Information, Event Global\sqlserverRecComplete opened
01/12/2019 23:07:13,Info, SQLServerAgent interrupted (normal)
01/12/2019 23:07:13,Error, Local node server is not running
01/12/2019 23:07:11,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
01/12/2019 22:58:11,Warning, Processor idle condition not defined - OnIdle type job schedules will not be used
01/12/2019 22:58:11,Warning, Failed to start mail session.
01/12/2019 22:58:11,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
01/12/2019 22:58:11,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
01/12/2019 22:58:10,Information, There are 7 subsystems in the subsystem cache
01/12/2019 22:58:10,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
01/12/2019 22:58:10,Information, 16 processors and 32430 MB of RAM detected
01/12/2019 22:58:10,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
01/12/2019 22:58:10,Information, ODBC driver for SQL Server version 14.00.2002
01/12/2019 22:58:10,Information, SQL Server TES-SRV version 14.00.2002 (limited to 0 connections)
01/12/2019 22:58:09,Information,
01/12/2019 22:58:09,Information, Restoration of SQL Server databases "msdb" is pending...
01/12/2019 22:58:09,Info, The SQL Server Agent Launch Service account is equal to TES-GROUP\TES-SRV$.
01/12/2019 22:58:09,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 3508
01/12/2019 22:58:09,Information, Event Global\sqlserverRecComplete opened
01/12/2019 21:42:21,Information, SQLServerAgent interrupted (normal)
01/12/2019 21:42:21,Error, Login to server "(local)" failed (DisableAgentXPs)
01/12/2019 21:42:21,Error, SQLServer error: 773
01/12/2019 21:42:21,Error, SQLServer error: 21
01/12/2019 21:42:20,Error, Login to server "(local)" failed (SaveAllSchedules)
01/12/2019 21:42:20,Error, SQLServer error: 773
01/12/2019 21:42:20,Error, SQLServer error: 21
01/12/2019 21:42:18,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
01/10/2019 00:05:43,Warning, Processor idle condition not defined - OnIdle type job schedules will not be used
01/10/2019 00:05:43,Warning, Failed to start mail session.
01/10/2019 00:05:43,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
01/10/2019 00:05:43,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
01/10/2019 00:05:42,Information, There are 7 subsystems in the subsystem cache
01/10/2019 00:05:41,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
01/10/2019 00:05:41,Information, 16 processors and 32430 MB of RAM detected
01/10/2019 00:05:41,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
01/10/2019 00:05:41,Information, ODBC driver for SQL Server version 14.00.2002
01/10/2019 00:05:41,Information, SQL Server TES-SRV version 14.00.2002 (limited to 0 connections)
01/10/2019 00:05:40,Info, The configuration parameter "Agent XPs" was changed from 0 to 1. Run the RECONFIGURE statement to install.
(Message 15457)
01/10/2019 00:04:27,Information, Restoring the "msdb" SQL Server databases is expected...
01/10/2019 00:04:27,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
01/10/2019 00:04:27,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 14060
01/10/2019 00:04:27,Information, Event Global\sqlserverRecComplete opened
01/09/2019 23:49:50,Information, SQLServerAgent interrupted (normal)
01/09/2019 23:49:50,Info, The configuration parameter "Agent XPs" was changed from 1 to 0. Run the RECONFIGURE statement to install.
received from the user
process or OS...
05/12/2018 00:30:13,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
05/12/2018 00:30:13,Warning, Failed to start mail session.
05/12/2018 00:30:13,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
05/12/2018 00:30:13,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
05/12/2018 00:30:12,Information, There are 7 subsystems in the subsystem cache
05/12/2018 00:30:10,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
05/12/2018 00:30:10,Information, ODBC driver for SQL Server version 14.00.2002
05/12/2018 00:30:10,Information, SQL Server TES-SRV version 14.00.2002 (with a limit of 0 connections)
12/05/2018 00:30:07,Information,
05/12/2018 00:30:07,Information, Restoring the "msdb" SQL Server databases is expected...
05/12/2018 00:30:07,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
05/12/2018 00:30:07,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 11212
12/05/2018 00:30:07,Information, Event Global\sqlserverRecComplete opened
11/30/2018 23:08:29,Information, SQLServerAgent interrupted (normal)
11/30/2018 23:08:29,Error, Login to server "(local)" failed (DisableAgentXPs)
11/30/2018 23:08:29,Error, SQLServer error: 773
11/30/2018 23:08:29,Error, SQLServer error: 21
11/30/2018 23:08:29,Error, Login to server "(local)" failed (SaveAllSchedules)
11/30/2018 23:08:29,Error, SQLServer error: 773
11/30/2018 23:08:29,Error, SQLServer error: 21
11/30/2018 23:08:29,Error, SQLServer error: 773
11/30/2018 23:08:29,Error, SQLServer error: 21
11/30/2018 23:08:27,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
02/11/2018 23:13:51,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
11/02/2018 23:13:51,Warning, Failed to start mail session.
02/11/2018 23:13:51,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
02/11/2018 23:13:51,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
02/11/2018 23:13:50,Information, There are 7 subsystems in the subsystem cache
11/02/2018 23:13:50,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
02/11/2018 23:13:50,Information, 16 processors and 32430 MB of RAM detected
02/11/2018 23:13:50,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
11/02/2018 23:13:50,Information, ODBC driver for SQL Server version 14.00.2002
11/02/2018 23:13:50,Information, SQL Server TES-SRV version 14.00.2002 (with a limit of 0 connections)
11/02/2018 23:13:49,Information,
11/02/2018 23:12:40,Information, Restoring the "msdb" SQL Server databases is expected...
02/11/2018 23:12:39,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
02/11/2018 23:12:39,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 6416
11/02/2018 23:12:39,Information, Event Global\sqlserverRecComplete opened
11/02/2018 14:25:22,Warning, SQLServerAgent terminated (forced)
02/11/2018 14:25:22,Error, Login to server "(local)" failed (DisableAgentXPs)
11/02/2018 14:25:22,Error, ODBC error: 0
11/02/2018 14:25:22,Error, SQLServer error: 21
02/11/2018 14:25:22,Error, Thread "JobInvocationEngine" (ID 9956) is still running
02/11/2018 14:25:22,Error, 1 handler threads could not stop after 2 seconds of waiting
11/02/2018 14:25:19,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
10/29/2018 01:12:13,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
10/29/2018 01:12:13,Warning, Failed to start mail session.
10/29/2018 01:12:13,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
10/29/2018 01:12:13,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
10/29/2018 01:12:12,Information, There are 7 subsystems in the subsystem cache
10/29/2018 01:12:11,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
10/29/2018 01:12:11,Information, 16 processors and 32430 MB of RAM detected
10/29/2018 01:12:11,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
10/29/2018 01:12:11,Information, ODBC driver for SQL Server version 14.00.2002
10/29/2018 01:12:11,Information, SQL Server TES-SRV version 14.00.2002 (limited to 0 connections)
10/29/2018 01:12:10,Information,
10/29/2018 01:12:10,Information, Restoring the "msdb" SQL Server databases is expected...
10/29/2018 01:12:10,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
10/29/2018 01:12:10,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 9756
10/29/2018 01:12:10,Information, Event Global\sqlserverRecComplete opened
10/23/2018 18:34:43,Info, SQLServerAgent interrupted (normal)
10/23/2018 18:34:43,Error, Login to server "(local)" failed (DisableAgentXPs)
10/23/2018 18:34:43,Error, SQLServer error: 773
10/23/2018 18:34:43,Error, SQLServer error: 21
10/23/2018 18:34:42,Error, Login to server "(local)" failed (SaveAllSchedules)
10/23/2018 18:34:42,Error, SQLServer error: 773
10/23/2018 18:34:42,Error, SQLServer error: 21
10/23/2018 18:34:41,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
13/10/2018 22:13:43,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
10/13/2018 22:13:43,Warning, Failed to start mail session.
13/10/2018 22:13:43,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
10/13/2018 22:13:43,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
10/13/2018 22:13:41,Information, There are 7 subsystems in the subsystem cache
10/13/2018 22:13:40,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
10/13/2018 22:13:40,Information, 16 processors and 32430 MB of RAM detected
10/13/2018 22:13:40,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
10/13/2018 22:13:40,Information, ODBC driver for SQL Server version 14.00.2002
10/13/2018 22:13:40,Information, SQL Server TES-SRV version 14.00.2002 (with a limit of 0 connections)
10/13/2018 22:13:40,Information,
10/13/2018 22:13:40,Information, Restoring the "msdb" SQL Server databases is expected...
10/13/2018 22:13:39,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
10/13/2018 22:13:39,Information, Microsoft SQLServerAgent version 14.0.2002.14 (X64 unicode commercial build): process ID 5192
10/13/2018 22:13:39,Information, Event Global\sqlserverRecComplete opened
10/13/2018 18:54:15,Information, SQLServerAgent interrupted (normal)
10/13/2018 18:54:15,Error, Local node server is not running
10/13/2018 18:54:13,Information, Stopping SQLSERVERAGENT due to Windows shutdown...
10/13/2018 18:53:12,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
10/13/2018 18:53:12,Warning, Failed to start mail session.
13/10/2018 18:53:12,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
10/13/2018 18:53:12,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
10/13/2018 18:53:11,Information, There are 7 subsystems in the subsystem cache
10/13/2018 18:53:11,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
10/13/2018 18:53:11,Information, 16 processors and 32430 MB of RAM detected
10/13/2018 18:53:11,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
10/13/2018 18:53:11,Information, ODBC driver for SQL Server version 14.00.1000
10/13/2018 18:53:11,Information, SQL Server TES-SRV version 14.00.1000 (limited to 0 connections)
10/13/2018 18:53:10,Information,
10/13/2018 18:53:10,Information, Restoring the "msdb" SQL Server databases is expected...
10/13/2018 18:53:10,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
10/13/2018 18:53:10,Information, Microsoft SQLServerAgent version 14.0.1000.169 (X64 unicode commercial build): process ID 10744
10/13/2018 18:53:10,Information, Event Global\sqlserverRecComplete opened
01/10/2018 23:01:22,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
10/01/2018 23:01:22,Warning, Failed to start mail session.
01/10/2018 23:01:22,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
01/10/2018 23:01:22,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
10/01/2018 23:01:21,Information, There are 7 subsystems in the subsystem cache
10/01/2018 23:01:21,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
10/01/2018 23:01:21,Information, 16 processors and 32430 MB of RAM detected
10/01/2018 23:01:21,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
10/01/2018 23:01:21,Information, ODBC driver for SQL Server version 14.00.1000
10/01/2018 23:01:21,Information, SQL Server TES-SRV version 14.00.1000 (limited to 0 connections)
10/01/2018 23:01:20,Information,
10/01/2018 23:01:17,Information, Restoring the "msdb" SQL Server databases is expected...
01/10/2018 23:01:17,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
10/01/2018 23:01:17,Information, Microsoft SQLServerAgent version 14.0.1000.169 (X64 unicode commercial build): process ID 4900
10/01/2018 23:01:17,Information, Event Global\sqlserverRecComplete opened
09/28/2018 22:11:58,Warning, Processor idle condition is not defined - OnIdle type job schedules will not be used
09/28/2018 22:11:58,Warning, Failed to start mail session.
09/28/2018 22:11:58,Warning, Database Mail component profile could not be updated. (reason: Email profile not defined)
09/28/2018 22:11:58,Info, SQLSERVERAGENT started using NT Windows Service Control Tool
09/28/2018 22:11:57,Information, There are 7 subsystems in the subsystem cache
09/28/2018 22:11:56,Information, Local computer TES-SRV runs Windows Server 2016 Standard 10.0 (14393)
09/28/2018 22:11:56,Information, 16 processors and 32430 MB of RAM detected
09/28/2018 22:11:56,Information, The driver uses DBNETLIB as the NetLib library; local node server: TES-SRV
09/28/2018 22:11:56,Information, ODBC driver for SQL Server version 14.00.1000
09/28/2018 22:11:56,Information, SQL Server TES-SRV version 14.00.1000 (limited to 0 connections)
09/28/2018 22:11:56,Information,
09/28/2018 22:11:54,Information, Restoration of SQL Server databases "msdb" is pending...
09/28/2018 22:11:53,Info, The SQL Server Agent Launch Service account is equal to TES-SRV\Administrator.
09/28/2018 22:11:53,Information, Microsoft SQLServerAgent version 14.0.1000.169 (X64 unicode commercial build): process ID 5724
09/28/2018 22:11:53,Information, Event Global\sqlserverRecComplete opened
I think that most users have encountered such a problem as freezing of services in Windows, and an attempt to forcefully terminate such a service was unsuccessful, and it hangs in mode "Stopping". It is also not possible to restart or forcefully terminate the service from the graphical interface, and restarting the server itself, in our case the computer, may not always be acceptable.
Now we will look at a method that will help you forcefully terminate a process that has frozen, without the need to restart the device itself.
How to forcefully terminate a hung service?
So, as soon as 30 seconds have passed and it is clear that the service has not stopped, Windows will display the following message:
You can quickly and effortlessly terminate a hung process using the utility. Before doing this you will need to define PID process (service). For example, we will use the service, the system process name is wuauserv.
Attention! If you terminate an important process, it may result in a system reboot or BSOD (Screen of Death).
Now open the command line with admin rights; if you don’t do this, an error may occur. Enter the following into the command line:
A message appears indicating that the Windows Update service has ended. You can then return to service management and start the process there again, or delete it altogether if you don’t use it.
There is another method for forcing the process to terminate without needing to find out the PID. The already familiar utility will help us in this matter. We run it as administrator.
The following command will help us identify services that are in the stopping state:
| Get-WmiObject -Class win32_service | Where-Object ($_.state -eq ‘stop pending’) |
Now we need to complete the process for the services we found, this will help us. Using the following script, all suspended services in the system will be terminated:
$Services = Get-WmiObject -Class win32_service -Filter “state = ‘stop pending"”
if ($Services) (
foreach ($service in $Services) (
try (
Stop-Process -Id $service.processid -Force -PassThru -ErrorAction Stop
}
catch (
Write-Warning -Message » Error. Error details: $_.Exception.Message"
}
}
}
else(
Write-Output “No services with ‘Stopping’.status”
}
That's all, today we were able to terminate processes that we could not terminate, for example, using the device manager or from the graphical shell.
Good afternoon!. Last time we looked at the problem with code 43 and descriptor request failure, today I want to show you another unpleasant moment that I encountered on Windows Server 2012 R2, but it also occurs on other platforms. The point of the glitch is that you get service startup error code 1053, or there may also be wording that the service did not respond to the request. This prevents your application from starting and running, we will look at the main reasons for this behavior and eliminate them.
What does error 1053 look like? The service did not respond to the request.
A little background. I continue the process of virtualizing an old fleet of physical servers, for this I use the P2V VMware vCenter Converter Standalone 6.2 utility. Everything went as usual, I rolled up the utility and tried to launch it, but the program window did not appear for a long time. After a while I got an error on the screen:
Vmware vCenter Converter Standalone Server is installed but not running. When VMware vCenter Converter Standalone Server is not running, you will not be able to connect to local server. Do you want to start it now?
The message says that the converter service is not running, do you want to start it, I choose of course yes. After about 30 seconds, a second window appears with the following text:
We are told that the converter service cannot be started. In the Services snap-in, you can see three VMware vCenter Converter services.
I try to start the application service manually, via right-click, but a warning pops up:
Windows could not start the VMware vCenter Converter Standalone Worker service on Local Computer. Error 1053: The service did not respond tj the start or control request in a timely fashion.
In the Russian version, it looks like this:
The service (Service Name) could not be started on the local computer.
Error 1053: The service did not respond to the start or control request in a timely manner.
List of services and programs where you can see error 1053
Let me give you a list with examples where you can see the service response. that she didn't answer
- VMware vCenter Converter Standalone 6.2
- Apple Mobile Device Service (ITunes)
- QEMU Guest Agent
- At the time of installing the Rutoken drivers
- Skype
- MSSQL Service
- SharePoint
- 4game-service
As you can see, the range of problems is very large and varied, the same applies to operating systems, you can easily see this on client Windows 7 or Windows 10, and on server Windows Server 2012 R2 and higher.
How to fix error 1053
Let me show you how I corrected error code 1053 in the case of the Vmware vCenter Converter Standalone utility, but the described technique is also suitable for other services and programs.
- First of all, you must go to the service snap-in, this is very simple, to do this, press two keys Win and R at the same time, you will see the “Run” window, write the word in it services.msc, this is the system name of this equipment, see the link for details.
You will see a snap-in with all the services that are in the operating system. You find the one you need, which in your case gave the message “the service cannot start, error 1053,” and try to start it manually. To do this, you right-click on it and select “Run” from the context menu. In some cases, this can help, oddly enough, but this was not my case.
We see that we have received the same error, do not despair, since everything is just beginning. Through the same context menu, select the “Properties” item. Here the situation may be like this. Some services, for the life of me, cannot function without others, and while others are not running, they will also be idle, and as a result of this, you can see a message with code 1053. This combination is called a dependency. You can see whether your faulty service has it or not on the corresponding “Dependencies” tab. In my case, for the Vmware vCenter Converter Standalone utility to work, the “Workstation” service needs to work, which, as you can see, consists of three components.
We close this window and in the list of services, look for the dependent one we need, I remind you that this is the “Workstation” service. As you can see, it turned out to be running, if your dependent service is turned off, then try to start it and when it starts working, try to start the main one.
- If the trick with dependent services did not help you and you, like me, still receive the message “the service did not respond in a timely manner,” try checking your DNS settings. It happens that some programs must connect to a workstation or server by name in order to work, and if this does not work, then you find yourself in this situation. Open the TCP/IPv4 settings and check your data by IP address and DNS server, see the link on the left for how to get there. My address was configured statically (manually), if you have an automatic one, in most cases users there have an automatic setting that comes from a DHCP service located on another server or network equipment, for example, in home computers, this is WIFi or a regular router.
I noticed at home that the first of the DNS servers, some strange one that was not familiar to me, apparently someone had registered it earlier. I'm trying to check its network availability using the ping command and at the same time find out its name.
ping -a ip address of your dns
It didn’t respond to me, I also tried to resolve the name of this server, where I received an error, its IP address in my example ends with 157, the name was determined, which means the second DNS server processed everything correctly, I corrected the first one. If you have a domain computer, make sure that names are resolved via IP. Let's go look for a solution further.
- I continued to study this issue and came across one discussion on my utility Vmware vCenter Converter Standalone (https://docs.vmware.com/en/vCenter-Converter-Standalone/6.2/rn/conv_sa_62_rel_notes.html), it described the situation that due to the fact that the DNS name cannot be resolved within 30 seconds, you may receive service error 1053. It suggested changing the standard value in the Windows operating system to another one, increasing the check interval.
In 90% of cases you have error 1053, the service did not respond in a timely manner, it will pass. I also saw a situation that after a reboot, those services that come with delayed start may take a little longer to start than usual, sometimes they even have to be started manually, but they work. For me personally, this method helped with Vmware vCenter Converter Standalone.
Additional methods to fix error 1053
Unfortunately, the trick with a registry key does not always work and not with all software; in 10% of cases you will all see a warning “the service did not respond to the request in a timely manner,” here I will provide a checklist that will allow you to eliminate the cause.
- In some cases, many programs in their code have code that works with net framework libraries, and if they are damaged on your computer, then code 1053 may appear, in such cases we do this:
I hope that I helped you a little in eliminating the warning code 1053 and you managed to start the necessary service..
When installing the Rutoken Drivers, an error occurs: "Calling function: RTSC_Wait_For_Service_Status. Error code: 1053: The service did not respond to the start or control request in a timely fashion. (Error code: 1053: The service did not respond to the request in a timely manner)"
Cause
When installing the Rutoken Drivers, an attempt is made to restart the Smart Card service, the performance of which is one of the most important components for working with the Rutoken key identifier. If it is impossible to restart the specified service, error code 1053 occurs. There may be various reasons for problems with the Smart Card service.
Solution
1. Disable your antivirus while installing Rutoken Drivers
2. Make sure that the registry branches ("Start" - "Run" - regedit)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\Readers
The Local Service user has full access: RMB on the desired branch - Permissions - select the desired user (*) and check the "Full access" checkbox at the bottom
(*) If the required user is not in the selection, you need to add it:
Click "Add"
In the "Enter the names of objects to select" field, enter LO
Click "Check Names"
Select Local Service
3. Make sure that the Smart Card Service is running as NT AUTHORITY\LocalService ("Start" - "Control Panel" - "Administration" - "Services"). Start/Restart the service.
4. If the service does not work/does not start/does not restart, it may need to be reinstalled (System administrators only!).
1) Win7, Vista, Win8/8.1, Win10
Run the file (smart-card-7) from the attachment
Restart your computer
Reinstall the smart card service according to the instructions in the attachment (Smart-Card-XP)
Manually editing the Windows registry to remove Error 1053 keys that contain errors is not recommended unless you are a PC service professional. Mistakes made when editing the registry can render your PC inoperable and cause irreparable damage to your operating system. In fact, even one comma placed in the wrong place can prevent your computer from booting!
Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster [Download] (developed by Microsoft Gold Certified Partner) to scan and repair any Error 1053-related issues. Using Registry Cleaner [Download] you can automate the process of finding corrupted registry entries, missing file references (such as those causing the %%error_name% error), and broken links within the registry. Before each scan, a backup copy is automatically created, allowing you to undo any changes with one click and protecting you from possible damage to your computer. The best part is that fixing registry errors [Download] can dramatically improve system speed and performance.
Warning: Unless you are an experienced PC user, we DO NOT recommend manually editing the Windows Registry. Using Registry Editor incorrectly may cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from incorrect use of Registry Editor can be corrected. You use Registry Editor at your own risk.
Before you manually repair the Windows registry, you need to create a backup by exporting the portion of the registry associated with Error 1053 (for example, Windows):
- Click on the button Begin.
- Enter " command" V search bar... DON'T CLICK YET ENTER!
- While holding down the keys CTRL-Shift on your keyboard, press ENTER.
- A dialog box for access will be displayed.
- Click Yes.
- The black box opens with a blinking cursor.
- Enter " regedit" and press ENTER.
- In the Registry Editor, select the Error 1053-related key (for example, Windows) that you want to back up.
- On the menu File select Export.
- On the list Save to select the folder where you want to save the Windows key backup.
- In field File name Enter a name for the backup file, for example "Windows backup".
- Make sure the field Export range value selected Selected branch.
- Click Save.
- The file will be saved with extension .reg.
- You now have a backup of your Windows-related registry entry.
The following steps for manually editing the registry will not be described in this article, as they are likely to damage your system. If you would like more information about editing the registry manually, please check out the links below.
