Enterprise Vault™ Troubleshooting Operations Manager
- About this document
- Troubleshooting the installation and configuration of Operations Manager
- Configuring Operations Manager manually
- Troubleshooting accessing Operations Manager
- Troubleshooting problems when using Operations Manager
Configuring Operations Manager manually: IIS 7 and later
The procedure is divided into three parts:
Create the EnterpriseVaultMonitoring application pool in IIS.
(For background information on creating application pools with IIS 7, see the following Microsoft article: https://technet.microsoft.com/library/cc731784.aspx)
Create the MonitoringWebApp Web application.
(For background information on creating Web applications with IIS 7, see the following Microsoft article: https://technet.microsoft.com/library/cc772042.aspx)
Complete the configuration of Operations Manager.
Perform the steps in the order described.
To create the EnterpriseVaultMonitoring application pool
- Confirm that the folder
MonitorringWebApp
is present in the Enterprise Vault installation folder, for exampleC:\Program Files\Enterprise Vault
.If the
MonitorringWebApp
folder is not present, Operations Manager has not been installed. Run the Enterprise Vault installation wizard to install the Operations Manager component, as described in the Installing and Configuring manual. - Open Internet Information Services (IIS) Manager.
- In the Connections pane, expand the server node and click Application Pools.
- On the Application Pools page, in the Actions pane, click Add Application Pool.
In the Add Application Pool dialog do as follows:
For Name, enter EnterpriseVaultMonitoring.
For .Net Framework version, select .NET Framework v4.0.30319 for Enterprise Vault 12 or .NET Framework v2.0.50727 for earlier versions of Enterprise Vault.
For Managed pipeline mode, select Classic.
Select Start application pool immediately to make sure that the application pool starts whenever the WWW service starts.
Then click OK to add the application pool.
- Right-click the newly created application pool and select Advanced Settings.
- In the Process Model settings, in Identity, specify the user name and password for the monitoring user.
- Click OK to close the Advanced Settings dialog.
To create the MonitoringWebApp Web application
- In the Connections pane of IIS Manager, expand the Sites node.
- Right-click the Default Web Site and click Add Application.
In the Add Application dialog, do as follows:
In the Alias box, enter a value for the application URL, such as MonitoringWebApp.
For the Application pool, click Select and select EnterpriseVaultMonitoring from the drop-down list, and click OK.
For Physical path, you must specify the physical path of the application's folder. To specify the path, browse to the
monitoringwebapp
folder, for exampleC:\Program Files\Enterprise Vault\monitoringwebapp
and click OK.Optionally, click Test Settings to verify the settings that you specified.
Click OK to close the dialog.
- With Features View selected, open Default Document and remove all the pre-existing entries except default.aspx.
- Select the MonitoringWebApp Web application and with Features View selected, open Authentication.
- Enable Windows Authentication and ASP.NET Impersonation, and disable Anonymous Authentication.
To complete the configuration of Operations Manager
- Add the monitoring user to the IIS_IUSRS local group.
- Give read permission to the monitoring user for the following Registry 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
- Give read permission to the monitoring user on the
MonitoringWebApp
folder in the Enterprise Vault installation folder. - Give read and write permissions to the monitoring user on the
Logs
subfolder of theMonitoringWebApp
folder. - Give read, write, and execute permissions to the monitoring user on the folder
C:\WINDOWS\Microsoft.NET\Framework\version\Temporary ASP.NET Files
where version is v4.0.30319 for Enterprise Vault 12 or v2.0.50727 for earlier versions of Enterprise Vault. - Note the site ID of the computer on which you are configuring Operations Manager. The site ID can be obtained from the SiteID value of the following Registry 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
- Open SQL Server Enterprise Manager and browse to the EnterpriseVaultDirectory database. Select Tables and locate the table MonitoringSettings. Right-click MonitoringSettings and select Open Table > Return all rows.
- Locate the row with the SiteEntryID that matches your Site ID.
- Update the MonitoringUser column with the domain and user name of the monitoring user, in the format
domain\username
. - Update the SiteAddress column with the address of your Web server. For example, if you have configured MonitoringWebApp on the server blackbird, the URL takes the form:
http://blackbird/monitoringwebapp/default.aspx
- Close the table.
- Restart the IIS Admin Service.
- Browse to http://localhost/monitoringwebapp/default.aspx, and confirm that you can now view Operations Manager.