I have so far found 2 possible workarounds - although neither is perfect. We are running Automation Point 3.4 for NT and things may be slightly different under 3.5.
First, we are currently starting Automation Point with the Autostart service. This service uses a "system account" to...
We are running Automation Point on NT 4.0 and are using REXX for the program logic and workflow.
The REXX is setup to call an executable (TEXT.EXE) which will then start/stop a service on another server on our network. If I run the TEST.EXE from a desktop command prompt on the Automation Point...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.