This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Database Details page "Unexpected Website Error" after upgrade from NPM 12.3 to 12.4

jinwu over 5 years ago

After we upgrade Orion from NPM12.3 to 12.4, the database details page starts to appear like this,

A quick research suggested that the page requires accessing to table sys.master but failed due to permission issue. We then grant permissions using

GRANT VIEW ANY DEFINITION TO [Solarwinds_user_name]

It solves the Website Error problem, and the page can be accessed as normal.

My question is,

Is there any risk associated to such database permission change? and

Why NPM12.4 requires further DB permission in compare to older versions?

0 steffen.gutzeit over 5 years ago

It might not had to do anything with permissions. Usually when that error shows up after a fresh installation or an upgrade it just needs a few minutes or a repair/rebuild of the website:
Orion Web Console error: Object Reference not set to an instance of an object against OrionWeb.SWTab.FilterTabs - SolarW…
Error: Object reference not set to an instance of an object - SolarWinds Worldwide, LLC. Help and Support
Best regards,
Steffen
Cancel
Vote Up 0 Vote Down

Cancel
0 bobmarley over 5 years ago in reply to steffen.gutzeit

I have a new install of 12.4 running on Windows 2106, SQL 2016 SP2. Everything else appears working but when I try to view the database details under Main Settings and Administration
I get the dreaded error.
I ran the repair in the above mentioned article and still getting the error.
I'm running Solarwinds as DBOWNER, which is the same as I have in my past installs.
Cancel
Vote Up 0 Vote Down

Cancel
0 bobmarley over 5 years ago

I ran into the same thing. I have always ran as DBOWNER in my previous installs but some things are not working in 12.4.
Cancel
Vote Up 0 Vote Down

Cancel
0 liammiller over 5 years ago

Did anyone get to the bottom of this?
Im on 12.4 HF3 now and getting the same error
Cancel
Vote Up 0 Vote Down

Cancel
0 steffen.gutzeit over 5 years ago

Could you please follow the steps outlined here: Clicking Database Details in the Orion Web Console generates an error - SolarWinds Worldwide, LLC. Help and Support
Shouldn't that work then create a ticket requesting Tech Support from SolarWinds. I've seen cases were a small sql query to grant view permissions fixed it as a workaround.
Cancel
Vote Up 0 Vote Down

Cancel
0 kingoftyland over 5 years ago

Had the same problem here I realized today. Running Orion 2018.4 HF3. I reran the Configuration Wizard as suggested in the support doc mentioned by Steffen, but only selecting the Database option. The thing I made sure of was to use our SQL instance SA credentials on the first page where the database server is defined, then on the second credentials page (3rd dialog page technically) use whatever service account you've defined for ongoing access to the database.
From what I can tell, the initial database setup requires account permissions with full rights to the SQL instance to properly set rights for the service account. The SA credentials are not used for any ongoing operations within SolarWinds, only to create and set permissions for the database upon installation or rebuild.
After rebuilding using the SA credentials in the first dialog, I can now see the Database Details page.
Further, to hopefully answer jinwu, I looked at the Securables permissions for our SolarWinds DB account, and I see that "View any definition" is granted. This was set by the config process, so it must be what's necessary.
Cancel
Vote Up 0 Vote Down

Cancel
0 liammiller over 5 years ago in reply to kingoftyland

Interesting, thanks for the info ill give it a go in my enviro and let you know how I get on.
Cancel
Vote Up 0 Vote Down

Cancel
0 rmullal over 5 years ago

I had this issue when I upgraded as well. Try running the config wizard on all polling engines...that fixed it for me.
Cancel
Vote Up 0 Vote Down

Cancel
0 wlouisharris over 4 years ago

Having the same problem. Running configuration wizard on all the pollers is quite resource heavy for us. Hoping for another fix and hate to just try something. I'm going to open a support case. Still it's not really impacting any services at this point.
Cancel
Vote Up 0 Vote Down

Cancel
0 XM07535 over 4 years ago

I have an open ticket with support. I'm running Active Diagnostics (running for the past 2 hours) and will upload once complete. Otherwise I have a scheduled call for next Tuesday to hopefully resolve it.
We tried the KB article Success Center
and it didn't work.
I have 3 polling servers and we reran configuration wizard on all of them, but no luck. I'm on the latest version of NPM 12.4 HF3. I just upgraded my system this week.
Cancel
Vote Up 0 Vote Down

Cancel