Error opening workbook. Make sure Excel is installed, any idea?

Solution:
These are few approaches provided by UiPath team:

Approach 1 : It seems to be registry on that machine was damaged and is missing a key.

try the below steps:

  • Open regedit
    Go To HKEY_CLASSES_ROOT\Typelib{000‌ 20813-0000-0000-C000‌ -000000000046} . Delete the available node. probably 1.7 for office 2013
    Note: {000‌ 20813-0000-0000-C000‌ -000000000046} value changes with IID (in this case 208D5). You might need to refer google to verify the value.

Please refer to the below forum articles

Approach 2:
This issue usually occurs when OS is unable to find the required dll’s.

We recommend you to repair the Microsoft Office 2013
• Right-click the Start button (lower-left corner), and select Apps and Features on the pop-up menu.
• Select the Microsoft Office product you want to repair, and select Modify.
• Depending if your copy of Office is Click-to-run or MSI-based install, do the following.
Click-to-run
How would you like to repair your Office Programs , select Online Repair to make sure everything gets fixed, and then select Repair (The faster Quick Repair option is also available, but it only detects and then replaces corrupted files.)
MSI-based
In Change your installation , select Repair and then click Continue.
• Follow the instructions on the screen to complete the repair.

Approach 3# :
Modify a registry key named LoadBehavior. It needs to have its value changed from 3 to 9. It can be found in the following locations:

For 32-Bit Version of Windows
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Word\Addins\ACT7.OfficeAddIn
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Word\Addins\ActOffice2007Addin.Connect
HKEY_CURRENT_USER\Software\Microsoft\Office\Word\Addins\ACT7.OfficeAddIn
HKEY_CURRENT_USER\Software\Microsoft\Office\Word\Addins\ActOffice2007Addin.Connect

Kindly reboot after making the changes.
Thereafter confirm if you face same issue again.



Approach 4# : (If still the issue persist, please modify the workflow to avoid the issue )

Update the developed workflow. Code workaround would be , open excel application prior to invoking it.
This solution approach has worked for few of our client. ( Important )

Also, further suggestion’s

  1. If feasible change the Excel activities to use Workbook activities which do not need Excel to be installed
    Note: Make sure if you have not used Macros in the excel.
  2. As the issue is intermittent, please use retry scope to handle this error to retry the transaction when the failure happens.
3 Likes