- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Microsoft Office issues
Various errors may occur when you build or run automations with Microsoft Office applications, especially Excel.
-
One of the following errors occurs when you are configuring an activity in the StudioX profile and you select Indicate in Excel in the Plus
menu:
- Error opening workbook. Make sure Excel is installed.
-
Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)).::
- An Excel activity runs and the following error occurs:
Error opening workbook. Make sure Excel is installed. Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type 'Microsoft.Office.Interop.Excel._Application'.
- The following error occurs when a Word activity runs:
Error opening document, make sure Word application is installed. If already installed, an Office Repair may be required.
- The following
error occurs when an Outlook activity runs, or when you are
configuring an activity in the StudioX profile and you are
trying to access Outlook data such as folders or accounts
from the Plus
menu:
Property accessor 'Account' on object 'UiPath.Mail.Activities.Business.OutlookApplicationCard' threw the following exception:'Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'...
Microsoft Office installation issues may result in incorrect COM Interop configurations in the Windows registry. For example, this may happen if:
- Microsoft Office is installed, then removed, and then an older version of Office is installed.
- With Office already installed, Skype for Business is installed, which comes with different Office components than the ones in the already installed version of Microsoft Office.
The Repair Tool for Microsoft Office checks the Windows registry and attempts to repair common issues with Microsoft Office applications that cause errors when building automations. In addition, you can use it to run Microsoft's Office repair tool. The tool generates a repair plan that you can either run on your machine or export and deploy on other machines.
- Select Home (Studio Backstage View) > Tools > Apps > Repair Tool for Microsoft Office. The repair tool opens.
-
Tabs at the top of the window enable you to view each available action. The following tabs are available::
- A tab for each Microsoft Office application: Excel, Outlook, Word, and PowerPoint.
-
Office Repair, with information about the Microsoft Office repair tool for Office 2013 and newer versions.
For each action, the tool automatically detects the application installation path, version, and whether it is a 32-bit or 64-bit version. Verify that the information is correct and make adjustments if needed.
-
Click Generate Repair Plan. A list of actions to perform is displayed.
- Select which repair actions to perform. By default, all recommended repair actions are selected. To view details about an
action, click
next to it.
-
Select what to do with the repair plan:
- Run Repair Actions - Run the actions on your machine. If you select this option, the results are displayed on the lower part of the window.
- Create .REG file - Generate a
.regfile see a full list of repair changes. - Export Configuration - Create a JSON file with the repair plan that you can then deploy on other machines.
Every time a repair plan runs, a backup of the previous Windows registry configuration is saved. If you encounter unexpected issues after running the Repair Tool for Microsoft Office:
- Open the tool again and select the Backup tab. A list of repairs that have run is displayed.
- Click Restore next to the repair whose registry changes to undo.
