Hi Filip,
The answer could be tricky, as on a general level we would recommend Blue Prism and the Target Application to have matching bit-ness. However, a bit more information for context may be useful. Blue Prism's core processes are 32-bit processes regardless of which version is installed, and irrespective of whether the 32-bit or 64-bit option is installed. The 64-bit installation includes a 64-bit version of the Application Modeller (APPMAN64) which is an interface to 64-bit applications specifically (using the "External, 64-bit mode").
The 64-bit version of Blue Prism is designed to be installed on 64-bit operating systems.
However, 64-bit Blue Prism can work with both 32-bit and 64-bit applications. The 32-bit version of Blue Prism can only work with 32-bit applications and can only be installed on a 32-bit operating system.
Therefore, if you intend to interact with 64-bit applications you will need to install the 64-bit Blue Prism on to a 64-bit operating system, and this will allow you to interact with both 32-bit and 64-bit applications.
If you're using 32-bit Blue Prism and this is a 64-bit target application, we could only suggest to install the 64-bit version of Blue Prism to help prevent this issue. If you're using 64-bit Blue Prism and this is a 32-bit target application, you'll want to ensure you're using the correct
Application Manager mode (KB link). If you still encounter this issue, review the session and EV logs from a time of failure to determine if this is a connectivity problem to the target application, or an issue with the application (freezing, etc) itself.
------------------------------
Steve Boggs
Senior Software Support Engineer
Blue Prism
Austin, TX
------------------------------