Stopping site services preinst.exe /stopsite
I am trying to move the SCCM database. However, when I try to do the preinst.exe /stopsite command, I get an error that the site component manager is not responding. All of the sccm services are currently started and have no errors. I get about 12 messages of "Waiting for the Site Component Manager to respond", then the command fails with "The Site Component Manager is not responding". I'm not sure if there is another way to stop the site services???
July 30th, 2010 8:53pm

You cna just stop the SMS_executive service, sms agent host and the site component manager service from the services snap-inKent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2010 9:05pm

You will have to stop SMS reporting,SMS SQL monitor as well.___________________________________________________________ Shimbesh
July 30th, 2010 9:13pm

Hi, preinst.exe /stopsite is used to stop all SCCM related service, you can still manually stop these services in service snap-in by running "services.msc"Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2010 6:41am

Well, after rebooting all of our SCCM servers, along with our SQL server, I tried the preinst.exe /stopsite command again. This time, it appeared to be working as I could see all of the services stopping. After a couple of minutes, it failed on the "Failed to stop the SQL Monitor service" error, then the next line was "Failed to stop all services". I looked on all or our servers, but couldn't find the SQL Monitor service. In addition, some of the services were in a "stopping" mode and never actually went to a stopped state. However, I tried the /stopsite command again, the message was "site already stopped", even though the previous message was "failed to stop all services". I'm wondering how concerned I should be if all of the services won't even shut down properly. I rebooted all of the servers (again), tried to stop the site and got the "Waiting for the site component manager to respond" error (again). So, it seems as if something in our environment isn't quite right if I can't even get some of the main services to stop properly. I don't want to modify the configuration and risk more problems, even though this isn't our production environment we are trying to change. I'm just trying to go from a single SQL database to using a SQL cluster.
August 2nd, 2010 2:48pm

Is there a service called SMS_SQL_MONITOR? That service was needed back with SMS 2003, but is now no longer required and can be removed: http://technet.microsoft.com/en-us/library/cc872792.aspx
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2010 3:12pm

No, we can't find any service called SMS_SQL_MONITOR. We were always at Config Mgr. 2007 - we never had an SMS environment that we upgraded from. We are at the latest release of SCCM as well.
August 2nd, 2010 3:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics