Showing results for 
Search instead for 
Did you mean: 

ERROR: Internal : Application already launched

Level 2
Hi Team,
We are not able to schedule a bot via Interactive Client(B) to a resource PC(A). The bot runs find when we do it manually on Interactive Client, but when we try running it via schedule it throws a strange error saying 
"ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Open Page with Ariba Login Page' on page 'Open QA and Login' - Application already launched" 
even though the application(Internet explorer.exe) is not running in the Resource PC and also we have added a step at the beginning to kill the process(application)
Can you guys please tell us what configurations are we missing. 
Here is our Environment
A --> Resource PC (where blue prism software and Database is installed) (Windows RDP)
B --> RDP (where Informative client is installed)
on A we have started the BPserver.exe and Connection is set to Database connection, the connection mode is WCF SOAP with message encryption and windows authentication and also, the listener is running and we can see the connection from the machine (B).
Can you please help in resolving this, this is impacting Production Go-Live

Alankar Mordekar


hello Alankar Mordekar  you are using internet explorer as browser to automate task? the process name will be iexplore.exe not internet explorer .exe.

is your process running fine in dev and QA env?
please check sometime application are not killed properly and remain in hung state as seems from task manager>details.

Neeraj Kumar

Hi Neeraj,

Yes we have used the correct name for the process, but still its not working. No, we just have one env. 

Alankar Mordekar

Level 4

Hi Alankar,
Can you try to restart the resource PC .
If the issue still persists, you can create a separate object and  try to run it .

Satish Gunturi
Senior Consultant

Satish Gunturi

Level 4

Based on the error message you provided, it seems that the Blue Prism process is trying to launch an Internet Explorer page, but it believes that the application is already launched. This may happen if the previous instance of Internet Explorer did not close properly or there is a timing issue with the automation process.

To troubleshoot this issue, I suggest the following steps:

  1. Verify that the Internet Explorer process is not running on the resource PC (A) before running the bot. You can check the Task Manager for any running instances of Internet Explorer.

  2. Double-check that the step to kill the Internet Explorer process is working as expected. You can add a temporary "Wait" step after the "Kill Process" step to ensure that the process has been terminated before continuing with the automation process.

  3. Verify that the Blue Prism process is able to interact with the Internet Explorer application. You can try adding a "Delay" step before the step that launches the Internet Explorer page to allow the application to fully load.

  4. Check the Blue Prism logs for any additional error messages or warnings. The logs may provide more details about the issue.

  5. If none of the above steps resolve the issue, you may need to contact Blue Prism support for further assistance. They can help you troubleshoot the issue and provide recommendations on how to resolve it.


Level 4

     I personally see this all the time while using Chrome.  Usually it goes away on a future workitem in the processes' queue, but it's still frustrating as we DO have the proper delays/kill task in the workflow.

My current theory is that the kill action doesn't always properly terminate the  targeted exe - I have had other co-workers say as much and they have resorted to using a powershell script instead to work around the issue.

Jeffrey McCormick
ECS RPA Team Lead
Fidelity Investments
Merrimack NH