Tripp Lite PowerAlert Execute Command Script

February 10th, 2015

Spent days trying to figure out why the PowerAlert software would not run a batch (.bat) file automatically. The batch file would run fine manually, I just could not get PowerAlert to run it.


Save the script file in the ‘C: \Program Files\TrippLite\PowerAlert\engine\’ directory. If you save the script file in this directory, you will not have to put the path in the software’s executable command field in the PowerAlert console.

Use ‘C: \Program Files (x86)\TrippLite\PowerAlert\engine\’ if you are on a 64 bit machine.

9 Responses to “Tripp Lite PowerAlert Execute Command Script”

  1. hessercan says:

    Could you elaborate on how you got this to work? I’m having a similar issue. I did what you suggested and the on clear script I have runs when I plug the ups back in but I can’t get the power off script to run when I unplug it.

    • Craig Mashburn says:

      I assume you are using the Power Alert software? Besides putting the script in the folder referenced, Under Events, Battery Low-Critical, I have it Execute Command Script. Only the file name is listed in the field, no path.

  2. Thank you for posting this information. It is simply amazing that Tripp Lite does not seem to offer any DETAILED documentation or support for this software. Searching the web for similar information yields virtually nothing – your post is among the top results.

    I have also been unsuccessful getting .bat files to execute. I can’t use the critical alerts to test this process since I have users on my production system. I have tried to test the Contact Notification and Execute Command Script using the Communications Lost Event by disconnecting the USB connection from my UPS. Although I can see an attempt to send the email notification and I do get a log entry on my log server, the batch file does not run.

    I’m curious if you have any other thoughts on this, I have tried to put the files in the engine directory as you suggested and also in the C:\ directory with the full path – the script still will not run.

    • Craig Mashburn says:

      As far as I know, it will only run if it is in one of the two folders listed in the article. Make sure you are using the correct one. I was never able to get it to run in a different location.
      In the field where you type the actual bat file to run, it should only be the “filename.bat”.
      I ended up calling support. They were not real helpful, but I finally figured this out.

    • Hi Arizona Sysadmin,
      *Disclaimer: I work for Tripp Lite*

      I know this is late.

      Did you get your issue resolved?

      A few tips I can suggest if you didn’t:
      -Check C:\Program Files (x86)\TrippLite\PowerAlert\engine\poweralert.log for error message around the time you are triggering the script.
      -Make sure the script isn’t doing something that would cause Session 0 Isolation to block it (I can expand on this if needed)
      -A helpful test event you can trigger is “Battery Age Above Threshold”. If you edit the device’s “Date Installed” you can trigger this event (by default 3 years before today will trigger that event). It’ll work with most UPSes. I could expand with specifics if we know what platform you’re using.
      -The tip Craig posted about placing the .bat file in the engine directory and just inputting “yourscript.bat” in the GUI is a good tip too

      Even if you did get this resolved, I’d be interested to get your feedback on how we could make things more intuitive and where you tried to get help before posting here.

      • Craig Mashburn says:

        The Tripp Lite software is so unreliable. It will just stop seeing the UPS sometime and my only option is to move it to another server. Tripp Lite really needs to develop some Enterprise quality software. When it comes to buying UPS’s in the future, I will be looking at other brands, unless something new is released from Tripp Lite.

        • Hi Craig,
          I’d be interested in diving into a bit more detail on your feedback and use case. Is it something you’d be willing to discuss? There are actually a number of changes coming to our software and maybe your feedback can give us some food for thought.

          Topically, (assuming you’re using PowerAlert Local) dropping communication with a UPS might have a few different causes (the PowerAlert Agent service stopped for example).

      • *I typo’d the path to the log file above. “engine” should be “log”. The right path is:
        C:\Program Files (x86)\TrippLite\PowerAlert\log\poweralert.log

        Drop the (x86) on 32 bit systems.

  3. Basil says:

    The only thing I feel comfortable about using this to test is the “Lost communication” trigger since I also have machines in production. David, you mentioned changing the battery age – Where can we do that?


Leave a Reply to Craig Mashburn