• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 1459 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Asset Discovery not returning collection results (WMI)

duece7

We are new to WHD and have a server up and running.  Clients imported just fine through our Active Directory connection but we are trying to import assets and the WMI connection is finding our assets but the Collection Results say zero.  We are using a domain admin account and it's the same account that works just fine on our old spiceworks server for WMI collection.  Any ideas on what we're missing.  We tried with the domain field populated and then the login, we tried with it populated then the user name had domain\username format, and we tried with domain field empty and username format of domain\username.

Thanks for any help

  • 0

    Not a fix but I'm having the exact same problem except it work intermittently . The support guy said to check the logs on the server that hosts SolarWinds ...  

  • 0

    Have you checked your server firewall to your workstation? Also, try connecting from a command prompt on your WHD application server to see you can connect correctly.

  • 0

    We can connect properly via a command prompt and we've ran all the WMI tests and tools and they connect just fine.  We also use Solarwinds ipMonitor which utilizes WMI and it works just fine.  Windows firewall is turned off on the server as well as target machines.

    We've combed through the logs before and everytime we either create a new WMI connection or sync the previous one, these are the only errors that keep getting repeated for each node.  This is just a snippet, but it does this error for each node it skips and doesn't collect data for.

    2021-03-11 10:23:35.453 [requestMessageListenerContainer-1] INFO c.s.d.manager.CollectionManager - Registering collection activity 943b1166-db56-4e3d-b681-934e375ea120 for 161 node(s)
    2021-03-11 10:23:56.500 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute serial_number was not collected properly for nodeId 125
    2021-03-11 10:23:56.500 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute hostname was not collected properly for nodeId 125
    2021-03-11 10:23:56.500 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute model was not collected properly for nodeId 125
    2021-03-11 10:23:56.500 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute manufacturer was not collected properly for nodeId 125
    2021-03-11 10:23:56.500 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute available_memory was not collected properly for nodeId 125
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute operating_system was not collected properly for nodeId 125
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultMessageHandler - Some of the attributes of the node with id 125 were not collected properly, skipping this record
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute serial_number was not collected properly for nodeId 3
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute hostname was not collected properly for nodeId 3
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute model was not collected properly for nodeId 3
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute manufacturer was not collected properly for nodeId 3
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute available_memory was not collected properly for nodeId 3
    2021-03-11 10:23:56.501 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute operating_system was not collected properly for nodeId 3
    2021-03-11 10:23:56.502 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultMessageHandler - Some of the attributes of the node with id 3 were not collected properly, skipping this record
    2021-03-11 10:27:39.877 [WmiExecutor-89] WARN c.s.d.api.wmi.WmiSession_IWbemImpl - Collection exception for 'Win32_Product': org.jinterop.dcom.common.JIException: The remote procedure call failed. This could be an internal library error or the COM server simply declined the request. Please contact library development team. [0x800706BE]
    2021-03-11 10:27:39.877 [WmiExecutor-89] WARN c.s.d.wmi_executor.WmiCollectionJob - Collection of Win32_Product failed.
    2021-03-11 10:27:39.884 [WmiExecutor-89] WARN c.s.d.api.wmi.WmiSession_IWbemImpl - Collection exception for 'Win32_PatchPackage': org.jinterop.dcom.common.JIException: The RPC server is unavailable. Please check if the COM server is up and running and that route to the COM Server is accessible (A simple "Ping" to the Server machine would do). Also please confirm if the Windows Firewall is not blocking DCOM access. [0x800706BA]
    2021-03-11 10:27:39.884 [WmiExecutor-89] WARN c.s.d.wmi_executor.WmiCollectionJob - Collection of Win32_PatchPackage failed.
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute serial_number was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute hostname was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute model was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute manufacturer was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute available_memory was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute operating_system was not collected properly for nodeId 172
    2021-03-11 10:27:47.238 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultMessageHandler - Some of the attributes of the node with id 172 were not collected properly, skipping this record
    2021-03-11 10:28:35.639 [WmiExecutor-82] WARN c.s.d.api.wmi.WmiSession_IWbemImpl - Collection exception for 'Win32_Product': org.jinterop.dcom.common.JIException: RPC_E_UNEXPECTED - An internal error occurred. [0x8001FFFF]
    2021-03-11 10:28:35.639 [WmiExecutor-66] WARN c.s.d.api.wmi.WmiSession_IWbemImpl - Collection exception for 'Win32_Product': org.jinterop.dcom.common.JIException: RPC_E_UNEXPECTED - An internal error occurred. [0x8001FFFF]
    2021-03-11 10:28:35.639 [WmiExecutor-82] WARN c.s.d.wmi_executor.WmiCollectionJob - Collection of Win32_Product failed.
    2021-03-11 10:28:35.639 [WmiExecutor-66] WARN c.s.d.wmi_executor.WmiCollectionJob - Collection of Win32_Product failed.
    2021-03-11 10:28:35.639 [WmiExecutor-82] INFO c.s.d.wmi_executor.WmiCollectionJob - Caught exception: The timeout has occurred during the collection of 'Win32_Product'.
    2021-03-11 10:28:35.639 [WmiExecutor-66] INFO c.s.d.wmi_executor.WmiCollectionJob - Caught exception: The timeout has occurred during the collection of 'Win32_Product'.
    2021-03-11 10:28:35.650 [WmiExecutor-45] WARN c.s.d.api.wmi.WmiSession_IWbemImpl - Collection exception for 'Win32_Product': org.jinterop.dcom.common.JIException: RPC_E_UNEXPECTED - An internal error occurred. [0x8001FFFF]
    2021-03-11 10:28:35.650 [WmiExecutor-45] WARN c.s.d.wmi_executor.WmiCollectionJob - Collection of Win32_Product failed.
    2021-03-11 10:28:35.650 [WmiExecutor-45] INFO c.s.d.wmi_executor.WmiCollectionJob - Caught exception: The timeout has occurred during the collection of 'Win32_Product'.
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute serial_number was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute hostname was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute model was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute manufacturer was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute available_memory was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultProcessor - Attribute operating_system was not collected properly for nodeId 31
    2021-03-11 10:28:35.664 [resultMessageListenerContainer-1] WARN c.s.d.listeners.ResultMessageHandler - Some of the attributes of the node with id 31 were not collected properly, skipping this record

  • 0 in reply to duece7

    create a support call with Solarwinds...

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.