Please enter search query.
Search <book_title>...
Enterprise Vault™ Troubleshooting Operations Manager
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)
- About this document
- Troubleshooting the installation and configuration of Operations Manager
- About troubleshooting the installation and configuration of Operations Manager
- Troubleshooting the installation and configuration of Operations Manager
- Determining whether Operations Manager is installed and configured successfully
- Running the Operations Manager Configuration utility
- Configuring Operations Manager manually
- Troubleshooting accessing Operations Manager
- About troubleshooting accessing Operations Manager
- Troubleshooting accessing Operations Manager
- Authentication failure and access denied message
- Parser error: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"
- Changing the port for accessing the Monitoring database
- Checking the Monitoring Agent and Middle Tier executables
- Troubleshooting problems when using Operations Manager
Checking the Monitoring Agent and Middle Tier executables
The Enterprise Vault Admin service attempts to spawn the Monitoring Agent and Monitoring Middle Tier executables up to three times. If the Admin service fails to start these executables you need to investigate why.
To check the Monitoring Agent and Middle Tier executables
- Right-click an empty space on the Windows task bar, and then click Task Manager.
- Click Task Manager's Properties tab.
- Check whether
MonitoringAgent.exeandMonitoringMiddleTier.exeare running. If they are, continue with the next diagnostic step to troubleshoot accessing an installed Operations Manager. See Troubleshooting accessing Operations Manager. If you cannot see these programs listed in Task Manager, continue with the following. - Examine the application event logs for entries logged by the .NET runtime process around the time that the Admin service started, for indications as to why
MonitoringAgent.exeandMonitoringMiddleTier.exedid not start. - If you cannot find any entries in the event logs, run DTrace on
adminservice.exe, restart the Admin service, and then search the DTrace logs for entries from the function StartProcessesInList(). This gives you a specific Windows error code that indicates why the launch of the executables failed.For details of how to use DTrace, see the Enterprise Vault Utilities manual.
After rectifying the problem, restart the Admin service and then repeat steps 1 to 3 to confirm that both executables are now running.