PROBLEM No performance Monitoring 'counters' appear for Micro Focus servers, even though the region has been enabled for Performance Monitoring and is running. RESOLUTION 1. Check the Console log for CASAM messages: a) CASAM3017E Logged CASAM3017E will be seen in console.log if the user running Enterprise Server isn't able to update the Windows Registry Key for performance monitoring. The key is detailed in the error message, ie: 151210 15420572 9116 ESDEMO CASAM3017E ES Monitoring and Management unable to open performance registry key: " SYSTEM\CurrentControlSet\Services\Micro Focus Server\Performance ", RC=0005. M & M disabled. 15:42:05 The key is under HKLM (HKey Local Machine) To give the required access use windows 'RegEdit' to set the permissions for the above key to include the relevant user and give that user 'write' access. The user that will need this access will be the user that runs the Enterprise Server (CAS) processes. This will be the logged-on user if the command line 'casstart' is used to start the region. If the region is started from the GUI then it will be the user that MFDS is running under. (The relevant user can be checked when the region is running by looking in Windows Task Manager to see which user is running the CAS* processes for this region.) b) CASAM3014E Logged: For example: 151210 16270850 8640 ESDEMO CASAM3014E Unable to create Server Monitoring and Management shared memory. Monitoring and Management support disabled. 16:27:08 In this case the registry key HAS been correctly updated but the user doesn't have sufficient privilege to create the required Windows Global Shared memory . The ' Create Global Objects ' Policy is required for this user (see above about determining the relevant user). This can be set in the Windows 'Local Policy Editor ': Security settings -> Local Policies -> User Rights Assignment -> add the required user to this policy If either or both of the above changes were required, restart the region and again check for CASAM messages in the console.log c) CASAM3016I Logged This message mean: ES Monitoring and Management support enabled If CASAM3016I is seen in the console.log then neither of the above error messages should be seen as this means that both the registry key has been updated successfully and that the Global Memory has been written to. 2. No Performance Counters available with CASAM3016I in the Console.log If performance counters are still not visible for selection in Windows Performance Monitor but CASAM3016 is seen in the console.log, then the Windows Users need to be checked. It may be necessary to run the Windows Performance Monitor utility as a different user (in order that it can access the Global Shared memory that has been created/written to by the region). In order for Perf Mon to see the region's performance counters it has to be running as the same user that started the region , or as the Local System account. If the region is started from the command line, the Enterprise Server (CAS) processes will run as the logged-in account and when perfmon is started (in this same login session) the required access will be allowed and performance counters will be available. If the region is started from the GUI then the Enterprise Server (CAS) processes will run as the 'MFDS user' - by default this will be the Local System Account , in which case the counters should available. However if the MFDS is running under a different account (for example another local account) then the CAS processes will also run under this account and in this case PerfMon started as the logged-in user won't have access to the counters. To be able to use the peformance counters from a region started in this way, 'Perfmon.exe' will need to be started as the Local System Account (or the same account that is running the region). This can be done using the 'Sysinternals' utility "psexec" as follows: psexec –i –s perfmon psexec is part of the SysInternal PSTools suite available at: https://technet.microsoft.com/en-us/sysinternals/psexec.aspx If PerfMon is running as the correct user it should be possible to see and select the performance counters for this region when adding counters to a collection in PerfMon
↧