Date: Fri, 29 Mar 2024 06:32:37 +0000 (UTC) Message-ID: <1146235.5635.1711693957952@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5634_255605828.1711693957950" ------=_Part_5634_255605828.1711693957950 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The WMIDIAG tool runs a diagnostic test against a system's WMI c= onfiguration and working status, reports any errors, and explains the confi= guration settings. The WMIDIAG tool is available from the Microsoft website . The downloa= d is an exe file that will extract 3 files. Run the wmidiag.vbs = script to start the diagnostics scan. If you receive a warning about =E2=80= =9CYour Default scripting engine is WSCRIPT.EXE=E2=80=9D, it may appear tha= t=E2=80=99s not happening, but the scan will still run in the background. A= fter it=E2=80=99s completed scanning it will automatically open a text file= with the results.
If you scroll through the file, you=E2=80=99ll see a lot of information = about the state of your system, and various performance counters used by WM= I. It=E2=80=99s fairly common to see a few ERRORS/WARNINGS in the log, espe= cially for things like =E2=80=9C(WBEM_E_NOT_FOUND) Object cannot be found.= =E2=80=9D At the end of text file you=E2=80=99ll see the overall status for= your system. This will either be:
If you see the status asking you to check the other log file, check that= , as it will contain additional details about your system=E2=80=99s WMI per= formance.
After running the tool, review the configuration for indications of cond= itions that will prevent Uptime Infrastructure Monitor from communicating w= ith the WMI system. If errors are reported, as a first troubleshootin= g step, you should try refreshing the performance counters with the below &= nbsp;commands. As they will fix most of the common WMI issues that interfer= e with Uptime Infrastructure Monitor=E2=80=99s ability to gather performanc= e metrics.
winmgmt= /resyncperf wmiadap /f
After refreshing the counters, run the WMIDIAG tool again to see if the = errors have been fixed. If you require further assistance resolving the iss= ue after running the scan and performance counter reset commands, then send= the WMIDIAG results before refreshing the counters and then again after re= freshing the counters, as well as the additional .LOG mentioned above to&nb= sp;support@uptimesoftware.com.