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

When SDK won't authenticate to the Solarwinds database because there's no listen on Port 17777--how does one correct this?

I've been unable to connect SDK's SWQL Studio to my Solarwinds database for a few weeks, and haven't taken time to look into why.

The message I get is:

This worked well in months past. I found a more recent release of SDK (2.5.0.214) and installed it. There was no benefit--it still fails, but it gives me many options for connecting:

I tried all of them. The two highlighted in yellow provided only a slightly different error:

I ran a port-scan of my SW database server and I do not see a Listen on TCP port 17777 or 17778. So there's little surprise to having SDK fail to access it.

Where do I go on the database server, or elsewhere, to correct the issue?

Rick Schroeder

Find more posts tagged with

sdk_port_17777

Accepted answers

jm_sysadmin

I see your alias is solarwindsdb my SWIS connections go to my primary polling engine, is that what this alias points to?

All comments

jm_sysadmin

I see your alias is solarwindsdb my SWIS connections go to my primary polling engine, is that what this alias points to?

jrouviere

SWQL Studio doesn't connect to the DB directly, but connects to the primary server or an APE.

At first I was thinking check the service, firewall, etc, but then I noticed that. If you point it to one of your APEs you should get the same data, but that it's SolarWinds itself that's offering up the information through the SolarWinds Information Service which would only exist on one of your polling servers.

rschroeder

That helps explain the problem trying to get to port 17777 and 17778; thank you.

Pointing SDK at my Main Instance's FQDN reveals a new error:

My organization is getting tighter and tighter on security every day. So I regard the above message as an improvement. At least SWQL Studio hit a valid listen on a valid destination server.

Next I started trying each of the Server Types in the drop-down for SDK's "New Connection" and eventually selected one that got me right into the database. I'm happy. Your answer put me onto the right track, jrouviere, and trial & error did the rest.

I wouldn't say "no" to an online resource equivalent to "SDK for Dummies" that helps me make the best choices first. Many experts have written Thwack entries that are helpful to many Thwack users, but I've not yet seen a guideline for beginners that takes the time to cover the very first baby steps to start down the SWQL path for anyone with no scripting knowledge. Given how intuitive Solarwinds products are, with such great GUI's, it doesn't seem to require anyone to RTFM before starting their first NPM adjustments. But in SDK, one at least must be provided the right methods for attaching to the correct server and using the right server type. Especially when a significant amount of time & projects have passed by since one last accessed SDK successfully.

This is another great example of how awesome Thwack members are. Answering quickly with helpful suggestions and getting me headed in the right direction. Excellent work, jrouviere and jm_sysadmin ! Thank you.

"The packets have returned to normal speeds. Go about your business, Citizens; there's nothing to see here."

jm_sysadmin

Glad you are moving forward, shout if you need anything else, is that error in the new post related to an new alias? I always use the hostname with an fqdn

jrouviere

I agree with your assessment on SWQL knowledge. Once upon a time that was in the works, but life happened and outside of the Devs and Head Geeks I'm not sure how many people at SolarWinds have any more knowledge. It's definitely there, but for the rest of us it's largely self taught.

Here's a few resources that I've found previously to help get me started:

Intro to API, SDK & SWQL

Orion Platform SWQL, Thwack! Now I got it.

https://loop1.com/swblog/using-the-rest-api-to-get-the-most-out-of-solarwinds-part-2/

SWQL Functions · solarwinds/OrionSDK Wiki · GitHub

There are sample scripts and more if you need to get into that, but the GitHub is something I go to for pretty much every project and often for reports to discover what the SWQL functions and the like are, the examples can help discover what's available and there's a link to the Schema if that's more your speed as well.

It's a lot of information, but the basics are fairly simple and interchangeable, it's just discovering what you need for each project from there.