At times, you may wish to stop services via custom scripts. You can successfully script the stopping and restarting of MetaCommunications services to accommodate your needs.
USING "NET STOP" TO STOP SERVICES
The Windows "net stop" command can be used to stop one or multiple services. The usage would be:
- net stop <service_name>
RECOMMENDED ORDER FOR STOPPING SERVICES
When stopping services, you will want to do so in the following order:
- MetaCommunications Services Watcher (If not stopped first, this will attempt to restart other MetaCommunications Services)
- MetaCommunications File System Service (an InterSync component)
- MetaCommunications MetaData Service (an InterSync component)
- MetaCommunications Update Service (technically, this can be stopped at any time, as it is only used to upgrade Virtual Ticket desktop clients for Windows)
- MetaCommunications Application Server
ANY REMAINING NON-METACOMMUNICATIONS SERVICES
- Microsoft IIS-Related Services (If using Workgroups Portal (Approval Manager and/or Job Manager), or Image Portal). See below for additional details.
- Microsoft SQL Server Related Services (If you have multiple instances and/or versions of MS SQL Server installed, take care only to stop the instances you need to stop for your purposes)
MICROSOFT IIS-RELATED SERVICES TO STOP
Ensure that the following IIS-related services are stopped if you use Workgroups Portal (Approval Manager and/or Job Manager) or Image Portal:
- IIS Admin Service
- World Wide Web Publishing Service
- ASP.net Service
If the MetaCommunications Application Server (or any other service including SQL SERVER service) does not stop after ?net stop? within roughly 10 minutes, we recommend you then kill their executables with PsKill.
The following Microsoft Technet article may be of assistance: http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx