Skip to main content

I am running same Bot on 2 different runner machines accessing 2 different files, but when bot is running on one machine, if I run same bot on different machine accessing different input file, it is giving me Database Connect Error, file already in use. 

How is this possible, Can somebody help me with this issue.

Following is the error message:

“219 Error message: 'InputFile1' name already in used. Please provide other session name.”

I am replying here because I am having a similar issue : 

  • I am running 2 bots (same bot just a different parameter) on the same virtual machine (but 2 different users), and I notice some issue with ClipBoard action (Error I receive : Problem extracting value from clipboard) and the bots don’t work as expected. It’s like if the clipboard is messed up when 2 bots are running in the same time, even if normally each user would have each own clipboard
  • Of course when I run each bot alone they work fine

I am new to Automation Anywhere and I don’t know if I missed something about running 2 bots in the same VM with different users, this was weird


Hi @Faiz Khan,

 

The error message you’re encountering, “219 Error message: ‘InputFile1’ name already in use. Please provide another session name,” typically occurs when a session name is duplicated within your Automation Anywhere A360 bot. Here are a few steps to resolve this issue:

  1. Check Session Names: Ensure that each session name within your bot is unique. If you have multiple sessions, each one should have a distinct name.
  2. Review Bot Code: Go through your bot’s code to identify where ‘InputFile1’ is being used and change it to a unique session name.
  3. Update Session Names: If ‘InputFile1’ is used in multiple places, update those instances with a new, unique name.

Root Cause: The bot may have failed before disconnecting the previous session (InputFile1), and this issue might need to be handled in the error handler. 

 

Best Practices:

  • Always create a unique session name.
  • Avoid using the same session name within the same task.

If these steps help you resolve the problem, please mark it as answered. If you need further assistance or have other questions, feel free to ask!

 


Reply