Return
-
Title
Error: "Failed to execute collection [DBSS_DTC_Information], reason=failed to run WMI query: DBSS_Dtc_Information1_0_0_0.wmi" -
Description
The following error appears in the agent log file:---ECHO ERROR [MyAgent-lowPriorityPool-2-[DBSS_DTC_Information][2016/03/01 14:47:38]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSDTCInformationProcessor processor of DBSS_DTC_Information collection.java.lang.RuntimeException: Failed to execute collection [DBSS_DTC_Information], reason=failed to run WMI query: DBSS_Dtc_Information1_0_0_0.wmi[...]Caused by: com.quest.qsi.fason.framework.connections.fglam.wmi.exceptions.WMIInvalidQueryException: WinRM request to http://MyHost:5985/wsman failed: [code:2150858778] The WQL query is invalid. - Profile:FglAM Connection Profile {Host = MyHost, Agent = MyAgent} Query: "Select PartComponent From MSCluster_ResourceTypeToResource Where GroupComponent = "MSCluster_ResourceType.Name=\"Network Name\"" and (PartComponent = "WindowsInfoReference:\\MyHost\root\mscluster:MSCluster_Resource" OR PartComponent = "WindowsInfoReference:\\MyHost\root\mscluster:MSCluster_Resource" ) "---What does that mean? -
Cause
Product defect
This only occurs using WinRM connections.
Only the DTC information data is missing; affected dashboard is "Services | DTC".
-
Resolution
WORKAROUND:
Pplease use a WMI connection instead of WinRM to collect data from the operating system of the monitored host.
A workaround is to turn off the WinRM listener on the remote target host. The Foglight agent manager which initiates the connection will then fail on its attempt for a WinRM connection and fail-over to WMI to connect.For an HTTP Listener:
winrm delete winrm/config/Listener?Address=*+Transport=HTTPFor an HTTPS Listener:
winrm delete winrm/config/Listener?Address=*+Transport=HTTPSIf required solution 102431 provides details how to setup WMI on the target machine.
STATUS: SSFOG-337 is fixed in DBSS cartridge version 5.7.5.50.
Also Enhancment Reqquest FOGDG-301 "Provide ability to control over which connection & port for WinRM" has been submitted for consideration in a future release.
-
Defect ID
SSFOG-337 -
Additional Information
It has been determined that the DB agent is parsing the WMI query result in a wrong way. The query returns a reference instead of an object (in WMI connection the D agent receives the referenced value directly).