ERROR: Internal : Application already launched
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-04-23 12:43 PM
Regards,
Alankar
------------------------------
Alankar Mordekar
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-04-23 12:59 PM
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
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-04-23 01:20 PM
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
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-04-23 02:53 PM
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 .
Best,
Satish Gunturi
Senior Consultant
------------------------------
Satish Gunturi
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-04-23 03:22 PM
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:
-
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.
-
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.
-
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.
-
Check the Blue Prism logs for any additional error messages or warnings. The logs may provide more details about the issue.
-
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.
------------------------------
Kirby
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
21-04-23 02:23 PM
Alankar,
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
------------------------------