solomon78

I have a downtime window on Saturday when I'm upgrading the platform. Will see if the upgrade fixes it. If not then I'll follow these steps and let you know after. On Tue, Jan 24, 2017 at 2:40 PM, michael malendoski <

Hi there I was wondering if you can assist me with editing the template for the linux-unix directory size? I have a path: 192.168.54.5/db4/db4sys/db4share/blahblah/outgoing I don't know if i need to include the first part (the machine ip) or if it needs a //192.168.etc for the script to recognise it as I'm really not…

Thank you Michael, I will try this as soon as possible and let you know if it worked.

Hi there can you share what the SW techs did to assist you please? I'm having the same issue. I've also logged a ticket now - but if you can help sooner that would be great. Thank you Kind regards Ismail

Hi So since yesterday our's has been stable. The SW guy enabled TLS 1.2 on our main poller via a registry entry and I deleted alot of AGENTS that simply didn't want to connect. I think that more than anything else caused port exhaustion which required a services stop\start every few hours. Also on FRIDAY night we upgraded…

under "response time history" the date option is the variable you're looking for.

Not all heroes wear capes. You deserve a medal.

Hello Thanks for this - This looks brilliant - I wanted to know if it can be modified to run on the latest version of NPM. Because its giving a few errors when I put it in the SQL\WSQL query window. We've just upgraded to NPM 12.4