I am trying to stop a site to troubleshoot a certain issue. I ran preinst.exe /STOPSITE on one of the secondary sites which executed to completion in matter of few minutes. When I ran the command on the central site, the components are stopping one at a time but it's been 30 minutes and the process is still going on. Each component is taking around 3-4 minutes to stop. I dont think I have seen this before. Comments? Thanks.Mayur

Hi, That's no unsual, I have seen it take that long a few times. Do the components stop or timeout?Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Thanks Kent. The components did stop. It did tell me some components could not be stopped but I felt lazy to look for them. I think there's something seriously wrong with the site. I have a similar experience with another site I managed before. The reason why I restarted the components was because compmon.log kept complainting that it could not get the current execution state for component because it's in an unknown state. There were few other abnormal behaviors on the site (no events in the event viewer, one of the collections showed an hourglass and did not update at all etc.). Stopping and starting the site did not fix this error in compmon.log. Which is when I restarted the server. ConfigMgr reinstalled all components after the restart! It sill does not make any sense why it took more than 30 minutes to stop the components on the central site. Mayur

It can take quite some time until all threads are stopped. That depends on how busy the site is. There's a hotfix for that. I am not 100% sure of it's http://support.microsoft.com/kb/982399/en-us, but I am sure that others will chime in here.