Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > ipMonitor > Resolve internal errors from the SQL Server and Exchange Server Monitors

Resolve internal errors from the SQL Server and Exchange Server Monitors

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 57 Votes: 0 Revisions: 7

The Exchange Server and SQL Server Monitors are designed to monitor performance counters of the server and the respective application. In order to do so, ipMonitor performs a series of WMI queries over RPC to retrieve the selected performance counter values.

Having said that, here's what ipMonitor requires to complete these tests:

1. The ipMonitorSrv service must run under a Windows account which is allowed to impersonate.

-In order find out what account it is using, simply run the ipMonitor Configuration program (\ipMonitor8\ipm8config.exe) and click the "Service Settings" option.

-In order to ensure that this account has the needed privileges, simply proceed with the following:

a. Open "Administrative Tools -> Local Security Policies".
b. Branch open "Security Settings -> Local Policies -> User Rights Assignment".
c. Ensure the Windows account assigned to the ipMonitorSrv service is explicitly listed within the following policies:

->Act as part of the operating system
->Bypass traverse checking
->Log on as a Service
->Replace a process level token

After modifying any of these settings, you must refresh the applied Local Security Policy settings.

To refresh the applied Local Security Policy settings in Windows XP, Server 2003, and Vista

1. Open a command prompt.
2. Run the following command:

gpupdate /target:computer /force

3. Verify in the Application Event log that the new settings were correctly applied. If an error was encounted, it will be recorded here.
4. Restart the ipmonitorsrv service.

To refresh the applied Local Security Policy Settings in Windows 2000
1. Open a command prompt.
2. Run the following command:

secedit /refreshpolicy user_policy /enforce

3. Verify in the Application Event log that the new settings were correctly applied. If an error was encounted, it will be recorded here.
4. Restart the ipmonitorsrv service.


2. The Credential assigned to the Exchange Server or SQL Server Monitor must be pointing to a Windows Account that exists on the ipMonitor system (.\account) or the domain it is a member of (domain\account). This account must also be a member of the "Administrators" group on the Exchange or SQL server and must NOT be the same account as the one assigned to the ipMonitorSrv service.

3. An RPC connection must be possible from the ipMonitor 8 system to the Exchange system. In order to test this, try going to \\ExchangeSrv\c$\ from the ipMonitor system.

Last modified

Tags

Classifications

Public