Iniciar sesión
 
InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI >
> 
> 
windows could not start smsagenthost service Error: 1053

Respondida windows could not start smsagenthost service Error: 1053

  • miércoles, 23 de mayo de 2012 10:26
     
     
    Inicie sesión para votar
    0

    HI,

    I tried to start the ccmexec service but not able to start the service. I got the below error

    windows could not start smsagenthost service

    Error: 1053. The service did not respond to the start and or control request in a timely fashion

    Please help on the error

    Regards,

    Boopathi S

     

Todas las respuestas

  • miércoles, 23 de mayo de 2012 10:31
     
     
    Inicie sesión para votar
    0

    Hi

    Take a look in the ccmexec.log, it will have more details about any error it is having when the service is starting.

    Regards

     
  • miércoles, 23 de mayo de 2012 14:44
     
     
    Inicie sesión para votar
    0
    if reinstalling doesn't help, make sure to do a proper uninstall with ccmclean.
     
  • miércoles, 23 de mayo de 2012 17:05
     
     
    Inicie sesión para votar
    0
    ccmclean is not supported or recommended for use with ConfigMgr 2007 clients. That's kind of a drastic step to take also without examining any log files first to try to determine a root cause.

    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

     
  • jueves, 24 de mayo de 2012 5:43
     
     
    Inicie sesión para votar
    0

    HI,

    Please find the below erros in ccmexec.log

    The CCM namespace does not exist. Repair required.
    Detected faulty configuration. Repair will be started in 5 minutes.
    Entering main message loop.
    WM_QUIT received in the main message loop.
    Shutting down CCMEXEC...
    UninitCommandExec failed (0x800401fb).
    SystemTaskProcessor::Shutdown failed with code 0x8000ffff
    Error invoking shutdown system tasks (0x8000ffff)
    Waiting up to 2 seconds for active tasks to complete...
    Error waiting for tasks (0x8000ffff), will shut down anyway.
    Finished shutting down CCMEXEC.

    Regards,

    Boopathi S

     
  • martes, 29 de mayo de 2012 9:09
    Moderador
     
     Respondida
    Inicie sesión para votar
    1

    This issue can be WMI related.

    What about to repair the WMI?

    WMI Troubleshooting Tips

    Sabrina

    TechNet Community Support

     
  • miércoles, 30 de mayo de 2012 13:40
     
     Respondida
    Inicie sesión para votar
    1

    I agree with the thought below from Sabrina that this is a WMI issue.

    How many machines is this happening on?  I've seen many people get stuck on an error with one machine and spend a lot of time trying to troubleshoot something that is an anomaly.

    If it is one or a relatively small percentage then if a repair of the client does not work then reinstall the client.  If that doesn't work then some WMI repair, or more drastically, a rebuild of the machine.  What is a small percentage?  Thinking of past environments I've dealt with, about 5% or so might be considered reasonable.

    If it is a larger percentage of machines then it has to be determined what they have in common.  Perhaps there is something in your image or build process that is causing the WMI issue on a more widespread basis.

    John DeVito