Issue
When using a supported emulator (see link below for list), Foxtrot/RPA cannot connect or if it did in the past and "all of a sudden" will not connect anymore.
Resolution
If it connected in the past, check to see if an update was received since the last time Foxtrot/RPA connected with the emulator. Java will send out updates and if accepted, the update will upgrade your Java version to a 64 bit version which will "break" your Foxtrot/RPA connection.
- Go to Search and type "Java"
- Choose About Java from the list
- If Java version shows 64 bit, then you will need to remove the 64 bit version of Java and reinstall the 32 bit version and this should resolve your issue.
**Be careful in the future of the Java update notification. Speak to your IT professional to find out what is best to do, keeping in mind that the 64 bit version will not work with Foxtrot/RPA.
Additional Information
If Foxtrot/RPA will not connect, please check:
The emulator must be HLLAPI complaint to be recognized by Foxtrot/RPA.
The emulator and Java version must be 32 bit, Foxtrot/RPA does not work with 64 bit systems.
For IBM iAccess 5250 emulator:
In the Supported Emulator link below, there is a pdf at the bottom which shows how to setup the IBM iAccess 5250 emulator. Even if you are not using the IBM emulator, there is a lot of good information in that pdf that may assist you in troubleshooting.
In the PDF mentioned above step 7 shows where the EHLLAPI Bridge must be.
Go to the install directory: C:\Program Files (x86)\IBM\EHLLAPI and copy the 17 files into the Emulator Directory: [Desktop]\ IBMiAccess_v1r1\Start_Programs\Windows_i386-32
Make sure the screen is adjusted as it mentions in steps 15-20 or RPA will not be able to target the emulator correctly and this could stop the connection.
If you see a red X on the bottom left, this means the user tried to target an invalid target and the emulator is frozen. The user must press escape to clear that before trying to target again.
You cannot target the entire screen with this emulator. If you need to, please reach out to support with details as to why you need to target the screen and we will help find a scripting resolution.
