Cause of Service Control Manager restarting a service - windows

Service Control Manager in Windows Server 2016 keeps restarting one of the service every 1 min. How can we find the reason behind service control manager restarting the service?
On checking out the event view I am able to see Event ID 7031 with the below error description:
service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Locate the service (as it is named in the Event description) in Windows services console (Run->Services.msc).
Right-click on the service and go to Properties.
Navigate to the Recovery tab. Here it is defined the action taken (in your case restart the service) when the service terminates unexpectedly as for Event ID 7031

Related

What are the reason when a stopped windows service starts automatically?

What are the reason when a stopped windows service starts automatically?
I know only few which are
When service start-up mode is automatic and someone re-start the server then service will also get started.
When someone forcefully start the service manually.
Is there any other way when a stopped service can start?
Service triggers. This can be hardware device added, internet connection discovered, group policy change or any ETW event.
Have you checked there is a service Dependence? If another service depends on its function, it will automatically come up even though you stop the service.
Since it keeps restarting, it means you are not suppose to disable or stop the service.
Locate the ASP.NET State Service and check the Startup Type property and click the recovery tab for your service configuration and check if the options there could be restarting it.
You can also run a virus scan on your system to be sure your pc is safe.

TFS Waiting for Service to Start

I'm using TFS Express and trying to set up the environment. I create the project and then it hangs saying its 'Waiting for Service to Start"
What service is it waiting for to start?
Check TFS Background Job Agent service is running or not.
Check Event log in Event Viewer to see whether there is useful information.

Visual Studio 2013 loadtest: remote Controller cannot restart Agents and cannot run load test

I have succesfully installed a load test Controller and 3 agents on 4 different machines. All of the services are running under the same domain account, and this account is in the Administrator's group on all four machines. From each Agent machine I successfully registered with the controller using the Test Agent Configuration Tool.
In a Visual Studio 2013 load test project I selected the controller in the "Test Settings" dialog, and then from my load test I opened the "Manage Test Controller" dialog by clicking the wrench icon. I see my selected controller, all 3 of my agents, and the correct database connection string that I used when setting up the controller.
If I click the "Restart Controller and Agents" button I get the error message "Rig failed to restart for controller 'Controller1'. The following error was reported: Object reference not set to an instance of an object."
I click the same button again and get a slightly different error message: "An existing connection was forcibly closed by the remote host."
I can see that the controller is recieving the command, because this error is seen in the event viewer on the Controller machine, repeated for each agent: (QTController.exe, PID 4984, Thread 15) AgentManager: Exception stopping agent service for agent 'Agent1' on machine 'Agent1.MyDomain.com': Cannot stop VSTTAgent service on computer 'Agent1.MyDomain.com'.
For each individual agent, I can select "restart" and it successfully restarts (I confirmed this by observing the Event Viewer on each agent machine). Each agent shows as "Ready" in the status column
If I try to run the load test it shows "pending" for 60-90 seconds, then finally stops with the error message "Failed to queue test run 'MyName#MyMachineName 2015-10-28 11:44:23': A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond".
I turned on verbose logging for the controller service, and when I attempt to run the test I see that the service recieves the command. The service tries repeatedly to connect to all 3 agents, this bit of code is printed for each agent in the log file repeatedly until my test errors out:
V, 3600, 26, 2015/10/28, 11:52:53.372, Controller1\QTController.exe, ControllerObject.RequireAgentServiceUser: Agent: Agent1 of environment [Default] trying to connect.
V, 3600, 26, 2015/10/28, 11:52:53.372, Controller1\QTController.exe, ControllerObject: AgentHello from Agent1
V, 3600, 26, 2015/10/28, 11:52:53.372, Controller1\QTController.exe, Verifying the connection integrity for following number of objects: 3
windows Firewall is turned off on all 5 machines (the controller, the 3 agents, and the machine with the Visual Studio loadtest project).
I've tried using the IP address of the controller instead of the host name (using the "bindto" appsetting in the controller configuration file) but get the same sad results.
I've tried rebooting and restarting all services, to no good effect.
Is there any way to debug or fix this issue?

IIS w3svc error

