Skip to main content

Hello Team,

I am encountering an error while attempting to run the bot in the production environment. The error message states that the file does not exist in the specified folder, despite the file being present in the folder path.

Please refer to the attachment for more details.

 

Regards,

Prashant M

Hi @Prashant M ,

The error message indicates that the file is not available in the specified location, resulting in the occurrence of an error.

To mitigate this issue, consider adding an "if" condition before attempting to open the Excel sheet. This condition should verify whether the file exists or not

If condition file exists 

This way, you ensure that you only attempt to open and process the Excel sheet if it actually exists, preventing unnecessary errors. If the file is not found, you can choose to log the error or display a message for reference


Hello @Tamil Arasu10,

No, the problem is even though the file exists in the respective path bot is unable to open it. we can find that file using the same path that is showed in error message.

 

Regards,

Prashant M


Hi @Prashant M,

The bot agent having the access for the file location ?


Hi @Tamil Arasu10,

How to provide permission to access the folders path by bot agent

 

Prashant M


If the Bot Agent is installed at system level, then as part of the configuration update, permissions for the Global Cache folder is set as follows:

  • Full access for System user and Administrator group.
  • Read, Execute, and List access for Authenticated users
  • Select an option to install the Bot Agent either at the system level or user level.
    • To install at the system level, select Anyone who uses this computer (all users)

      All users of the device can use this Bot Agent. However, users installing the Bot Agent must have administrator privileges.

    • To install at the user level, select Only for me (username).

      The Bot Agent will be available only to the individual user.


Hi @Tamil Arasu10,

We are still trying to solve the error with your extraction but facing the same issue.

 

Prashant M

 

 


Reply