cancel
Showing results for 
Search instead for 
Did you mean: 

MS Excel VBO Error during Write Collection

Amruthasimplify
Level 5

Hi All,

I am getting the below error when trying to use the MS Excel VBO. Please suggest your thoughts on resolving the issue.

"ERROR: Internal : Could not execute code stage because exception thrown by code stage: Exception has been thrown by the target of an invocation."

Process Flow:

1. Read queue data using Get Report Data action

2. Close All Instance - MS Excel VBO (This stage results in the error: The RPC server is unavailable. which is handled in exception stage and resumed to following stages)

3. Create Instance - MS Excel VBO

4. Open Workbook - MS Excel VBO

5. Activate Worksheet - MS Excel VBO

6. Write Collection - MS Excel VBO (The collection can contain min 250 rows and max 5000)

At this stage, the process fails even after 3 retry with the error "ERROR: Internal : Could not execute code stage because exception thrown by code stage: Exception has been thrown by the target of an invocation."

 

3 REPLIES 3

david.l.morris
Level 15

First, check this Support article to make sure none of the documented reasons are your cause: BPE error "Exception has been thrown by the target of an invocation" when calling an action of the Excel VBO while running a Process : (blueprism.com).

So, here are some questions:

  • Are you ever able to successfully use Write Collection in other processes or other scenarios?
  • Can you share screenshots of your inputs and outputs and screenshot the actual data in the current values of those data items to help us guess what the issue is?
  • Have you tried this in a separate place with some test logic and a test file to see if it happens all the time?

In my experience, the error "Exception has been thrown by the target of an invocation" can just mean absolutely anything. It could mean you are referencing something that doesn't exist (sometimes), you have a corrupted install, or you forgot to buy eggs when you went to the store earlier. It's just the actual literally most unhelpful error you will ever get in your entire time working with automating Office products. This likely is not a Blue Prism issue. Instead, you are doing something in a wrong order, giving bad input, or there is a configuration issue on your machine.


Dave Morris, 3Ci at Southern Company

Thanks David for your response.

I am able to execute the stages when using small set of dataset like less than 60 rows. The collection contains more than 60 columns. However, the same stage is used in Production with 4k dataset which is working fine.

Apparently, these stages were working before. What has changed now is that I am now logging with different Windows ID since the old ID got deactivated.

 

Did you go to the Support article I linked to and verified that none of those things are the issue?


Dave Morris, 3Ci at Southern Company