cmartin4255

I deployed this two weeks ago. My thoughts are below. I appreciate the effort put forth adding this much requested feature to IPAM and, from the perspective of the requester, the template is straightforward and easy to use. However, the mess that the requests leave behind is problematic enough that I will be removing the…

Good news... server has been u since applying hotfix.... The first connection to the web interface took forever to come up this morning, but after that it seems responsive. Anyone else apply and have feedback?

Totally agree....

Yes, the first two were closed after doing the installation on a new server. One was related to issues I had re-installing after running the complete removal script. The most recent (not the NTA ticket) was closed earlier this week after applying the streaming fix because we went over a day without crashing. Yesterday we…

upgrade finished and system is up and responsive. I have disabled the server reboot jobs and will now have to wait and see how long it operates.

Sound advice. Thanks for the link as well.

Changing the streaming setting improved my uptime from about 8 hours to about 36 hours and seemed to help with the services crashing. Things have been pretty bad for the past few weeks, most users have stopped using solarwinds due to the crashes and poor performance and I'm pretty sure we have blown our chance to move off…

I believe all of the below are related. 00112480 00124054 00134578 00121311 00137104

Better here, was able to get at least 36 hours of up-time. After that the website was not responsive. Ran the active diagnostics and discovered the database maintenance was not completing. I looked up the issue and have corrected the problem which corrected the website issue without further actions. Still monitoring.

Things have been more stable for the most part, but the response time is slowing down dramatically as the week goes on and we get closer to the scheduled weekend reboot. Management will laugh in my face if I ask for renewal money for next year.

Did all that, even stood up a new windows server and did a fresh install and re-applied all the recommended fixes. The only way I keep it running is by rebooting the server twice a day.

I have been battling this issue for over 6 weeks (very early adoption of 12.3 , won't make that mistake again) and was experience more severe symptoms. Actually had my app server on a schedule to reboot every 6 hours, and even then it was barely functional. I applied this fix today and should know by morning if it resolved…

Same here. I was soooo disappointed in the IP request feature.

Any chance this is on the road-map for a future release?

I opened a support case and demonstrated the issue I was having and the tech confirmed in his lab that my deployment was not working properly. We changed the monitored port types under the UDT advanced settings to only the types needed, and changed a setting to enable removal of udt data for devices not seen in x days...…

As was said earlier, there are a lot of reason to NOT want UDT to monitor a port. I sure hope this gets fixed with a hotfix soon.

Will apply this immediately.. I have been battling instability issues since upgrading in early May. The past 2 months have been so frustrating I'm almost ready to shut the servers down and find another monitoring solution.

This is maddening to me.. why leave a button in a settings configuration page that DOES NOT WORK! The more I use SW, the more I come to believe that there is NO end user testing that goes into the product.