lopaka1313

This is a no brainer!

I deleted all of the wireless from my system and now I've been running nice a smooth!

Hey Spiky, Can you post how you wrote your alert please?

I still get "stuck" on the wireless and it really screws everything up. I don't know if I should just clear out all that data and start fresh. I need help though. This is getting really old.

Installed NPM 9.5 SP3 today and then tried to do DB maintenance and ran in to the same issue of it locking up when it hit "Summarizing detailed data from NPM_WIRELESS"

Me as well.

If SP2 on 9.5 is the latest then YES.

Thanks Jason, I looked at the log file and found that it was hanging on the NPM_Wireless table. I have removed all wireless devices from NPM over a month ago. Are these old files? How can I delete them? 

I get the same as VegardAa.

Excellent!

These are great! Been trying to figure out something like this. Great job!

That's excellent! Great addition.

I had been having this problem with V9.0 for a long time and I opend a case and the tech had me uninstall NPM and download a fresh copy from Solarwinds site and reinstall. This was our last resort of course. Well, this worked for months until I added the VoIP Monitor module. My problem came back. I upgraded to v9.1 SP3…

I'm having this same problem. "Bad Password" I verified my credentials and have changed them to different known working creds. I have tried just downloading a config from just 1 device. I am testing NCM so this is an eval copy but still I need to test it's features. WTF?

The IETF's current set of MIBs do not cover reporting on multiple CPUs, so a device that has multiple CPUs must send statistics that are averaged for all of its CPUs. This means that Solarwinds developers do not have a way to request information for individual CPUs. But when the IETF releases an RFC that introduces a…

I have been logging in to my Orion server everyday to kill this process (including weekends) but today I created a batch file that kills the process and then I set up a scheduled task to run the batch file right after the process starts. Now I don't have to worry about it.

Had tech support on my machine this morning poking around with the SQL code. He said it was probably a bug and was escalating to DEV. Here is his reply: "I have just checked in with Dev and this issue was reported last week and they are hopefully going to put a fix in the next Service Pack (SP3). At the moment I have no…