10.3 and 3.1 OpenEdge Explorer Shows No Resources
Problem
Today, OpenEdge Explorer shows no resources. It worked before and then stopped working.
Solution
Progress Technical Support gave us the following solution:
OpenEdge Explorer gets its Resource Information by using Microsoft performance counters and their libraries in Windows.
Microsoft performance counters depend on a pdh.dll.
For 64-bit installation of OpenEdge on Windows 64-bit the pdh.dll file should be placed in C:\Windows\System32\
For 32-bit installation of OpenEdge on Windows 64-bit the pdh.dll file should be placed in C:\Windows\SysWOW64\
For 32-bit installation of OpenEdge on Windows 32-bit the pdh.dll file should be placed in C:\Windows\System32\
The above problem is caused by the fact that either the pdh.dll file is missing, corrupted or an issue with the related Microsoft performance counters that may be missing or do not contain counter data.
The base set of performance counter libraries may become corrupted and may need to be rebuilt. Additionally, any custom (.NET Framework application created) counters or any extensible counters may need to be rebuilt.
This behavior may occur if certain extensible counters corrupt the registry, or if certain Windows Management Instrumentation (WMI)-based programs modify the registry.
In this case, the pdh.dll file did exist on the customer's machine. Since they have installed 32 bit OpenEdge, the \system32 folder is where it needed to be. Therefore, we performed the 'rebuild' steps in
https://progress.my.salesforce.com/articles/Article/P158938.
Rebuild the Microsoft performance counters, running the following command directly (DOS prompt is required to be Opened as 'Run as Administrator') within the folder where the pdh.dll is located (system32):
$ lodctr /R
Some performance counters may be disabled, run the following command to identify those counters:
$ lodctr /q
Run the following command for each of the disabled counters:
$ lodctr /e:
After restarting the AdminService, OpenEdge showed all resources correctly. Customer tested a server restart and everything came up correctly.