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

Cannot delete SNMPv3 Credential

I am trying to remove two SNMPv3 credentials that are actually duplicates.

I suspect these credentials may be causing further problems as well.

When I try to edit a node, the webpage acts as though it's refreshing and scrolls to a certain spot every second or two.

But to return to my original problem, I cannot delete these credentials in the credential manager.

Prompt comes up asking if it's okay to delete, click OK. Nothing happens.

I've tested this on some other credentials and it works fine; there are just two problematic ones not used on any nodes.

Thanks in advance. I'd love to get this resolves.

Saw an older post referencing manual changes to tables and I'd really like to not go there unless someone can specify very well what needs done.

Find more posts tagged with

Accepted answers

All comments

sum_giais

Maybe query what is using it via SWQL?

Node assigned credentials SWQL query - Custom Queries - The Orion Platform - THWACK (solarwinds.com)

donrobert5

They can be deleted from the DB directly via the dbo.credential table, and you will want to delete the associated information in the dbo.credentialproperty table as well. Using the "ID" column from the Credential table, you can link to the "CredentialID" in the CredentialProperty table and delete those corresponding rows to remove the additional settings and password info.

However, I haven't verify this with the newer versions because I no longer have a solarwinds environment.

You can also check if the SNMPv3 credential is being used for Discovery.

nerengm

Same problem here @NetworkChunk . What did you end up doing? I'm on 2023.3.1.