April 15, 2017 at 1:03 pm
Comments posted to this topic are about the item PowerShell 3rd Party tool Memory Alert
April 16, 2017 at 8:15 pm
Are you saying that "Idera" produced the memory leak? How did you determine this either way?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 17, 2017 at 8:35 am
Seems the "particular" 3rd party exe not to mention any names is on 2 different servers and 1 of them it eats the memory in X days to the point it is not functional and even a service re start hangs. So for a temporary band aid until the "3rd party vendor hands us a fix this works for now. The solution is a fix from the vendor not the band aid. Thanks for checking it out and posting, Ed
April 17, 2017 at 8:39 am
Gee, I posted another script after deleting this one I did not want to mention any vendor names. Seems the original one is up, oh well..or should I say "Yikes"..
April 25, 2017 at 2:12 pm
This numeric alert value needs "20" quotes around it.
Ed
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy