3 Replies Latest reply: May 15, 2012 2:24 PM by tdanner RSS

PowerShell Snapin - ContractFilter Mismatch

derek.pryor

I have been reading through the PowerShell section of the Orion SDK and this thwack post and have encountered an error.

 

The powershell script is a stripped down version of the one from the linked post.

$source = Connect-Swis ..........

$sourceNodes = Get-SwisData $source "SELECT Uri, IPAddress, Caption, NodeID FROM Orion.Nodes"

 

foreach ($sourceNode in $sourceNodes) {

    Write-Host "Found" $sourceNode.Caption "(" $sourceNode.IPAddress ")" $sourceNode.Uri

   

    $sourceNodeProps = Get-SwisObject $source $sourceNode.Uri

    Write-Host $sourceNodeProps

}

Connect-Swis and Get-SwisData execute fine, and the first write-host prints what is expected.

 

Get-SwisObject throws the following error

Get-SwisObject : The message with Action 'http://schemas.solarwinds.com/2007/08/informationservice/InformationService/Read' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

Same thing with New-SwisObject.

 

I followed the instructions for install the Snapin in the Orion SDK document.

The script is running on the same machine as SolarWinds.

Due to certification requirements I am working with NPM 10.1, APM 3.5, and NCM 6.0

 
  • Re: PowerShell Snapin - ContractFilter Mismatch
    tom.rybka

    Hi Derek,

     

    The error indicates missing support for the Read operation which seems to correspond with the note that you are using NPM 10.1. Unfortunately, the CRUD interface you are referring to has been introduced in NPM 10.1.2 for the first time.

    • Re: PowerShell Snapin - ContractFilter Mismatch
      derek.pryor

      This is the first part of a larger effort in release engineering, so the question then becomes is there a way to bulk import nodes into NPM 10.1 / NCM 6.0 with custom properties? An external automated way is best.

       

      We are building a set of capabilities around NPM/APM/NCM. This includes: new custom resources, customized views, custom APM templates, custom NCM templates, maps, and more. We are looking to automate (as much as possible) the install and configuration of our modifications (custom code and customization of SolarWinds) on a clean install of SolarWinds. The need for automation stem from a desire to have a build server rebuild / install / configure our modifications, and because the final product will be deployed to multiple sites and having to have an operator click through many different dialogs to get the system installed / configured is undesirable.