Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion SDK not working after upgrade to NPM 10.4

Our SolarWinds Admin just upgraded our NPM from 10.3 to 10.4 (Orion Core 2012.2.1, SAM 5.2.0 SP1, NPM 10.4.1, IVIM 1.5.0, VNQM 4.0). I have the SDK v1.5 installed on my machine. My unmanage/remange script is no longer working after the upgrade. Does anyone know what would cause this? I now get this error:

Get-SwisData : No DNS entries exist for host orion.domain.corp.

At line:1 char:22

+ $nodes = Get-SwisData <<<< $swis 'SELECT NodeID,DNS FROM Orion.Nodes'

+ CategoryInfo : NotSpecified: (:) [Get-SwisData], EndpointNotFoundException

+ FullyQualifiedErrorId : System.ServiceModel.EndpointNotFoundException,SwisPowerShell.GetSwisData

Here are the functions I was using for this (part of a larger VM restore script):

Function Unmanage ($vm2restore) {

#Unmanage server in Orion

$orion = "orion.domain.corp"

$node = $vm2restore+".domain.corp"

$user = "swis_user"

$pw = "swis_pass"

$pass = $pw | ConvertTo-SecureString -AsPlainText -Force

$cred = New-Object System.Management.Automation.PSCredential($user,$pass)

$swis = Connect-Swis -Credential $cred -Hostname $orion

$nodeid = Get-SwisData $swish "SELECT NodeID FROM Orion.Nodes WHERE DNS like '$node'"

$global:mynode = "N:"+$nodeid

$now = [DateTime]::Now

$later = ($now).AddDays(1)

Invoke-SwisVerb $swis Orion.Nodes Unmanage @($mynode,$now,$later,"false") | Out-Null

}

Function Remanage ($vm2restore) {

#Remanage server in Orion

$node = $vm2restore+".domain.corp"

$orion = "orion.domain.corp"

$user = "swis_user"

$pw = "swis_pass"

$pass = $pw | ConvertTo-SecureString -AsPlainText -Force

$cred = New-Object System.Management.Automation.PSCredential($user,$pass)

$swis1 = Connect-Swis -Credential $cred -Hostname $orion

$nodeid = Get-SwisData $swis "SELECT NodeID FROM Orion.Nodes WHERE DNS like '$node'"

$mynode = "N:"+$nodeid

Invoke-SwisVerb $swis Orion.Nodes Remanage @($mynode) | Out-Null

}

Here is the output from the c:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log file on the NPM server:

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at System.ServiceModel.ICommunicationObject.Close()

at SolarWinds.InformationService.Contract2.InfoServiceProxy.Close()

2013-02-12 10:57:33,101 [5] WARN SolarWinds.Data.Providers.Orion.DynamicServicesHost - Failed to subscribe to notifications for limitations, custom property, and account rights - endpoint not found. Will try again in one minute. Exception message: There was no endpoint listening at net.tcp://orion:17777/SolarWinds/InformationService/v3/Orion/certificate that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

2013-02-12 10:57:33,164 [5] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - An error occured opening a connection to the orion communication service.

System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://orion:17777/SolarWinds/InformationService/v3/Orion/certificate that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Any help would be greatly appreciated.

Thanks,

-Steve10

Find more posts tagged with

orion_sdk_1.5

Accepted answers

Jan_Pelousek

Hi Steve,

thanks for the news even if the issue wasn't resolved yet.

I looked at the issue once more and it seems to be the network problem. Please try following:

1. Launch cmd -> nslookup -> orion.unisource.corp - If my assumption is right it should fail. Then go to your orion server and in CMD run command " ipconfig /registerdns " and wait a few minutes, try the nslookup once more and if passes then try to relaunch the script. If it fails again, go to step 2.

2. Try to define the Orion server using IP address instead of the hostname. In your case $orion = "x.x.x.x" and relaunch the script.

Please let me know about the results.

Many thanks in advance.

Honza

All comments

Jan_Pelousek

Hi Steve,

it seems to me you have typo in swis connection variable in following line because the connection was previously built as $swis and you use $swish. Similar problem is in Remanage function ($swis1 vs $swis). Can you, please check it or are the used variables global?

Problem part:

$nodeid = Get-SwisData $swish "SELECT NodeID FROM Orion.Nodes WHERE DNS like '$node'"

stevekiser

Jan,

That was just a typo in the copy/paste. I ensured the original script is in fact using $swis, and am still receiving the same error.

Get-SwisData : No DNS entries exist for host orion.unisource.corp.

At line:10 char:24

+ $nodeid = Get-SwisData <<<< $swis "SELECT NodeID FROM Orion.Nodes WHERE DNS like '$node'"

+ CategoryInfo : NotSpecified: (:) [Get-SwisData], EndpointNotFoundException

+ FullyQualifiedErrorId : System.ServiceModel.EndpointNotFoundException,SwisPowerShell.GetSwisData

Invoke-SwisVerb : The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

At line:15 char:17

+ Invoke-SwisVerb <<<< $swis Orion.Nodes Unmanage @($mynode,$now,$later,"false") | Out-Null

+ CategoryInfo : NotSpecified: (:) [Invoke-SwisVerb], CommunicationObjectFaultedException

+ FullyQualifiedErrorId : System.ServiceModel.CommunicationObjectFaultedException,SwisPowerShell.InvokeSwisVerb

Thanks,

-Steve

Jan_Pelousek

Hi Steve,

thanks for the news even if the issue wasn't resolved yet.

I looked at the issue once more and it seems to be the network problem. Please try following:

2. Try to define the Orion server using IP address instead of the hostname. In your case $orion = "x.x.x.x" and relaunch the script.

Please let me know about the results.

Many thanks in advance.

Honza

stevekiser

Jan,

Thanks again for the help. I naturally changed the "actual" server name when I pasted my script to the forum. When I tried nslookup, etc., it worked because I would type the correct server name. A co-worker noticed that I had inadvertently deleted a character from the actual server name in my script, and that is why it wasn't working. Since I have been staring at it so long, my mind was reading the name as being correct.

-Steve