ASP error after 8.5 Orion and 2.2 Netflow upgrade

Question

Hi all.

Rather urgent problem here. I just upgraded to Orion 8.5, very smooth process, no errors. After that I upgraded NTA to 2.2, no errors there either. Orion website works fine, all subpages and functions working fine.

However when I click "Netflow Traffic Analysis" on the top of the Orion webpage I get the following error
System.Configuration.SettingsPropertyNotFoundException: The settings property 'TrafficAnalysis.NetFlowSummaryViewID' was not found. at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName) at System.Configuration.SettingsBase.get_Item(String propertyName) at System.Web.Profile.ProfileBase.GetInternal(String propertyName) at System.Web.Profile.ProfileBase.get_Item(String propertyName) at System.Web.Profile.ProfileBase.GetPropertyValue(String propertyName) at SolarWinds.Orion.Web.UI.OrionView.SelectView() at SolarWinds.Orion.Web.UI.OrionView.OnPreInit(EventArgs e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

If I run the admin page and select Netflow summary page and preview it is presented OK but with a different path. The path on the Orion page is servername/.../SummaryView.aspx and in the admin preview netadm01/.../SummaryView.aspx

I need some quick fix to this.

Regards

Fredrik Hofgren

timf · Answer

I was getting the same thing with several of my accounts, but my Admin account was working fine.  Instead of copying the admin account and then go through the pain of re-customizing, i did a little hack.  I went into the actual database using the native ms sql tools and modified the orion database, specifically the "Accounts" table.  I modified the "NetFlowSummaryViewID" column to match my non-working accounts to the admin account setting.  I changed it from 0 to 63 in my case. Worked like a charm.

I'm sure this is a very non-approved way to do it, but I can click on the netflow traffic analysis link now.  I could find no other way in the web settings to change it.  It's a hack, but it worked.

FormerMember · Answer

We are having the same issue.  Can you post any findings?  Thx much.

Stig, we'll need those diagnostics.  Can you run those and attach them to a Support ticket?

StigLeschley · Answer

We are having the same issue.  Can you post any findings?  Thx much.