locked
The service cannot accept control messages at this time RRS feed

  • Question

  • Hi!

    I've collected some errors I get trying to do several tasks on a 2008 R2 fileserver. (Opening Server Manager, Services, looking at file permissions, open the reg. editor...) I haven't tried a restart yet, because of the criticallity of the server

    Has anyone out there seen this problem?


    Freddy

    Friday, May 25, 2012 12:40 PM

Answers

  • Please restart it when it is possible to do that. Maybe it is a temporary issue.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by CesarTabares Tuesday, May 29, 2012 7:12 AM
    Friday, May 25, 2012 1:12 PM

All replies

  • Please restart it when it is possible to do that. Maybe it is a temporary issue.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by CesarTabares Tuesday, May 29, 2012 7:12 AM
    Friday, May 25, 2012 1:12 PM
  • open powershell and run the following:

    Get-WmiObject win32_service | Sort-Object State | select name, startmode, state

    Check the output to make sure you dont have any services that should be started, but are not , and that you dont have any services stuck in start/stop pending.
    • Proposed as answer by Sinnaral Friday, August 10, 2012 2:17 PM
    • Unproposed as answer by Sinnaral Friday, August 10, 2012 2:17 PM
    • Proposed as answer by Sinnaral Friday, August 10, 2012 2:19 PM
    • Unproposed as answer by Sinnaral Friday, August 10, 2012 2:19 PM
    Friday, May 25, 2012 1:15 PM
  • To whomever, I had this issue and banged my head against a wall for a while, then i remembered I disabled a set of processes due to a previous issue. I am 100% it is a process, probably AppMgmt, AppIDSrv or one of those 4 App*.*

    I reset with a default process setting enabled and problem fixed.

    • Proposed as answer by david_santiago Tuesday, June 12, 2012 10:19 AM
    Tuesday, June 12, 2012 10:19 AM
  • Restarting fixed the issue in my case.
    Monday, July 1, 2013 11:15 AM
  • Microsoft says all you have to do is wait:

    MS Link - The service cannot accept control messages at this time

    But as someone else found, rebooting sounds like a good option, too.

    -Tom

    Wednesday, August 28, 2013 3:04 AM
  • hi, to me rebooting didn´t solved my problem. i need some help because services, windows firewall, task manager and many others are stuck in that message.

    Helder Pereira

    Wednesday, October 30, 2013 11:18 AM
  • For those who cannot reboot a production server that is business critical:

    This issue is caused by the Application Information service not responding to requests to elevate applications to Administrator (such as MMC, MSC, etc), resulting in the error message.

    1. Log in as the local administrator account.
    2. Open Services.msc, and keep it minimized (the following steps will prevent you from running services.msc to start the service after it has been killed so services.msc will need to be open beforehand!)
    3. Run Process Explorer as Administrator
    4. Kill the svchost.exe netsvcs process.
    5. Then start the Application Information service from Services.

    Check all automatic services as a few may have stopped (Group Policy Client and a couple of other non critical services) and start them again.

    This should resolve the issue.

    This is particularly helpful on critical production servers which can't be rebooted as that could cause disruption to service, but can also be used on desktops if you don't wish to reboot.



    • Edited by harpss1ngh Thursday, February 13, 2014 9:28 AM
    • Proposed as answer by harpss1ngh Thursday, February 13, 2014 12:08 PM
    Thursday, February 13, 2014 9:23 AM
  • For those who cannot reboot a production server that is business critical:

    This issue is caused by the Application Information service not responding to requests to elevate applications to Administrator (such as MMC, MSC, etc), resulting in the error message.

    1. Log in as the local administrator account.
    2. Open Services.msc, and keep it minimized (the following steps will prevent you from running services.msc to start the service after it has been killed so services.msc will need to be open beforehand!)
    3. Run Process Explorer as Administrator
    4. Kill the svchost.exe netsvcs process.
    5. Then start the Application Information service from Services.

    Check all automatic services as a few may have stopped (Group Policy Client and a couple of other non critical services) and start them again.

    This should resolve the issue.

    This is particularly helpful on critical production servers which can't be rebooted as that could cause disruption to service, but can also be used on desktops if you don't wish to reboot.



    Sorry but that doesn't work... Tried to kill SVCHOST using Process Explorer but will be back right away.

    Application Information services is already started...

    Since I tried to kill SVCHOST nothing is working any more even from the local administrator.

    Everything is "Media Write Protected" do not attempt that or will completely crash your server and end with a restart anyway.


    • Edited by fr4nk1985 Monday, March 24, 2014 5:21 PM
    Monday, March 24, 2014 5:19 PM
  • Killing svchost.exe works for me. Thx.

    • Edited by FrankHB Saturday, November 22, 2014 12:36 AM
    Saturday, November 22, 2014 12:36 AM
  • Restarting the server ( Active Directory :/ up for 10 month ) solved the problem.
    Thursday, December 18, 2014 5:22 PM
  • Restarting Servers is not really a right choice for production environment.

    1. Login into server with administrative privilege,

    2. Start task manager -> select possible process related to the service -> stop the process

    (if you don't know which process affecting the service; you have to hit and try to find process that is related to the service.)

    3. Go to services and  check the status of service. It won't be in hand state now.

    4. If it is in hang state  - it implies some other process is also crating issue so find those process in similar fashion we did in step 2.

    5 if require start the service .



    • Edited by swayankar Monday, June 19, 2017 7:09 AM
    • Proposed as answer by ynorvo Friday, August 10, 2018 2:46 AM
    Monday, June 19, 2017 7:07 AM
  • For those who cannot reboot a production server that is business critical:

    This issue is caused by the Application Information service not responding to requests to elevate applications to Administrator (such as MMC, MSC, etc), resulting in the error message.

    1. Log in as the local administrator account.
    2. Open Services.msc, and keep it minimized (the following steps will prevent you from running services.msc to start the service after it has been killed so services.msc will need to be open beforehand!)
    3. Run Process Explorer as Administrator
    4. Kill the svchost.exe netsvcs process.
    5. Then start the Application Information service from Services.

    Check all automatic services as a few may have stopped (Group Policy Client and a couple of other non critical services) and start them again.

    This should resolve the issue.

    This is particularly helpful on critical production servers which can't be rebooted as that could cause disruption to service, but can also be used on desktops if you don't wish to reboot.



    Excellent. More powershell way of doing this (useful when you have WinRM access to the server - no need of local administrator sign in in my case)

    1st - killing svchost -netsvc process. I didn't manage to do this using stop-process and had to invoke taskkill.

    Invoke-command -scriptblock {start-process -FilePath $env:windir\System32\taskkill.exe -Wait -ArgumentList "/PID $((Get-WmiObject -Class win32_process -Property name,commandline,processid  | Where-Object {$_.commandline -eq 'C:\Windows\system32\svchost.exe -k netsvcs'}).processid) /F"}

    2nd - starting services, related to the root process:
    Get-WmiObject -Class win32_service -Property name,pathname,state,startmode | Where-Object {$_.pathname -eq "C:\Windows\system32\svchost.exe -k netsvcs"} | foreach-object { if (($_.state -ne "Running") -and ($_.startmode -ne "Disabled")) {Try {start-service -name $_.name -ErrorAction Stop} Catch {Write-host "$_"}}}

    As for me, 2nd part was successfully finished only on 2nd attempt.

    Friday, July 28, 2017 10:55 AM
  • Sergius' answer is much better than the ones above.
    The PS worked as intended.

    Services.msc, taskmgr and various other items were broken for me as UAC was on and all required elevation.  Remote PS was the only option.
    • Edited by Naamondo Thursday, October 12, 2017 1:40 PM
    Thursday, October 12, 2017 1:39 PM
  • Restarting the Application Information service is a good thing to try first.
    • Proposed as answer by divankov Monday, June 4, 2018 9:10 PM
    Tuesday, March 13, 2018 6:03 PM
  • Hi

    Just wanted to let you Know that this has worked for me i.e. restarting Application Information service.

    I had issue with VM acting as Exchange 2016 server in my virtual lab where I have recovered it - I was unable to login, and in order to fix that - I had to join Computer back to domain. Until I restarted Application Information service - it didn't let me join Computer to domain :)


    D.

    Monday, June 4, 2018 9:12 PM
  • Please install a different OS when it is possible to do that.  Effin micro$hit.
    Wednesday, January 9, 2019 7:01 PM