I have a question regarding the latest UiPath.Excel.Activities update [v2.9.3].
Recently, our bots have started to stuck when working with Excel Application Scope.
In order to avoid such behavior, after each Excel Application scope activity a powershell script is called, which kills the excel process. (Description of a simplified version of the solution that is implemented and works
the description of UiPath.Excel.Activities v2.9.3 states the following
Fixed an issue that caused the Robot to sometimes get stuck without throwing an error when executing Excel activities, for example when an [Excel Application Scope] activity was used in a loop, or when multiple Excel Application Scope activities were used consecutively in the same process.
but now, my test flow, which I wrote to test the powershell script, [sometimes] throws the next exception.
**
Excel Application Scope: COM object that has been separated from its underlying RCW cannot be used.
**
that is, before v2.9.3 was installed, I had to call a script that kills the excel process.
Now, It looks like, I have to use a retry for each Excel Application Scope
@yaniketz
Can i assume that the previous version of the Excel activity is not causing major issues for you? Which version did work? 2.8.6 or lower?
Are you using multiple application scopes in your process?
Are you trying to kill the Excel Application Scope within your process or after the complete job is done?
Are you still using the powershell script to kill the process, or are you using the kill/stop process from the uipath activities?
Can you share the powershell script?
I’m not aware of this issue, so if you could explain more, we might can give you advise on what to do.
The excel activity isn’t depending on the studio or robot version indeed.
Regarding if you are using an old studio or bot version, be aware when you are using enterprise versions which are EOL, you won’t get any tech support from Uipath. They will advise you to upgrade.
Keep the product lifecycle in mind