topic Re: Excel issues in University Forum

Excel issues

blazino17 — Fri, 04 Apr 2025 05:09:58 GMT

I am having this error when trying toOpen workbook, please how can i resolve this? Internal : Could not execute code stage because exception thrown by code stage: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))

Re: Excel issues

Mukeshh_k — Fri, 04 Apr 2025 09:07:17 GMT

Hi @blazino17 - Is the 32-bit or 64-bit version of Excel installed on your machine? check the registry, open the registry editor to see if its pointing to correct path of excel.exe: Computer\HKEY_CLASSES_ROOT\TypeLib\{00020813-0000-0000-C000-000000000046}\1.9\0\

Or simply you can try repairing the office from control panel or reinstall excel on your machine just to check if it resolves the issue.

Re: Excel issues

blazino17 — Sat, 05 Apr 2025 08:11:51 GMT

I’ve confirmed that it’s a 32-bit system. The path wasn’t initially configured, but I’ve set it up now and restarted my PC. However, I’m still encountering the same issue. What should I do next?

Re: Excel issues

blazino17 — Sat, 05 Apr 2025 08:45:16 GMT

It is a 32 bit version of Excel.

Re: Excel issues

blazino17 — Sat, 05 Apr 2025 08:58:50 GMT

I just checked and confirmed that my Blue Prism installation is 64-bit, as it is located here:
C:\Program Files\Blue Prism Limited\Blue Prism Automate

Additionally, as I mentioned earlier, my Excel version is 32-bit. Could this mismatch between Blue Prism (64-bit) and Excel (32-bit) be the reason for the error I’m encountering? If so, how can I resolve this incompatibility issue?

Re: Excel issues

Mukeshh_k — Sat, 05 Apr 2025 10:36:07 GMT

Hi @blazino17 -

Is there any particular reason you're not using the default MS Excel VBO provided by Blue Prism? You can find it under: BluePrism Digital Exchange . I'm not 100% certain, but if you're using Interop services (Microsoft.Office.Interop.Excel) for your extended MS Excel VBO, then the bitness of Blue Prism and Excel(office) should match — otherwise, you might encounter the error you mentioned earlier. The native MS Excel VBO I believe is generally more forgiving in this regard. Try performing the same operation using the native MS Excel VBO and let me know if you're able to proceed.

I will ask @ewilson if he is able to confirm or provide more insights on the text highlighted in bold above.