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.

Verb "ScheduleListResources" only works for few hours after agent installation

Hello,
The powershell verb "Orion.Nodes/ScheduleListResources" to list ressources for an agent does not always work
http://solarwinds.github.io/OrionSDK/2020.2/schema/Orion.Nodes.html#schedulelistresources


1- ScheduleListResources to obtain a taskid
2- GetScheduledListResourcesStatus on this taskid : will stay in 'unknown" forever


It only works a few hours after the installation of the agent, but after that, it will never works.

PS E:\Local\Solarwinds> $result = Invoke-SwisVerb $swis "orion.nodes" "ScheduleListResources" 3178
PS E:\Local\Solarwinds> $result
xmlns #text
----- -----
http://schemas.datacontract.org/2004/07/SolarWinds.InformationService.Contract 34211f82-563a-4f0d-8...

PS E:\Local\Solarwinds> Invoke-SwisVerb $swis "orion.nodes" "GetScheduledListResourcesStatus" @($result.'#text', 3178)
xmlns #text
----- -----
http://schemas.datacontract.org/2004/07/SolarWinds.InformationService.Contract Unknown


I have tested and reproduced this problem for month and on thousands of agents (4500)

Maybe it's a plugin or update or something else which arrive and block the good execution of "ScheduleListResources"

I need to rediscover resources for ~500 agents, and it does not work. Solarwinds "support" does not support this

Parents
  • I am the only one with this problem ? I have now 7000 agents, ScheduleListResources sdk verb does not work, I have to launch manually through solarwinds website a list resources on each node to discover volumes, incredible

Reply
  • I am the only one with this problem ? I have now 7000 agents, ScheduleListResources sdk verb does not work, I have to launch manually through solarwinds website a list resources on each node to discover volumes, incredible

Children
  • I'm experiencing the same problem. Not sure if you were able to solve it but I'm in the same boat.

  • I have found another solution, as this verb does not work (and solarwinds support does not want to help on sdk)

    I have created a custom properties boolean "discovered" on nodes, "true" when at least 1 volume/interface exist, "false" if not.
    Then I have created 12 scheduled discovery tasks for agents (one by poller), filtered on discovered = false ; launched each hour 

    A another scheduled powershell script change discovered from false to true on each node with 1 volume/interface discovered

  • no more movement from support on this? i'm trying to move off of wmi and change all my existing wmi hosts to agents...it's going to take forever doing it manually.

    do you have a code snippet on how you do a discovery of an agent where discovered=false?