MSSMAN utility
- Last Updated: February 11, 2026
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
Use the MSSMAN utility to control the operation of a configured DataServer for MS SQL Server. The utility allows you to start a broker, query its status, start and stop additional DataServer servers, and shut down the broker.
Syntax
| Operating system | Syntax |
|---|---|
| Windows |
|
Parameters
- -name DataServer-name
- Specifies the name of a broker. This parameter is required.
- -kill
- Stops and removes the DataServer broker from memory, no matter what it is doing.
- -start
- Starts the DataServer broker.
- -stop
- Tells the DataServer broker to stop itself.
- -query
- Queries the DataServer brokers and servers for status.
- -host host-name
- Specifies the name of the machine where the AdminService is running. If a host name is not specified, it defaults to the local host name.
- -user user-name
- Specifies a user name and prompts for a password. A user name
and password are required only when you use the
-hostparameter and specify a remote host name. If you specify a remote host name with the-hostparameter, but do not specify a user name with the-userparameter, you receive a prompt for a username and password. - -port port-number
- Specifies the port number of the machine on which the AdminService is running. If a port number is not specified, it defaults to 20931.
- -help
- Displays command line help.
Notes
When you specify a user name with the -user parameter, Windows supports
three different formats:
- A user name as a simple
text string, such as "
mary," implies a local user whose user account is defined on the local Windows server machine, which is the same machine that runs the AdminService. - A user name as an explicit local user name, in which the user
account is defined on the same machine that runs the AdminService
except the user name explicitly references the local machine domain,
for example "
.\mary". - A user name as a user account on a specific Windows domain. The general format is Domain\User, in which the User is a valid user account defined within the domain and the Domain is any valid Windows Server, including the one where the AdminService is running.