tdanner ✭✭✭✭✭

Most of these errors are harmless - just various other discovery features complaining that you didn't provide a configuration for them. The discovery manager logs the errors and moves on. However, this error is probably the reason interfaces are not getting imported correctly: 2020-07-01 16:57:26,705 [44] ERROR…

This has been fixed in NPM 12.4. ifAdminStatus and ifOperStatus are now reported correctly for DiscoverInterfacesOnNode.

This shows the call to CreateCorePluginConfiguration failing now. It was definitely working before - I can see it in the log you posted earlier today. I can also see why it is failing now: <Credentials> <SharedCredentialInfo> <CredentialID> </CredentialID> <Order>1</Order> </SharedCredentialInfo> </Credentials> Notice that…

No updates, sorry.

At this point it looks like the issue is not in the Information Service part of the discovery process, so I would turn the Information Service log level back to INFO (DEBUG has noticeable performance impact). The "Import Failed" result indicates that the next log file to look at would be…

I'm sorry that was such an unhelpful call. The intention was just that it would add your "vote" (in the form of a customer support ticket) to NPM-6293 to help move it higher in the product management queue.

I pulled the interface plugin configuration block out of the log file you posted earlier. After decode, it had these items in it: <d2p1:AutoImportExpressionFilter xmlns:d3p1="http://schemas.datacontract.org/2004/07/" i:nil="true" /> <d2p1:AutoImportStatus…

You have three problems: 1. "Unable to find credential with ID = 13" - are you sure this is the correct credential ID? 2. "Engine Id 1 does not exist" - you can query Orion.Engines to see what the right EngineID is in your system. 3. Something is messed up with RabbitMQ. I recommend you open a ticket with SolarWinds…

Please start a new thread in this forum. This 4-year-old thread has way too many unrelated questions going on in it.

We make updates to the APIs in every product release. If you want to check on the status of this particular issue, you can ask support about "NPM-6293".

The log shows this more detailed error: SolarWinds.InformationService.Verb.VerbExecutorException: Verb Orion.Discovery.StartDiscovery cannot unpackage parameter 0 of type SolarWinds.Data.Providers.Orion.Verbs.Discovery+StartDiscoveryContext ---> System.Runtime.Serialization.SerializationException: There was an error…

Progress! We have gotten past the "cannot unpackage parameter 0" error. Unfortunately "ProvideFault failed" means SWIS had some error while trying to give us an error message. We'll have to go to the log file to get it. Check C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log on the Orion server.

When you call "ExecuteSQL", you are using the API as a proxy to talk directly to the SQL database. While this can occasionally be necessary to work around bugs or shortcomings, it is not the recommended way to automate Orion products. IPAM provides an API for setting the status of an IP address:…

No.

$EngineID and $EngineId are not the same. Could that be the issue? (You can add Set-StrictMode -Version latest to the script to catch issues like this.)

["Insert into NodesCustomProperties (NodeID) VALUES (13)"]

We have no ETA for this.

To add these items, you need to use the discovery API. Discovery · solarwinds/OrionSDK Wiki · GitHub

1) In that example, it looks like the connection profile ID is 2. 3) It is confusing. This is some product history leaking through in the API. NCM used to be a completely separate product from the Orion Platform. We have tightly integrated them, but sometimes the seams show and this is one of those places. 4) That looks…

There are a few variable references here: does $EngineId have a valid value (int)? Does $DeleteProfileAfterDiscoveryCompletes have a valid value (boolean)?

The URL looks correct. The POST body should be a json array containing one element, a string with the INSERT statement. If you are sending a json object, it won't work - it needs to be a json array.

This was fixed in NPM 11.5.3.

It sounds like you might have a database performance issue. How many rows are in your Traps and TrapVarbinds tables?

No update.

1. What happens with your call to GetAllConnectionProfiles? That one takes no arguments. Are you getting an error back? 2. AddNodeToNCM takes one parameter: the NodeID to add to NCM. In your call to $swis-Invoke, the verb parameters need to be in a perl array. Like this: $swis->Invoke('Cirrus.Nodes', 'AddNodeToNCM', […

Scott, I'll follow up with you by email.

It appears that it doesn't like something about $StartDiscoveryContext. Can you post the part of the script that builds this variable?

If what you have is the node caption (let's say it is "my-server") and you want to find the net object ID of all applications on that node, this query will do it: SELECT 'AA:' + N.Applications.ApplicationID FROM Orion.Nodes N WHERE N.Caption = 'my-server'

The JobEngine directory under your NPMv7 directory belongs to APM. That's Job Engine 1.0. Job Engine 1.1 lives under Program Files\Common Files. They coexist side-by-side. Job Engine 1.0 is only used by APM 1.0. Orion 9.0 and EOC 1.0 both use Job Engine 1.1, as will APM 2.0. (Sorry for all that detail - I just wanted to…

The "Query" API in SWIS only accepts SWQL SELECT queries. To do this insert, you need to use an Invoke call. On the json endpoint, that would look like this: POST https://servername:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.Reporting/ExecuteSQL["Insert into NodesCustomProperties (NodeID) VALUES (13)"] I…