Greetings.I am banging my head for a while now, and I haven't found an answer to my problem. The situation is like this:- I have a SCCM 2007 environment in mixed mode- different clients and servers- on Windows 2008 x64 servers I can install client, but on restart the client is stopped. In logs I can see the service starts but after few seconds it stops without any error whatsoever. The log entry reads: The SMS Agent Host service was successfully sent a stop control.This happens only on x64 servers (2003 and 2008). I have already tried to reinstall clent, first cleaned it with ccmclean.If I manually start the client after logon it works flawlessly without errors until reboot.Any help is greatly appreciated.Peter Sarf

I Presume the Log Entry The SMS Agent Host service was successfully sent a stop control is from the application Event Log.Please Check the ccmexec.log on that client in the Windows\SYSWOW64\CCM\Logs directory. Please check for errors there whichmight explain why theAgent Host service Stopped..

Thank you, for your reply. I have already checked ccmexec.log and found some errors. Googled for them, but found no reasonable answer. The errrors are:WM_QUIT received in the main message loop.CcmExec28.7.2009 22:44:324080 (0x0FF0)Shutting down CCMEXEC...CcmExec28.7.2009 22:44:324080 (0x0FF0)BEGIN ExecuteSystemTasks('PreShutdown')CcmExec28.7.2009 22:44:324976 (0x1370)Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)CcmExec28.7.2009 22:44:324976 (0x1370)Could not connect to machine policy WMI namespace to get service settings.CcmExec28.7.2009 22:44:324976 (0x1370)END ExecuteSystemTasks('PreShutdown')CcmExec28.7.2009 22:44:324976 (0x1370)BEGIN ExecuteSystemTasks('Shutdown')CcmExec28.7.2009 22:44:324976 (0x1370)Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)CcmExec28.7.2009 22:44:324976 (0x1370)Could not connect to machine policy WMI namespace to get service settings.CcmExec28.7.2009 22:44:324976 (0x1370)END ExecuteSystemTasks('Shutdown')CcmExec28.7.2009 22:44:324976 (0x1370)CUpdatesAgent::FinalRelease enteredCcmExec28.7.2009 22:44:324080 (0x0FF0)RebootCoordinator::FinalRelease enteredCcmExec28.7.2009 22:44:324080 (0x0FF0)ServiceWindowManager::FinalRelease enteredCcmExec28.7.2009 22:44:324080 (0x0FF0)ServiceWindowManager::FinalRelease enteredCcmExec28.7.2009 22:44:324080 (0x0FF0)Waiting up to 2 seconds for active tasks to complete...CcmExec28.7.2009 22:44:324080 (0x0FF0)Error waiting for tasks (0x80040213), will shut down anyway.CcmExec28.7.2009 22:44:344080 (0x0FF0)Finished shutting down CCMEXEC.CcmExec28.7.2009 22:44:344080 (0x0FF0)Starting CCMEXEC service...CcmExec28.7.2009 22:45:462076 (0x081C)Then after a whileWM_QUIT received in the main message loop.CcmExec28.7.2009 22:47:472076 (0x081C)Shutting down CCMEXEC...CcmExec28.7.2009 22:47:472076 (0x081C)UninitCommandExec failed (0x800401fb).CcmExec28.7.2009 22:47:472076 (0x081C)Waiting up to 2 seconds for active tasks to complete...CcmExec28.7.2009 22:47:472076 (0x081C)Finished shutting down CCMEXEC.CcmExec28.7.2009 22:47:472076 (0x081C)Starting CCMEXEC service...CcmExec28.7.2009 22:52:17248 (0x00F8)For this error I found, that it is nothing to worry about:Error registering hosted class '{E67DBF56-96CA-4e11-83A5-5DEC8BD02EA8}'. Code 0x80040154CCMEXEC28.7.2009 22:52:263408 (0x0D50)Invoking system task 'UpdatesDeploymentStartupTask'.CcmExec28.7.2009 22:52:343152 (0x0C50)Invoking system task 'SMSSHA_Startup'.CcmExec28.7.2009 22:52:353560 (0x0DE8)System task 'SMSSHA_Startup' returned error code 0x80070005.CcmExec28.7.2009 22:52:363560 (0x0DE8)Invoking system task 'DCMAgent_Startup'.CcmExec28.7.2009 22:52:363152 (0x0C50)END ExecuteSystemTasks('Startup')CcmExec28.7.2009 22:52:363068 (0x0BFC)And finally:CancelTask failed with error 80040215CcmExec28.7.2009 22:54:062976 (0x0BA0)If anyone has any ideas they are welcome. If it is neccessary I can post full logs.Regards,Peter Sarf

