Failed to perform step 1 in Navigate Stage - The host session was busy

Hey guys,

I have a process that writes notes in a mainframe app.

It writes a note, hits enter, then waits to see if there is a popup and if it finds it, it puts Y and hits enter again.

Every once in a while, I get the following unexpected error:

Error type: Internal
Error details :Failed to perform step 1 in Navigate Stage 'Send Keystroke' on page 'XXX' - The host session was busy; all of the keystrokes could not be sent. Return code: (4)

The 'Send Keystroke' navigate stage is a Global Send Keys with @E in the value.

I am not sure what "The host session was busy" means.

I got this error this morning. When I check the item in mainframe, I see that the note was added, therefore the first Enter worked. The process did not get to the next stage, so I assume the popup appeared and the process was not able to hit the second enter. I don't see anything in the logs because it is inside the BO.

The process treats around 150 items a day and I get the exception less than once a day. I could not find a pattern with the items it was treating when i got the error.

Is there any ways for me to enhance the logging to see the BO logs as well?

Any advice would be appreciated!

J-P

Hi jpcrepeau,

I'm assuming that you have already turned ON logging for the BO and still unable to identify the issue. Here are a few things that you could try of-
- Add a log file functionality to your Process/Object which will write a customised message into the text file just before the Navigate Stage 'Send Keystroke' on page 'XXX'. This will help you determine which item it was working on before throwing the error. You will be able to achieve this with the readily available actions in the 'Utility - File Management' VBO where you can keep on appending messages to the text file. Also you can customise your Log File functionality with a True/False Session variable so that you can easily disable the log file writing from the Control Room when not needed.

- If that doesn't work out for you and you would like to have a bit of enhanced identification feature then you can add a stage to capture a screenshot just before that Navigate Stage. To achieve this you can use the code in the below link.
http://rpaforum.net/threads/procedu...e-in-data-item-using-blue-prism.862/post-2614

The code in the above link saves the actual screenshot image in an Image data item as well as saves the image to a folder path. You can disable the saving into an Image data item and just keep the file on a folder path for later review of the screenshot.

Probably this might help you identify the issue by giving a visual representation of whats going-on on the screen.

Thank you so much for the reply.

I tried to add the screenshot capabilities but because the robot doesn't unlock the machine, it doesn't want to grab the screenshot. If I remote desktop on the ressource it works. I feel like adding a login to the process could create more problems than good.

I will look at the other logging options and hopefully find the root cause.

Thanks again!

J-P

jpcrepeau said:

Thank you so much for the reply.

I tried to add the screenshot capabilities but because the robot doesn't unlock the machine, it doesn't want to grab the screenshot. If I remote desktop on the ressource it works. I feel like adding a login to the process could create more problems than good.

I will look at the other logging options and hopefully find the root cause.

Thanks again!

J-P

Click to expand...

I feel like adding a login to the process could create more problems than good.
Did you intend to say logging. If so, to keep it plain and simple it is just one action (Append to Text file). This will even create the text if it doesn't exists and keep on appending the desired text.

Below is how it is used for a simple process to add 2 numbers.

View attachment 1529565742240.png

Append to Text file Action properties:
View attachment 1529565838414.png
You can append the datetimestamp to the name of the log file.

Final Log file:
View attachment 1529565883271.png