Known Issues and Workarounds

Overview

Sometimes things don't quite work like you'd expect, and while we may not have a fix just yet, we do have a way to get things back on track.

Known Issue Workaround

Known Issue	Workaround
[PRB36324] Empty result returned from agent poller invocation. Symptoms: Agent intermittently sends data throughout the day. Agent does not send data after an upgrade/installation	Root Cause: The Agent process is not terminated before starting again. Workaround: Kill the process and restart the FireScope Agent.
[PRB36866] Agent reports wrong Windows Operation System Version Symptoms: Use of the `host_information` Agent Remote Attribute operation on a Windows 2019 Datacenter returns "Windows Server 2012"	Root Cause: Hardcoded value checks for operating system versions Workaround: Use a WMI Attribute to get the most accurate results for Operating System and Version. Example operations: For Operating System: host_run(powershell -command "&get-ciminstance -classname win32_operatingsystem \| select-object -expandproperty caption") For Operating System Version: host_run(powershell -command "&get-ciminstance -classname win32_operatingsystem \| select-object -expandproperty version")

[PRB36324] Empty result returned from agent poller invocation.

Symptoms:

Root Cause:

Workaround:

[PRB36866] Agent reports wrong Windows Operation System Version

Symptoms:

Use of the host_information Agent Remote Attribute operation on a Windows 2019 Datacenter returns "Windows Server 2012"

Root Cause:

Workaround:

Use a WMI Attribute to get the most accurate results for Operating System and Version. Example operations:

For Operating System:

host_run(powershell -command "&get-ciminstance -classname win32_operatingsystem | select-object -expandproperty caption")

For Operating System Version:

host_run(powershell -command "&get-ciminstance -classname win32_operatingsystem | select-object -expandproperty version")