Folks, 

When i am trying restart the SMS Agent Service on remote machine ,I am getting below error message . Even I logged into that same machine RDP Connection still I can't 

Error Message : 

Error 1067 : The process terminated unexpectedly. 

Any one have solution 

What is in the ccmexec.log? Have you tried reinstalling the client?

Everything is not fine if the SMS Agent Host service will not start.  Look for errors in the ccmexec.log or try reinstalling the client.

Jeff

Thanks Jeff but re- installing the last step I should have to do since this was happens on more than 500 Machines

If any one there , Please help me

Can you please post the ccmexec log file?

1. If ccmexec started and then quit very quickly, you would see that in the ccmexec log file, and the logs will tell you why it quit.

2. If ccmexec did not even start, you will not see any updates to the log file, and you will think that everything is OK. In this case, service manager itself could not start ccmexec. The most common reason for this is missing DLLs or DLL mismatch.

Either way, you first need to determine if your case is (1) or (2).

I could not able to start SMS Agent Host Service in local machine and remote machine ....!

The event log saying :

Are machines in a vmware environment? I had that Problem too and could solve it.

http://www.networksteve.com/enterprise/topic.php/SCCM_Agent_fails_periodically_when_connected_to_the_Internet./?TopicId=67843&Posts=0

no it's not a VM machines but the error exactly same....!

How to resolve it , Can you please share step by step guide

no it's not a VM machines but the error exactly same....!

How to resolve it , Can you please share step by step

Why are you starting a completely new thread for the *exact* same question (https://social.technet.microsoft.com/Forums/en-US/5a643dec-8414-4c8e-84f5-d950416e27df/sms-agent-host-service-unable-to-start?forum=configmanagerapps#afd2d6e8-c454-499c-8766-5f4675dd68a6)?

Sorry, as pointed out in the other thread, you need to help us help you by examining logs and doing some troubleshooting. We don't have crystal balls and fixing this type of issue is not magic.

Not being able to start the service is *not* an error, it's a symptom. To troubleshoot, you need to find the root cause which as mentioned is looking at the logs that Torsten pointed out in this thread and Jeff pointed out in the other thread.