I am trying to start my website in IIS, whenever I try to start my website I get the following error
Cannot start service w3svc on computer
I tried to start "World wide web publishing service", but I was unable to start it as it said:
Error 1068: The dependency service or group failed to start
Meanwhile when I checked my log I found this error,
The World Wide Web Publishing Service service depends on the HTTP service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Please help me, I am badly caught with this error, I have spent a week researching this error but haven't found a solution yet.
Confirm that "Windows Management Instrumentation" is started and its start up type is set to automatic.
Also make sure the following dependency services are started for World Wide Web Publishing Service:
Windows Process Activation Service
Remote Procedure Call (RPC)
DCOM Server Process Launcher
RPC Endpoint Mapper.
Open regedit, navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP]:
a) Double click on Start and change value data from 4(disabled) to 3(automatically).
b) Delete "NoRun" key if this key exists.
(warning: backup any IIS website configuration first). UN-install "Internet information Service" and "Windows process activation service(if it is already installed)" from "Turn windows feature on or off" and Restart your PC.
Type the below command in CMD and press enter:
net start http
Now it will notify you that service is already running.
Re-install Internet information Service from "Turn windows feature on or off".
Start IIS and my websites are started now, no more "w3svc service is not running error."
As for me - I just restarted the computer.
Make sure these 2 services running and their startup type is automatic.If they disabled and not running right click on them and go to properties and change from there.
Windows process activation service
Worldwide web publishing service.
Run cmd as administrator. Type iisreset. That's it.
Go to Task Manager --> Processes and manually stop the W3SVC process. After doing this the process should start normally when restarting IIS
In my case it was C:\Windows\System32\inetsrv\config\applicationHost.config which had an issue.
I had a "system.web" section in this file which was causing the problem. Removed the section and everything started working
I have got same issue on my server. Follow below steps -
Open command prompt (run as administrator)
type IISReset and enter.
It works and solved my problem.
I have had this problem after a windows update. Windows Process Activation Service is dependent service for W3SVC. First, make sure that Windows Process Activation Service is running. In my case, it was not running and when I tried to run it manually, I got below error.
Windows Process Activation Service Error 2: The system cannot find the file specified
The issue seems to be, that windows adds an incorrect parameter to the WAS service startup parameters. I fixed the issue using the following steps:
Start regedit (just type it into start) Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WAS\Parameters
Delete the NanoSetup variable. This variable is preventing WAS from starting
Start the WAS service using task manager
Now start the W3SVC service
You can now start your website in IIS again
I found above WPA service solution in this stack overflow thread.
In my case, IIS suddenly stopped working, and after that Windows process activation service was unable to restart.
The solution to fix this was:
Find WAS service in the services tab of windows task manager
In context menu choose Go to process
Kill process (its name will be svchost.exe)
Restart Windows process activation service
My Net.Tcp Port Sharing Service was disabled. I changed its startup to manual, started the service, and then IISRESET worked.
I also verified that the following dependent services were started in Services ([windows]+[r] services.msc):
World Wide Web Publishing Service
Windows Process Activation Service
Remote Procedure Call (RPC)
DCOM Server Process Launcher
RPC Endpoint Mapper
Net.Msmq Listener Adapter
Net.Pipe Listener Adapter
Net.Tcp Listener Adapter
Net.Tcp Port Sharing Service
I found this solution by going through all dependencies and child dependencies of the World Wide Web Publishing Service and making sure that each service was enabled and started.
To verify all services for yourself, do the following:
Open up Services (just search for it from the start menu in Windows 10)
Find the World Wide Web Publishing Service
Right click on the service and then click "Properties"
Click on the Dependencies tab
Go through each system component in the two boxes and verify that each service is started (in Services).
Repeat steps 3-5 for each of the dependencies' dependencies until you run out of child dependencies
Service Properties - Dependencies Tab
This is probably a rarer case, but...
If you are using a custom AppPool Identity configuration be sure to check the AppPool is running. It may be turned off because credentials are invalid (usually due to an expired password). Update your credentials and start the AppPool.
I am able to resolve this by simply executing the below command in PowerShell to kill/stop service and restart the IIS server
taskkill /F /FI "SERVICES eq w3svc"
I managed to solve after:
Ctrl+Shift+Esc = To open Task Manager
In the "Processes" tab locate the "IIS Worker Process" and
finish it!
Run on cmd as an administrator. Type iisreset.
I was getting this error. It turns out World Wide Web Publishing Service was disabled.
Click Start, type Services in the Search box, and then click Services.
Scroll until you find the World Wide Web Publishing Service that is stopped or disabled.
right-click the service, and then click Properties.
Click the Startup type list, and then click Automatic.
Click Apply, and then click OK.

How to start windows service

I have created a windows service with Automatic Start Type and install it in my system successfully but it does not start until i restart my system.
Details: yesterday i have create and install my service and then restart my windows so the service started successfully. but the problem occurred today when i boot my windows and opened the services list of windows from Control Panel\Administrative Tools\Services and selected my service i saw that it did not start automatically.
what is my mistake?
Assuming the service is set to 'Automatic' as the startup mode, and that it's state is not 'Started', then there will be at least one message about why the service did not start in the System Event Log.
Typical reasons are that the service didn't start quickly enough (Service Controller imposes a time limit on how quickly services must respond to the 'Start' message) or that the service depended on another service which wasn't yet available (check your service dependencies) or that your service simply failed due to a software error (e.g. some resource it needs could not be found).
Find the error in the event log, and you'll have a much better idea of why your service hasn't started.
As your service was running fine yesterday but not today. Checking all its dependencies would be my first suggestion.
In your Start-> Run, type services.msc . It's a shortcut to open the services console.
Then Right click on your service , if it is listed there, click on Properties on this popup menu.
Open the Dependency tab (4th tab) , check if your service depends on some other service and that dependency is running.
Regards,
bhupendra
Example:
SC.exe config "ServiceName" start= auto

Resources