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

Node custom properties re-configuration

Hello!

I just added new node to Orion with unassigned "Depeartment" and "Environment" custom properties.

The problem is now I'm not able to find that node from search, when attempted to open link from the "Audit Events" menu got that "Unexpected Website Error. You are not permitted to view net object". Even when I'm trying to open this node with my Admin based user account.

How can I edit this node and change "Depeartment" and "Environment" custom properties to required?

Thanks!

Find more posts tagged with

Accepted answers

alexggolovin

Thanks guys, seems I already found the way how to fix it. Just go to the:

Setting -> Accounts -> Edit account -> Remove account limitations

After that my account limitations been removed I was able to see that hidden node again.

What about the database changes, it's a good advice, maybe will be helpful for some sort of changes in feature.

All comments

bspencer63

alexggolovin Have you tried re-adding the node yet?

alexggolovin

Yes sure, when I try to add it again it notifies me with error about that node already exists.

d09h

Should be in the database in Nodes table (via Database Manager in RDP session to app server or SQL Management Studio wherever your database lives). Most likely the last entry. In any case, you'll see everything as limitations don't apply in that context.

Disclaimer--SolarWinds will strongly discourage direct editing of the databqase.

That said, make the Nodes table writeable and set your properties. Then get out before you break something.

Or just do what ">bspencer63‌ said. But then you'd still have those those nodes and the duplication.

alexggolovin

It's a production server, I'm afraid about any not recommended by Solarwinds solutions. Are you sure there is no any other way how to get access to this node for changes or removing available?

Thanks,

bspencer63

alexggolovin,

You definitely don't have much historical data since the node was just added, I'd delete and re-add and you should be able to edit all the fields.

If you don't want to go that way, I've never had an issue changing things as outlined by d09h

You should be able to edit the fields necessary. It would only affect the node you are working on if you edit something and should not "break" anything. Just edit the node in question as outlined above.

With that said, I'm sure we'll get a "recommendation" by a SW Geek on this one that we shouldn't do this, but sometimes, it's the only way to "get it done"!

alexggolovin

Thanks guys, seems I already found the way how to fix it. Just go to the:

Setting -> Accounts -> Edit account -> Remove account limitations

After that my account limitations been removed I was able to see that hidden node again.

What about the database changes, it's a good advice, maybe will be helpful for some sort of changes in feature.

bspencer63

Most of the time, it's a simple fix! Thought you had access after the "admin" comment.

Note to self.... Always think security when access is denied to an object! DOH!

d09h

Russ, Audrey...earmuffs.

I mean SolarWinds moderators...nothing to see here.

I bet if a poll was done among SW admins, this probably gets done relatively often. It's never my first choice, however.

alexggolovin, can you launch the custom property editor and view all nodes...and then locate the offending ones? Or are they suppressed from your account view by account limitations? (I had assumed that was the case, but if not, it seems you could find them in the custom property editor.)

d09h

Don't forget to reapply the limitations if applicable. Might want to consider creating an account with no limitations for times like this...or just remove limitations as you just did.

Editing via the database has not burned me (yet). Knock on wood.