more 8.5 web issues

timf

I upgraded to 8.5 yesterday from 8.0, and went from netflow 2.0 to 2.2.   I've had nothing but issues since.  My first issue is that my network maps no longer show up properly.   Before the upgrade, I had a map of the US with lines and embedded maps.  The only thing I can see now is a big gray box with my lines and a few labels.  I pull up the map in mapmaker and everything looks great.  I tried modifying the view by re-adding the map, creating a fresh map, and changing to an existing map.  Nothing works, I can only see the big gray box of nothing. I opened a ticket with support, but no solutions yet. 

 

The other issue I am having is with netflow.  If I click on a node on my website that has a neflow data because netflow is enabled on it, the node details come up fine.  If i click on anything else, like a server, that obviously doesn't have netflow data, i get a nasty error message listed below.   I should have waited awhile before i upgraded. 

 Orion Website Error

An error has occurred with the Orion website.

Additional Information

System.Exception: Unable to create TopApplicationsReport. ---> System.Data.SqlClient.SqlException: Invalid object name 'NetflowDetail_5429'.
 at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
 at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
 at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
 at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
 at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
 at System.Data.SqlClient.SqlDataReader.get_MetaData()
 at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
 at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
 at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
 at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
 at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
 at System.Data.SqlClient.SqlCommand.ExecuteReader()
 at SolarWinds.Netflow.Reporting.TopApplicationsReport..ctor(Int32 rowCount, FilterCollection filters)
 --- End of inner exception stack trace ---

bleearg13

I should have waited awhile before i upgraded.

 

There's a lot of us having somewhat similar issues and I thought the same thing.  However, I think with the diverse amount of installations out there, we'd all be running into these strange issues no matter how long we wait to upgrade.  SW *did* do extensive beta testing with many customers, but there's no way they'd be able to account for every possible situation.  Combine this with the fact that the core web app language has changed from ASP to .NET, and you end up with even more issues.  AND on top of all of that, most beta testers likely did not install this into their production network or use their production DB to beta test, so even weirder issues unexpectedly arise because lab environments do not always mirror production environments exactly.

8.5 has a lot of great feature enhancements and I imagine the move to .NET was made for some very good reasons.  Stick with it with the knowledge that SW is working their arses off trying to support everyone who upgraded yesterday and today.  They have been very quick to fix bugs and have been pretty responsive (at least in my case) to the more critical issues.