Enterprise Vault™ Troubleshooting Operations Manager

To troubleshoot accessing Operations Manager

1. If, when you attempt to access Operations Manager, you are asked to authenticate three times and receive an "access denied" message, refer to the Microsoft support article in the following section

   See Authentication failure and access denied message.

2. If you enable or disable the Windows policy setting for FIPS-compliant algorithms on a computer on which Operations Manager is configured, you must then re-run the Operations Manager Configuration utility. Otherwise when you subsequently run Operations Manager, the Web browser displays a parser error message stating that the implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

   See Parser error: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms".

3. Check whether port 8071 is used by a program other than the Enterprise Vault MonitoringMiddleTier.exe program. If another program uses this port, the Operations Manager Web application will not appear. You can check whether a port is in use by running the following command from a command prompt window:

   netstat -b

   If required, you can change the port that MonitoringMiddleTier.exe uses. See Changing the port for accessing the Monitoring database.

4. Check whether the Monitoring Agent and Monitoring Middle Tier executables are running. See Checking the Monitoring Agent and Middle Tier executables.
5. Confirm that the prerequisites for Operations Manager are satisfied, as described in the Installing and Configuring manual.
6. If you are running Operations Manager on a 64-bit computer, make sure that you have switched to the 32-bit version of ASP.NET, as described in the Installing and Configuring manual.
7. Confirm that IIS is not locked down.
8. Check that the IIS_WPG group (for IIS 6) or the IIS_IUSRS group (IIS 7) has read/write access onto the folder <EVInstall_path>\MonitoringWebApp\Logs, where <EVInstall_path> is the location of the EV installation folder, for example C:\Program Files\Enterprise Vault.
9. Check that the identity for the EnterpriseVaultMonitoring application pool is set to the MonitoringUser Windows user account you created for Operations Manager to use.

10. Ensure that the MonitoringUser account is a member of the following group in Active Directory:

    • For IIS 6, the IIS_WPG group

    • For IIS 7, the IIS_IUSRS group

11. This step apples to IIS 6 only. For IIS 7, go to the next step.

    From the Windows Start menu select Control Panel > Administrative Tools > Internet Information Services Manager and check that the properties of the MonitoringWebApp website are as follows:

    • The ASP.NET version on the ASP.NET property tab is set to 2.*

    • The application pool is set to EnterpriseVaultMonitoring.

    • For authentication, Integrated Windows authentication is selected.

12. This step apples to IIS 7 only.

    From the Windows Start menu select Control Panel > Administrative Tools > Internet Information Services Manager, and do as follows:

    • Check in the Advanced Settings of the MonitoringWebApp website that the application pool is set to EnterpriseVaultMonitoring.

    • Check in the Basic Settings of the application pool EnterpriseVaultMonitoring, that the .NET Framework version is set to v4.* for Enterprise Vault 12 or v2.* for earlier versions of Enterprise Vault.

    • Open the Authentication page in the Features View of the MonitoringWebApp site. Make sure that the status of Windows authentication is Enabled