False negative returned from WMI monitors

Have your NT Service or WMI Active Monitors been reporting errors when in fact your services or counters are up? You may need to increase the default length of the RPCPingTimeout registry value so that you are given a longer chance to connect. For example, if you wish to set the timeout to 10 seconds, set RCPingTimeout to 10000 (decimal).

To edit the RPCPingTimout registry value:

  1. Go to Start > Run > Regedit.exe
  2. From the Registry Editor go to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Ipswitch\Network Monitor\WhatsUp Engine\Settings
  3. Within the Settings folder, select RPCPingTimeout and right-click. From the right-click menu, select Modify.
  4. In the Edit DWORD Value dialog, enter in a new value for the timeout and click OK.

Important: The default timeout is 5 seconds, expressed as 5000 (decimal), or 0x00001388 (hexadecimal). We strongly recommend that you do not exceed a timeout of 30 seconds.

After making any changes to the registry, you need to restart the Polling Engine.

To restart the Polling Engine from the web:

  1. Click the Admin tab, then click Admin Panel.
  2. Select Polling Engine and click Restart.

To restart the Polling Engine from the WhatsUp Gold server console:

  1. Click Start > All Programs > Ipswitch WhatsUp Gold > Utilities.
  2. Click Service Manager.
  3. Select Polling Engine and click Restart.

See Also

Troubleshooting and Maintenance

Troubleshooting your network

Maintaining the Database

Group Policy Object 503 Service Unavailable Error

Recovering from a "Version Mismatch" error

Task Tray Application fails on Windows Vista

Co-located SQL Server and WhatsUp Gold server clocks must be synchronized

Connecting to a remote desktop

WhatsUp Gold engine message

Troubleshooting SNMP and WMI connections

Re-enabling the Telnet protocol handler

Passive Monitor payload limitation

Receiving entries in the SNMP Trap Log

Recommended SMS modems and troubleshooting tips

Troubleshooting IIS configuration

Uninstalling Ipswitch WhatsUp Gold

Troubleshooting the WhatsUp Health Threshold