Search <book_title>...

Enterprise Vault™ Troubleshooting the Monitoring Database and Agents

Last Published: 2021-03-23

Product(s): Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2, 12.1, 12.0, 11.0.1, 11.0)

Creating a Monitoring database manually

Run the Monitoring Configuration Utility with the /create option to create the Monitoring database for an Enterprise Vault Directory.

To create a Monitoring database manually

Open a command prompt window on the Enterprise Vault server and navigate to the Enterprise Vault installation folder.

Enter the following command on a single line:

MonitoringConfigUtility /create DirectoryDB_SQLServer MonitoringDB_SQLServer Start_Immediately Vault_Version SiteEntryId SQL_DataFileFolder SQL_LogFileFolder LogFile

where the variables are as follows:

*DirectoryDB_SQLServer*	The SQL server where the Directory database is located.
*MonitoringDB_SQLServer*	The SQL server on which to locate the Monitoring database.
*Start_Immediately*	Whether monitoring is to start immediately on the Enterprise Vault server. Use a value of 1 (start immediately) or 0 (do not start immediately).
*Vault_Version*	The installed version of Enterprise Vault. See the Notes for information on how to identify this variable.
*SiteEntryId*	The Site Entry Id for the new site in the Directory database. See the Notes for information on how to identify this variable.
*SQL_DataFileFolder*	The location of an existing folder on the Monitoring database SQL server in which to create the SQL data files for the Monitoring database. Note that the folder must already exist. If you specified a SQL server on a remote computer, the location must be a valid path on the remote computer. If the path contains spaces, enclose it in quotes.
*SQL_LogFileFolder*	The location of an existing folder on the Monitoring database SQL server in which to create the SQL log file for the Monitoring database. Note that the folder must already exist. If you specified a SQL server on a remote computer, the location must be a valid path on the remote computer. If the path contains spaces, enclose it in quotes.
*LogFile*	The name to give the error log file.

Notes:

To identify the Enterprise Vault version, right-click on any Enterprise Vault binary file, such as MonitoringConfigUtility.exe, and select Properties. The Version tab lists the file version, for example 9.0.3.1164.
To identify the Site Entry Id, start the Registry Editor and navigate to the following key:
On a 32-bit installation of Windows:
```
HKEY_LOCAL_MACHINE
\SOFTWARE
 \KVS
  \Enterprise Vault
```
On a 64-bit installation of Windows:
```
HKEY_LOCAL_MACHINE
\SOFTWARE
 \WOW6432Node
  \KVS
   \Enterprise Vault
```
Note the value of the SiteID subkey.
Do not specify the root of a file system such as C:or D:as the location for the SQL data or log file folder.

The following example shows a command to create a Monitoring database:

MonitoringConfigUtility /create DataServer4 DataServer4 1
9.0.3.1164
1579A0FB3CA3B400C5741d100abcd.EVDOMAIN.mycompany.com
"C:\Program Files\Microsoft SQL Server\MSSQL\Data"
"C:\Program Files\Microsoft SQL Server\MSSQL\Log"
monconfigutil.log

This command specifies the following values:

The Directory database is located on SQL server DataServer4.
You want to locate the Monitoring database on DataServer4.
Monitoring is to start immediately.
The Enterprise Vault version is 9.0.3.1164
The site entry ID for the new Enterprise Vault site is 1579A0FB3CA3B400C5741d100abcd.EVDOMAIN.mycompany.com
The path to the SQL data file folder is C:\Program Files\Microsoft SQL Server\MSSQL\Data
The path to the SQL log file folder is C:\Program Files\Microsoft SQL Server\MSSQL\Log
The file name for the Monitoring Configuration Utility log is monconfigutil.log