MarkHofmann

 Stephen, I experimented with the polls per second tuning wizard, and have set my polling engine values to the max for both the values with no ill effects. The polling engine/webserver/Orion server never goes above 30-40% CPU. When using the suggested settings, it seemed to get "backed up" on polling. It doesn't seem to…

 This fixed the install for me: In case other people run into this, NetFlow v3 configuration might trigger a bug in Sql Server 2005 that is causing the "latch" errors. Until we work around the SQL Server bug, if you get the latch error, you can install the hotfix http://support.microsoft.com/kb/942680 which you can…

 Your screenshots were the same errors that I had when trying to install 3.0. This was also completely a fresh install with no previous version of Netflow on the SQL server. Just for kicks, I tried to install 2.2.1 with the same setup - and it worked fine. There is definitely something screwed up with the 3.0 installer. If…

David, It seems to start to process the script - and then part of the way through, I get that crash/popup. The interesting thing is, I have since tried to truncate all the netflow databases so that it would start from scratch, and I still get that error. As a test, I tried to reinstall 2.2.1 - and it works perfectly. I…

David, I tried setting the purge to 2 days. It removed lots of data - but the install still crashes. This is the exact error I get when it starts to process the Processing NetFlowDatabaseScheme.dbConfig part of the install: Configuration Wizard (popup) Error while executing script - Warning: Fatal error 3624 occurred at…

David, I just checked my summary2 table, and the row count is: 5473199. I assume you run that script you wrote from the SQL Management program. I will give it a shot and see if I have better results. Thanks! - Mark

Any update on this problem? I was testing the new 3.0 demo and had the same issue. Thanks! - Mark

Worked on the issue today with support - was informed that basic alerts are going away and not supported, to use Advanced Alerts. Configured the same Alert for High Response Time in Advanced Alerts only to have the same outcome. Will let everyone know once this is solved. As or now, I have High Response Time alerts and…

Below is what I currently have for "Response Time" alerts. Alert: ${NodeName} has exceptionaly high response time. Average Response Time is ${AvgResponseTime} and is varying from ${MinResponseTime} to ${MaxResponseTime}. Here is what I keep seeing for tons of nodes on our network (had 300+ alerts just overnight). The…

Did you ever get a resolution to your 100% CPU with the wireless addon to Orion? We have had the same problem with it since day one. We have called tech support and done many different things, and nothing helped. We do have 600+ APs on our network, however. It seems to not be able to handle a large number of APs. - Mark

Jason, That is similar to what I had to do. The default time to trigger the High Responsetime alerts was set to 0 seconds. I changed it to 3 minutes and it appears to have helped greatly. - Mark