Feedback
Did this article resolve your question/issue?

   

Article

What are WMIC messages in the admserv.log file

« Go Back

Information

 
TitleWhat are WMIC messages in the admserv.log file
URL NameWhat-are-WMIC-messages-in-the-admserv-log-000096842
Article Number000113107
EnvironmentProduct: OpenEdge Management
Version: 11.6 and later
OS: Windows
Question/Problem Description
What are WMIC messages in the admserv.log file
Steps to Reproduce
Clarifying Information
Error Message[osmetrics] * wmic failed to terminate after 15010 milliseconds. destroy() will be called for this process. This may indicate a problem with Windows performance counters.
Command: wmic Process where (Processid=10460 or Processid=6836) get CommandLine,CreationDate,ExecutablePath,KernelModeTime,MinimumWorkingSetSize,ParentProcessId,Processid,UserModeTime,WorkingSetsize
Defect/Enhancement Number
Cause
Resolution
In OpenEdge 11.6 the method of retrieving metric values for OS resources was changed from a JNI implementation to WMIC. The "WMIC" stands for Windows Management Instrumentation Command-line. These messages are simply recording the command line that was running and the exception or timeout that was reached which failed.

Additionally, the osmetrics code for Windows which accessed the Windows registry entries was completely replaced by a combination of standard java/WMIC calls in OpenEdge 11.6. As a result, osmetrics (on Windows only) no longer accesses the registry entries and this conflict no longer occurs when another Service uses performance counters.

For example, In Windows OEM uses "wmic <pid>" call terminate command, on other platforms it uses osmetrics

For example: The timeout messages would be related to a time that the Adminserver is not reachable, there's usually a pre-ceeding message in the admserv.log
Error registering with Admin Server. (8845)

The command syntax listed in these WMIC admserv.log messages can be useful to further diagnose issues on the system at the time. 
For example:
  • you could find the Processid numbers referred in the Task Manager
  • you could run precisely the "Command" information recorded from a command prompt:
wmic Process where (Processid=10460 or Processid=6836) 
get CommandLine,CreationDate,ExecutablePath,KernelModeTime,MinimumWorkingSetSize,ParentProcessId,Processid,UserModeTime,WorkingSetsize



 
Workaround
Notes
Last Modified Date6/14/2019 12:55 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.