Back to Geneos FAQ

Why is the Netprobe not starting on a Windows Server?

There are a number of situations and reasons which mean that the Netprobe cannot start. This page discusses some of the common problems. The perfmon counters of the OS might have issues that have contributed to the Netprobe not being able to start up. To fix this issue, execute the following command via the command prompt (MS-DOS) window to rebuild the perfmon counters.

lodctr /r

If the above command still does not work, the server may need a reboot. This might be caused by Windows’ ntdll.dll library. To verify this:

  1. Run the affected Netprobe in the foreground (not as a service) Geneos - Why is the Netprobe not starting on a Windows Server? This most likely will fail.

  2. Open Windows Event Viewer

  3. Go to Windows Logs > Application

  4. Search for the log pertaining to the Netprobe process and click it

  5. On the General Tab, look for “faulting module name” parameter Geneos - Why is the Netprobe not starting on a Windows Server? Geneos - Why is the Netprobe not starting on a Windows Server? There are known cases where a server reboot fixes this. The links below provide more detail on this: Windows Service crashing, failing module ntdll.dll Microsoft Learn Corrupt NTDLL.DLL on Windows 2019 Server running on a virtual server. Microsoft Q & A

["Geneos"] ["Geneos > Netprobe"] ["FAQ"]

Was this topic helpful?