We have 2 organization on orchestror Testenv and Default(production).
I’m using RE framework and I’ve kept config.xlsx and other template file in desktop folder. This works fine on local and testenv.
When I publish the process from studio it will directly create a process on Testenv and everything works fine here. It will read the config file from desktop folder where Ive given the path. Now i want to publish this process on Default which is my production environment. As i can’t directly publish the process to Default, I uploaded the nupkg package and created the process for my bot. From here bot is not able to read the config.xlsx aswell as other template file from the desktop folder. It gives the error like “Read range (Settings and Constants sheets): The workbook does not exist”
(System exception at initialization: Failed opening the Excel file *******. Possible reasons: the file is corrupt, the file is already used by another process or you don’t have permissions to open the file. at Source: Excel Application Scope)
If i keep the file inside my project it works fine but not on external folder.
How to resolve this access issue and how can i directly publish workflow to organization “Default”?
@manjula_rajendran Make sure connect your studio to default folder. Click on the small drop down besides default then you can see list of Orchestrator folders that you have access to
Also, can you share the path of the config that you have provided in the code
Yes, i’ve proper paths. I’ve set this paths in Assets and accessing through it. For Config file i’ve directly given the asset name in Get asset activity.
@manjula_rajendran Can you please go to the studio and see to which folder it was connected . If you open the studio at the bottom you can see the folder name (look below screenshot). Share that screenshot here
When i publish it published to TestEnv organization directly. My question was
how can i directly publish to “Default” organization instead of Testenv
For “Default” organization i’m currently uploading the nupkg packages to create the automation process. But here it is telling files are not accessible.
Error : System exception at initialization: Failed opening the Excel file *******. Possible reasons: the file is corrupt, the file is already used by another process or you don’t have permissions to open the file. at Source: Excel Application Scope