In Unit Platform, the monitoring checks can fail if the WMI repository does not return the correct information or returns an error. This article presents some alternatives to correct this problem.<\/p>\n
IMPORTANT:<\/strong> follow the instructions below at your own risk. Some procedures listed here may cause some systems to fail. If you are not sure what to do, contact Microsoft and ask for instructions.<\/em><\/p><\/blockquote>\n
Note: to execute the commands below, it’s necessary to have access to a command prompt (cmd.exe) with administrator privileges.<\/p>\n
Restart the server<\/h2>\n
Sometimes the solution to the problem is a simple reboot. It’s not guaranteed, but this is the easiest alternative and it has a low risk of causing problems.<\/p>\n
Restart the WMI service<\/h2>\n
It’s recommended to restart the server, but if this is not possible, you can try to restart only the WMI service:<\/p>\n
net stop winmgmt \/y\r\nnet start winmgmt<\/pre>\nWMI diagnostics (WMIdiag)<\/h2>\n
To detect WMI repository inconsistencies, there is the WMIdiag tool, created by Microsoft, that analyses the system and points out any configuration errors:<\/p>\n
Click here to download WMIdiag.<\/a><\/p>\n
To learn how to use it, read this article.<\/a><\/p>\n
Update the performance counters<\/h2>\n
This alternative requires the use of the command\u00a0 wmiadap<\/a> to force the update of the performance counters.<\/p>\n
The parameter \/f parses all the performance libraries on the system and refreshes the classes derived from Win32_PerfRawData and Win32_PerfFormattedData.<\/p>\n
wmiadap \/f<\/pre>\nThe parameter \/r parses all the Windows Driver Model drivers on the system to create performance objects.<\/p>\n
wmiadap \/r<\/pre>\nResyncronize the performance counters<\/h2>\n
Another way to try to recover corrupted performance counters is to use the command winmgmt<\/a>. For that, execute the following commands:<\/p>\n
# When Windows version is older than 2003, execute this command to clear previous resync attempts\r\n# In systems newer than 2003 this command won't work\r\nwinmgmt \/clearadap\r\n\r\n# resync the counters\r\nwinmgmt \/resyncperf\r\n<\/pre>\nReload the performance counters<\/h2>\n
According to this Technet article<\/a>, in the case the counters were not installed properly or with the wrong permissions, this command can be used to solve the problem:<\/p>\n
lodctr \/r<\/pre>\nRebuild the WMI repository<\/h2>\n
One of the last options is to restore the WMI to its original state. To rebuild the WMI repository, use the commands below (Windows Vista or newer).<\/p>\n
IMPORTANT:<\/strong> if your system has third party softwares that use the WMI, this command can cause these softwares to break and require a reinstall. Use the commands below at your own risk.<\/em><\/p><\/blockquote>\n
net stop winmgmt \/y\r\nWinmgmt \/resetrepository\r\nnet start winmgmt<\/pre>\nTo learn more about these commands, click here<\/a>.<\/p>\n
Update Windows<\/h2>\n
Check if there is an update related to WMI that hasn’t been installed. Hotfixes like this<\/a> can be available for your system.<\/p>\n
Third party counters<\/h2>\n
Some applications create their own counters. If that is the case, try reinstalling the software or contact the manufacturer to obtain instructions on how to proceed.<\/p>\n","protected":false,"raw":"In Unit Platform, the monitoring checks can fail if the WMI repository does not return the correct information or returns an error. This article presents some alternatives to correct this problem.\r\n
IMPORTANT:<\/strong> follow the instructions below at your own risk. Some procedures listed here may cause some systems to fail. If you are not sure what to do, contact Microsoft and ask for instructions.<\/em><\/blockquote>\r\nNote: to execute the commands below, it's necessary to have access to a command prompt (cmd.exe) with administrator privileges.\r\nRestart the server<\/h2>\r\nSometimes the solution to the problem is a simple reboot. It's not guaranteed, but this is the easiest alternative and it has a low risk of causing problems.\r\n
Restart the WMI service<\/h2>\r\nIt's recommended to restart the server, but if this is not possible, you can try to restart only the WMI service:\r\n
net stop winmgmt \/y\r\nnet start winmgmt<\/pre>\r\nWMI diagnostics (WMIdiag)<\/h2>\r\nTo detect WMI repository inconsistencies, there is the WMIdiag tool, created by Microsoft, that analyses the system and points out any configuration errors:\r\n\r\nClick here to download WMIdiag.<\/a>\r\n\r\nTo learn how to use it, read this article.<\/a>\r\n
Update the performance counters<\/h2>\r\nThis alternative requires the use of the command\u00a0 wmiadap<\/a> to force the update of the performance counters.\r\n\r\nThe parameter \/f parses all the performance libraries on the system and refreshes the classes derived from Win32_PerfRawData and Win32_PerfFormattedData.\r\n
wmiadap \/f<\/pre>\r\nThe parameter \/r parses all the Windows Driver Model drivers on the system to create performance objects.\r\nwmiadap \/r<\/pre>\r\nResyncronize the performance counters<\/h2>\r\nAnother way to try to recover corrupted performance counters is to use the command winmgmt<\/a>. For that, execute the following commands:\r\n
# When Windows version is older than 2003, execute this command to clear previous resync attempts\r\n# In systems newer than 2003 this command won't work\r\nwinmgmt \/clearadap\r\n\r\n# resync the counters\r\nwinmgmt \/resyncperf\r\n<\/pre>\r\nReload the performance counters<\/h2>\r\nAccording to this Technet article<\/a>, in the case the counters were not installed properly or with the wrong permissions, this command can be used to solve the problem:\r\n
lodctr \/r<\/pre>\r\nRebuild the WMI repository<\/h2>\r\nOne of the last options is to restore the WMI to its original state. To rebuild the WMI repository, use the commands below (Windows Vista or newer).\r\n
IMPORTANT:<\/strong> if your system has third party softwares that use the WMI, this command can cause these softwares to break and require a reinstall. Use the commands below at your own risk.<\/em><\/blockquote>\r\nnet stop winmgmt \/y\r\nWinmgmt \/resetrepository\r\nnet start winmgmt<\/pre>\r\nTo learn more about these commands, click here<\/a>.\r\nUpdate Windows<\/h2>\r\nCheck if there is an update related to WMI that hasn't been installed. Hotfixes like this<\/a> can be available for your system.\r\n
Third party counters<\/h2>\r\nSome applications create their own counters. If that is the case, try reinstalling the software or contact the manufacturer to obtain instructions on how to proceed."},"excerpt":{"rendered":"
How to solve WMI monitoring problems.<\/p>\n","protected":false,"raw":"How to solve WMI monitoring problems."},"author":3,"featured_media":402,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_pt_post_content":"Na Unit Platform, os monitoramentos podem falhar quando o reposit\u00f3rio do WMI n\u00e3o responde com as informa\u00e7\u00f5es corretas ou retorna uma condi\u00e7\u00e3o de erro. Este artigo lista algumas formas de corrigir esse problema.\r\n
IMPORTANTE:<\/strong> siga as instru\u00e7\u00f5es abaixo por sua conta e risco. Alguns procedimentos listados podem fazer com que alguns sistemas parem de funcionar. Em caso de d\u00favidas, contate a Microsoft e solicite instru\u00e7\u00f5es.<\/em><\/blockquote>\r\nObserva\u00e7\u00e3o: para executar os procedimentos abaixo, \u00e9 necess\u00e1rio acesso a um prompt de comando (cmd.exe) com permiss\u00f5es de administrador.\r\nReiniciar o servidor<\/h2>\r\nAlguns casos de erros no WMI podem ser resolvidos apenas com um reboot. N\u00e3o \u00e9 garantido, mas essa \u00e9 uma das alternativas mais f\u00e1ceis de executar e tem baixo risco de ocasionar problemas.\r\n
Reiniciar o servi\u00e7o do WMI<\/h2>\r\n\u00c9 recomend\u00e1vel reiniciar o servidor, mas caso isso n\u00e3o seja poss\u00edvel, pode-se apenas reiniciar o servi\u00e7o do WMI:\r\n
net stop winmgmt \/y\r\nnet start winmgmt<\/pre>\r\nDiagn\u00f3stico do WMI (WMIdiag)<\/h2>\r\nPara detectar inconsist\u00eancias no reposit\u00f3rio do WMI existe a ferramenta WMIdiag, fornecida pela pr\u00f3pria Microsoft, que se encarrega de analisar o sistema e apontar quaisquer erros com as configura\u00e7\u00f5es do WMI:\r\n\r\nClique aqui para fazer o download do WMIdiag.<\/a>\r\n\r\nPara saber como usar a ferramenta, leia este artigo.<\/a>\r\n
Atualizar os dados dos contadores de performance<\/h2>\r\nEsta alternativa consiste em usar o comando wmiadap<\/a> para for\u00e7ar a atualiza\u00e7\u00e3o dos dados dos contadores de performance.\r\n\r\nO par\u00e2metro \/f for\u00e7a a atualiza\u00e7\u00e3o das classes WMI e das bibliotecas de performance relativas \u00e0s classes Win32_PerfRawData e Win32_PerfFormattedData:\r\n
wmiadap \/f<\/pre>\r\nO par\u00e2metro \/r cria os objetos de performance usando os drivers do Windows Driver Model:\r\nwmiadap \/r<\/pre>\r\nResincronizar os contadores de performance<\/h2>\r\nOutra forma de tentar recuperar contadores de performance corrompidos \u00e9 atrav\u00e9s do comando winmgmt<\/a>. Para isso, execute os seguintes comandos:\r\n
# Caso a vers\u00e3o do Windows seja anterior \u00e0 2003, execute este comando para limpar as tentativas anteriores de resincroniza\u00e7\u00e3o\r\n# Em sistemas operacionais posteriores ao 2003 este comando n\u00e3o ir\u00e1 funcionar\r\nwinmgmt \/clearadap\r\n\r\n# execute a resincroniza\u00e7\u00e3o\r\nwinmgmt \/resyncperf\r\n<\/pre>\r\nRecarregar os contadores de performance<\/h2>\r\nConforme mencionado neste artigo na Technet<\/a>, caso os contadores n\u00e3o tenham sido instalados corretamente ou com as permiss\u00f5es erradas, o comando abaixo pode ser usado para resolver o problema:\r\n
lodctr \/r<\/pre>\r\nReconstruir o reposit\u00f3rio WMI<\/h2>\r\nUma das \u00faltimas op\u00e7\u00f5es \u00e9 restaurar o WMI \u00e0 configura\u00e7\u00e3o original. Para for\u00e7ar a restaura\u00e7\u00e3o use os comandos abaixo (Windows Vista ou mais recente).\r\n
IMPORTANTE:<\/strong> caso o seu sistema possua softwares de terceiros que usam o WMI, estes comandos podem fazer com que esses sistemas parem de funcionar e precisem ser reinstalados. Execute por sua conta e risco.<\/em><\/blockquote>\r\nnet stop winmgmt \/y\r\nWinmgmt \/resetrepository\r\nnet start winmgmt<\/pre>\r\nPara mais informa\u00e7\u00f5es sobre esses comandos, clique aqui<\/a>.\r\nAtualize o Windows<\/h2>\r\nVerifique se h\u00e1 alguma atualiza\u00e7\u00e3o relativa ao WMI que n\u00e3o tenha sido instalada. Hotfixes como este<\/a> podem estar dispon\u00edveis para o seu sistema.\r\n
Contadores gerenciados por softwares de terceiros<\/h2>\r\nAlgumas aplica\u00e7\u00f5es de terceiros criam os seus pr\u00f3prios contadores. Em caso de problemas nesses contadores espec\u00edficos tente reinstalar o software em quest\u00e3o ou contate o fabricante para obter instru\u00e7\u00f5es de como proceder.","_pt_post_name":"falhas-no-monitoramento-por-wmi","_pt_post_excerpt":"Veja como resolver problemas no monitoramento por WMI.","_pt_post_title":"Falhas no monitoramento por WMI","_en_post_content":"In Unit Platform, the monitoring checks can fail if the WMI repository does not return the correct information or returns an error. This article presents some alternatives to correct this problem.\r\n
IMPORTANT:<\/strong> follow the instructions below at your own risk. Some procedures listed here may cause some systems to fail. If you are not sure what to do, contact Microsoft and ask for instructions.<\/em><\/blockquote>\r\nNote: to execute the commands below, it's necessary to have access to a command prompt (cmd.exe) with administrator privileges.\r\nRestart the server<\/h2>\r\nSometimes the solution to the problem is a simple reboot. It's not guaranteed, but this is the easiest alternative and it has a low risk of causing problems.\r\n
Restart the WMI service<\/h2>\r\nIt's recommended to restart the server, but if this is not possible, you can try to restart only the WMI service:\r\n
net stop winmgmt \/y\r\nnet start winmgmt<\/pre>\r\nWMI diagnostics (WMIdiag)<\/h2>\r\nTo detect WMI repository inconsistencies, there is the WMIdiag tool, created by Microsoft, that analyses the system and points out any configuration errors:\r\n\r\nClick here to download WMIdiag.<\/a>\r\n\r\nTo learn how to use it, read this article.<\/a>\r\n
Update the performance counters<\/h2>\r\nThis alternative requires the use of the command\u00a0 wmiadap<\/a> to force the update of the performance counters.\r\n\r\nThe parameter \/f parses all the performance libraries on the system and refreshes the classes derived from Win32_PerfRawData and Win32_PerfFormattedData.\r\n
wmiadap \/f<\/pre>\r\nThe parameter \/r parses all the Windows Driver Model drivers on the system to create performance objects.\r\nwmiadap \/r<\/pre>\r\nResyncronize the performance counters<\/h2>\r\nAnother way to try to recover corrupted performance counters is to use the command winmgmt<\/a>. For that, execute the following commands:\r\n
# When Windows version is older than 2003, execute this command to clear previous resync attempts\r\n# In systems newer than 2003 this command won't work\r\nwinmgmt \/clearadap\r\n\r\n# resync the counters\r\nwinmgmt \/resyncperf\r\n<\/pre>\r\nReload the performance counters<\/h2>\r\nAccording to this Technet article<\/a>, in the case the counters were not installed properly or with the wrong permissions, this command can be used to solve the problem:\r\n
lodctr \/r<\/pre>\r\nRebuild the WMI repository<\/h2>\r\nOne of the last options is to restore the WMI to its original state. To rebuild the WMI repository, use the commands below (Windows Vista or newer).\r\n
IMPORTANT:<\/strong> if your system has third party softwares that use the WMI, this command can cause these softwares to break and require a reinstall. Use the commands below at your own risk.<\/em><\/blockquote>\r\nnet stop winmgmt \/y\r\nWinmgmt \/resetrepository\r\nnet start winmgmt<\/pre>\r\nTo learn more about these commands, click here<\/a>.\r\nUpdate Windows<\/h2>\r\nCheck if there is an update related to WMI that hasn't been installed. Hotfixes like this<\/a> can be available for your system.\r\n
Third party counters<\/h2>\r\nSome applications create their own counters. If that is the case, try reinstalling the software or contact the manufacturer to obtain instructions on how to proceed.","_en_post_name":"wmi-monitoring-failures","_en_post_excerpt":"How to solve WMI monitoring problems.","_en_post_title":"WMI monitoring failures","edit_language":"en","footnotes":""},"categories":[11,1,10,6,9,8],"tags":[],"class_list":["post-360","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asset-management","category-monitoring","category-multisite-monitoring","category-plugins","category-unit-platform-cloud","category-unit-platform-on-premises"],"_links":{"self":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/360","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/comments?post=360"}],"version-history":[{"count":35,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/360\/revisions"}],"predecessor-version":[{"id":403,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/360\/revisions\/403"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media\/402"}],"wp:attachment":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media?parent=360"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/categories?post=360"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/tags?post=360"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}