Try OpenEdge Now
skip to main content
DataServer for Microsoft SQL Server
Server Related Command Line Utilities and Startup Parameters : OpenEdge Management or OpenEdge Explorer command line utilities for the DataServer : MSSCONFIG utility


Use the MSSCONFIG utility to help you debug existing DataServer for MS SQL Server configurations defined in a properties file, such as the file. This utility displays the property settings associated with a DataServer for MS SQL Server configuration, and checks that the syntax and values are valid.
The MSSCONFIG utility runs locally, on the machine on which the AdminService is running. The utility does not run across the network.


Operating system
[-name DataServer-name]
  [-propfile path-to-properties-file ]
[-validate ]


-name DataServer-name
Specifies which existing configuration to examine. The name must match the name of an existing DataServer for MS SQL Server configuration defined in the specified properties file. If you do not specify a DataServer by name, the MSSCONFIG utility analyzes all DataServer for MS SQL Server configurations defined in the properties file specified by the -propfile parameter.
-propfile path-to-properties-file
Specifies a filename or pathname to a file that contains the property settings to be validated, for example If a filename or pathname is not specified, it defaults to the installation version of the file, such as %DLC%\properties\
Checks the syntax and values of property settings defined in the specified properties file.
Displays command line help.


*The file stores all the configuration definitions for each instance of the NameServer, AppServer, DataServer and WebSpeed Transaction Server products. Each configuration definition contains environment variables, registry entries if Windows, and property settings for each product instance. OpenEdge Management/OpenEdge Explorer and certain command line utilities such as MSSCONFIG, use this file to store, validate and manage the configurations for the products.
*The file is installed in the properties subdirectory of the OpenEdge installation directory. For example, %DLC%\properties\ in Windows.
*The file consists of a hierarchical structure of configuration entities, where parent entities provide configuration information that you can override or extend in each child entity. Each configuration entity has a name that begins the entity definition, and the definition contains configuration settings for one or more product instances.
For example, the DataServer for MS SQL Server configurations in can include:
Configuration entity name
Configuration entity function
Defines default property settings for all NameServer, AppServer, DataServer, and WebSpeed Transaction Server brokers.
Defines default property settings for all instances of DataServers for MS SQL Server.
Defines property settings for this instance of a DataServer for MS SQL Server. The file can contain several of these entities each with a unique product-instance-name.
*Parent entities provide default values for all of their child entities. For example, the parent [UBroker] contains a set of definitions that can be inherited by its child [UBroker.MS], and then again by its child [UBroker.MS.product-instance-name]. However, at any child level, a redefinition of any value supersedes the default value of its parent. All children from the redefinition level down inherit this new value.
*Optionally, you can edit the file using a text editor such as Notepad. If you want to manually edit this file to create or modify a product configuration, begin by making a backup copy from the installed file (and naming it for example, Once you edit the properties file, use the relevant validation utility such as MSSCONFIG to validate the changes and make sure there are no syntax errors or conflicts.