Skip to content

Known Issues

Memory Usage Showing As Zero

If G-Health is reporting 0% Memory usage for a client this could be due to corrupt performance counters in Windows.

To report on memory usage the G-Health Client Service will log performance counters, and set them up on start-up. Unfortunately sometimes the base counters are corrupt so the start can't proceed.

The error in the logs:

GHealth.Client.Monitors.SystemMonitor.Services.MemoryMonitor : Error Initilizing Memory Monitor: Category 'Memory' does not exist.
GHealth.Client.Monitors.SystemMonitor.Services.MemoryMonitor : Memory monitoring has been disabled because there was a problem trying to request memory use from the windows performance counters.  This problem can be caused by a corrupt performance counter configuration.  Running 'lodctr /r' as Administrator may resolved this problem.

Option 1: A workaround is provided in repairing the Windows Performance Counters:

  1. Open an elevated command prompt (run as administrator)
  2. Rebuild the counters with the following commands:
cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

If you get the response Error: Unable to rebuild performance counter setting from system backup store, error code is 2, run the same command once more.

A successful run will say:

Info: Successfully rebuilt performance counter setting from system backup store

Pitfalls:

If you get as a return: Error: Unable to rebuild performance counter setting from system backup store, error code is 5 then your prompt was not elevated. Elevate the command prompt with administrator permissions. If the commands are successful yet symptoms persist, perform Option 2.

Option 2 :

It is possible that some providers are disabled. You can check the status with lodctr /q.

[PerfOS] Performance Counters (Disabled)
    DLL Name: %SystemRoot%\System32\perfos.dll
    Open Procedure: OpenOSObject
    Collect Procedure: CollectOSObjectData
    Close Procedure: CloseOSObject

If it says (Disabled) next to a provider, you can enable it with lodctr /e:<provider name>. Use for <provider name> the string between the [ ] at the beginning of the entry.

e.g. lodctr /e:PerfOS

G-Health Client Crashes After Starting

If this happens and in the logs you get an error saying the GngDBINET_SDK.dll file can not be found then this is likely because the Microsoft Visual C++ Redistributable files are not installed. This normally is not a problem because the G-Core installer installs these files so this would typically occur if the G-Health client is for some reason installed on a device which has no G-Core software installed.

To resolve this, download and install the Microsoft Visual C++ Redistributable files (x64). These can be downloaded from Microsoft.