I've seen that once on a workstation and was not able to find the cause (repairing WMI, reinstalling client, permissions, GPOs, DCOM, etc). So I rebuilt that machine. You're talking about a server so you might consider calling CSS.

Well, I am talking about quite a few servers, including 4 Exchange servers, SQL, OCS, Sharepoint... which I cannot easily rebuild.This is not a good news to me. But thank you for your post. If I cannot find the answer this week, I will call CSS.Regards,Peter Sarf

Do you have any "Host Intrusion" type services installed on those servers? Something like that, or some other anti-malware service might be interfering.Standardize. Simplify. Automate.

I have heard things like that. I think that Symantec Antivirus was an issue. Only TrendMicro Antivirus solution is installed. I am going to try and disable (uninstall) it and reboot one of servers.I'll report the results.Regards,Peter Sarf

f.y.i I saw this problem today on a lab server, and it was after i had done a server reboot, the first thing i noticed was site status was red... log reading told me the MP_control_manager was reporting problems with starting Severity Type Site code Date / Time System Component Message ID Description Error Milestone WDN 8/3/2009 9:43:01 AM WIN-CILZXI45G1Q SMS_MP_CONTROL_MANAGER 5436 MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error. Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. so i checked http ://server:80/SMS_MP/.sms_aut?MPCERT and there was nothing, i looked in my event viewer and in the system log there were many Distributed COM errors which only seemed to have occured since the server was rebooted on August 2nd, they all read The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {D9B257A6-C7FC-4B76-9824-599466B69D3B} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool. further browsing through the event log showed me that just before all these errors and directly after the server reboot there was this A timeout was reached (30000 milliseconds) while waiting for the SMS Agent Host service to connect. and The SMS Agent Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. manually starting the SMS Agent service has resolved all the issues listed above, now... the question is why it failed to start after the reboot (i only rebooted because the latest windows updates required it..) server os is windows server 2008 sp1 x64, sccm 2007sp1r2 this server has symantec av software installed, did you see any difference on that server after you removed that software ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Hi Niall.No, I do not have any of your events. The only event in my logs is The SMS Agent service entered the stopped state.The AV installed is TrendMicro and uninstall didn't resolve this error.FYI, I have read over the forums that Symantec cause problems with client. Uninstall worked for most people.Regards,Peter Sarf

I believe I have found the answer. It seems that dependent services were not all up and running at the time SMS service started. On Server 2008 I have set the startup type as Automatic (Delayed Start) and now it seems it is working. For Server 2003 servers I will try to set dependency through registry on last started service, so the SMS service will start last.Thank you all for your help.Regards,Peter Sarf

Dear Peter Sharaf, Would you please let me know in registry what value and where to change, to make the SMS agent service to start at last. I am facing the same problem in all SMS clients that have been approved. Client side firewall is enabled, so client installation through "Client Push" does not take place.If you can give some suggestion to excempt some posts for Client installation to take place with APPROVED STATE, it will be most welcome. For the client to get approved, I have gone through some docs stating the "RPC and WMI communication" to client require posts 1024 to 5000 to be excempted. Can you please let me know the procedure for the same, across the domain. Expecting reply from any one.