We upgraded Pega robotics from 8.0 sp1 (8.0.2033) to 220.127.116.11. Also upgraded the text adapter from Bluezone 7.1 to 8.1. Now it's giving the error "Your Windows HLLAPI application is not currently connected to a Host session" at random places of the code. Sometimes it fails while setting text in the Bluezone window and sometimes it fails while sending keystroke like "Enter". The Bluezone window is already showing that it's connected to session "Z" which is what we have configured in properties.
We have just modified the Path to launch Bluezone from C:\Program Files (x86)\BlueZone\7.1\bzad.exe to
C:\Program Files (x86)\BlueZone\8.1\bzad.exe. Also the file placed at "C:\Programdata\BlueZone\Config\****.zad has been updated.
Please let us know if any specific changes are required.
***Edited by Moderator: Pooja Gadige to add platform capability tag***
@jeffbadger, Thanks for reply. Yes, I had updated the the path to WinHLLAPI32.dllas well as "C:\Program Files (x86)\BlueZone\8.1\whlapi32.dll". Please note that the text emulator launches when we run the application and it displays the session ID 'Z' as connected at the bottom side window. But as soon as the login process starts where Pega robotics sends commands like user name, password and keystrokes like ENTER, the error message appears saying "Your Windows HLLAPI application is not currently connected to a Host session."
Point to note here is that error happens at random places of the code, some times it occurs during setting username, sometimes during sending password and sometimes further in the flow and always we get same Host session related error. SO I was wondering why it's causing issue at random places, if host session is not connected then it should not work at all but code breaks mostly after sending few commands to the Text Adapter (black Screen).
I have attached the screenshot of Text Adapter and Bluezone properties set in the project, in case that helps.
@PiyushT9 Do you have access to Process Explorer? It is a free tool from Microsoft that might help here. I would run it and view the DLLs injected into the BZAD process to see the full path to the WinHLLAPI dll to make sure it matches your adapter settings. There's a menu option to view dlls for the selected process. It has a bullseye icon similar to interrogation where you can select a process to look into.
That error usually means that session "Z" (in your case) is not present. It should not be disconnecting in the middle of anything. That would mean that the OpenSpan.Adapters.WinHLLAPIHost.x64 (or OpenSpan.Adapters.WinHLLAPIHost.x32) process is getting closed somehow potentially.
One other thing I would do for troubleshooting is to use the WinHLLAPIUtils component in the Toolbox. Create a new project and write out the events from it to a ListBox or something you can view on-screen as they occur. I attached a sample project, but also a screenshot of the important bits in-case you cannot open it in your version.