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

Problem installing additional poller

I am attempting to install an additional poller on a new server and the configuration wizard won't let me go home on this lovely Friday afternoon. I am beginning to wish that this wizard should share the same fate as Dumbledore.

When asked about the database and whether I want to use Windows Authentication or SQL Authentication, I choose Windows Authentication and seems to pass along an empty username. It errors out with "Can not connect to the SQL Server. The original error is: Login failed for user ''. The user is not associated with a trusted SQL Server connection." I've followed some older instructions I've found in other posts, but nothing is working.

Find more posts tagged with

Accepted answers

All comments

morgolis

When you select "Windows Authentication" it will use the account that you're currently logged in with on the client desktop. So if you have RDP'd to the server using windows credentials XYZ on the domain, that is what it's passing. If that user doesn't have permissions on the database server then you'll get this error.

If you know what the username / password combination that was used when Orion was installed (Generally it's SolarWindsNPM and a password you gave it) and then use SQL authentication with those credentials you will probably have better success.

bleearg13

It's actually not passing any username/password. My SQL server uses Windows Authentication, so I would expect to be able to use it. I recall attempting to use the SolarWindsNPM account and not having success previously, which is why I use Windows Authentication.