App Manager v6.0.1.2 and older causes a problem if you install the Robot twice in the same session, i.e.:

• Open App Manager
• Select Instance A
• Install Robot A
• Switch to Instance B
• Install Robot B

The files and folders get installed as you’d expect, but the services in Control Panel are not correct:

The second service doesn’t get the right name, and both of them point at the same path.  This means that Pentana A’s robot is controlled by two services, while Pentana B’s never gets started.

Workaround

If using App Manager v6.0.1.2 or earlier and are going to work on two instances of Ideagen Internal Audit (Aura) on the same server:  Work on one instance, switch, then quit App Manager and re-open.

Fixing existing occurrences of the problem

If you see a Robot service with the name ‘Pentana Robot Service’ then this is an indication that there could be a problem.  Check the paths of each Robot service installed on the server, and make sure there is no duplication.

If an instance requires fixing, the safest method is to delete the existing ‘faulty’ service and re-install via App Manager:

• Delete the folder containing the ‘faulty’ service application files (e.g. following on from this example C:\Program Files (x86)\Pentana\ServerRobot\PentanaB)
• Delete the service, for example using sc and the display name of the ‘faulty’ service:
  

  sc delete PentanaB

• Ensure App Manager is configured correctly for the Robot service to be replaced
• Reinstall the Robot
• Ensure the folder properties for the new Robot allow the service account write permission
• Update the Log On As details in the service properties with the Robot service account details
• Start the Robot, see it starts without error
• Check the Robot application folder and see that the log file gets created