rwbuckn

Just got off the phone with support. One extra step that has to be done after the upgrade. Have to update the report schema to add the custom properties. All reports working again. quote:Originally posted by rwbuckn Anybody else running the pre-release 7.1 yet? I am and now all of my reports that contain custom properities…

I agree. Any information would be greatly appreciated. quote:Originally posted by Grabowski I think it would be very appropriate! So, what was the answer? quote:Originally posted by mickc Hi, Placed a support call & got the answer I needed (very quickly too!). Not sure if it's appropriate to post it here though? mick Lars…

I've been experiencing this problem too. Only I'm running Enterprise SQL so no 2Gig limit on the database. I've been working around it by rebooting my Orion server nightly. I just got off the phone with support. They told me my problem should be fixed with 7.1. I installed 7.1.89 yesterday and disabled my nightly reboot. I…

I'm still getting it on 7.2

I see 7.7 is out now. Anybody care to elaborate on the changes made to the 7.6 beta that we tried out and 7.7?

I went looking for the 2 or 3 other posts relating to 7.6 beta. I was going to ask about the status since we've received the e-mail about a performance hit. Seems like they have deleted those post! Am I missing something or am I right?

quote:Originally posted by iunderwo The delay is based on the rediscovery interval. Interface speeds and descriptions are only read on a periodic basis, and not with every polling cycle...mostly due to efficiency, and most of that stuff doesn't change much. // Ian Underwood - Service Management // Level 3 Communications…

Hey I'm having that same problem.

quote:Originally posted by Network_Guru You may need to tune your polling engine. Download and install the Polling Engine tuning tool. How much do you trust the tuner? I've been told by SW support not to use that tool. In fact when I do the math manually, I come out with a number of 69 polls per second, when the tuner…

Thanks, that's what I needed. I completely forgot to look at the additional reports on Solarwinds site. That logic coupled with Crystal Reports made a real nice MTTR report.

Are you still having this problem? I was having it with 7.1 but it cleared up after upgrading to an early 7.2 beta. It's back now that I've upgraded to the production version of 7.2. I've been working with support but so far nothing. Was wondering if you found anything?

I'm testing this function out on a Treo 600. I made some custom views and a user account just for handheld use. The views are 1 column with a width of 200. I'm just showing the essentials such as down nodes, high util and such. I'm pretty excited about the outcome. Looks really good and a fair response time. Only problem…

quote:Originally posted by Mithrilhall Sounds very similar to a problem I just had. Every few months it would look like Orion stopped polling. I would have to stop and restart the service or server to get it to work properly again. Last week I had the same problem so I rebooted the server. It would poll during the Baseline…

I'm not getting as near as many missed polls as I did before "lowering" my polls per second settings. I do on occassion have nodes on the higher end of the table (higer nodeID, last ones added to Orion database) go to warning state for a cycle or two. My worst problems with missed polls was with switches on the same subnet…

I had this problem for many month through several releases. I worked with Solarwinds support on several occasions only to be led in the complete opposite direction from what I hope finally fixed my problem. Support told me to ditch the "Polls per second" tuning tool and suggested some settings that were more than double…

I have Solarwinds looking into the COM+ errors in my application log now. I'm already running 7.2. Guess it didn't fix the problem!

I've looked through the registery and can't find anything obvious. As good as this product is, Solarwinds sure lacks on documentation. quote:Originally posted by jonchill Just upgraded to 7.3 and it seems to of solved the false positives on packet loss. One of the changes that is mentioned in the Release notes is the…

Every time I use map maker I fuss about the method of locating elements. I sure wish it had a filter to narrow down the elements to select from like Custom Property Editor has. That might help you out as well.

Has anyone else noticed this? Running 7.5 on my dual Xeon server, both processors ran about even. Now with 7.7 one is running about 2 times higher than the other. I reported the same thing on 7.6 beta but never got a response.

One of the more serious problems that I had with 7.6 beta was with stopping the service. Under 7.5 it would stop in seconds unless I was having a problem with polling. With 7.6 beta it would take 45 minutes to an hour no matter what. Can anybody verify that this is NOT the case with 7.7?