If you have problems running Excel Command on Server

[dgudkov]

The “Excel command” action under the hood uses COM-automation to automate Excel operations. Unfortunately, it’s the only automation interface provided by Microsoft for Excel. It’s very outdated and has many limitations (e.g permissions, concurrency). It has problems running under the LocalService account (which is the default account for EasyMorph Server service) as well. The LocalService account lacks some obscure permissions, hidden folders, and God knows what else that is required by COM-automation compared to a regular Windows user account. That’s why the “Excel command” action can work on your Desktop, but can stop working on the Server.

What to do in this case:

1. If you have the Enterprise edition of EasyMorph Server, try using a separate worker that runs under a Windows user account. This option is not available for the Team edition. The Server Admin Guide explains what is a worker and how to configure one.

2. If running “Excel command” is crucial for your Team edition of Server, try changing to Server service account from LocalServer to a Windows user account. This is a big change that can affect folder permissions required by other tasks so make sure you understand the implications. The Server Admin Guide explains how to change the Server service account.

3. Don’t run workflows with “Excel command” on Server. Run them in EasyMorph Launcher, if possible.

Of course, Excel must be installed on the Server for options 1 and 2 above to work.

When we designed the “Excel command” we knew about the limitations of COM-automation and we anticipated many issues with it on EasyMorph Server. Nevertheless, we’ve added it because it can be extremely useful despite all the issues.

Other topics on the same issue:

Running VBA Macros from the Excel Command action

With the release of EasyMorph version 5 comes an amazing new action called Excel Command which allows for running precreated Excel macros – subroutines or functions – from with a workflow, using the “Run VBA macro” setting. This option opens up new potentials for processes outside the scope of EasyMorph like applying complex formatting, inserting or formatting objects (charts, pivottables, shapes, etc.), or triggering an Excel-based reporting process. The sky’s the limit when you can have a co…

Excel command VBA not working

Hi, Strange case here. When I use RDP to log in to the EasyMorph server (Administrator account) the process works fine with the Excel VBA command. But when run as a job it fails. It does not seem to open the Excel file. Excel has been installed of course (Office 2021 Home edition). The EasyMorph service uses account ‘Local Service’. And this account has been given acces to the Excel file. I’ve tested with worker Administrator and Local service. Both fail with the same error. This is the loggi…

Excel command error on EM-server

Hi! We’re unable to use the function “recalculate workbook” on our EM-server. because of the following error. Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)). **Location:** action "Excel command", table "data_template.xlsx" When researching the error we found a MSDN forum that suggested to create the directory “C:\Windows\SysWOW6…

[Jake_DiSanto]

FYI - One thing I noticed when working with this excel command action is that if the excel workbook has any datasets, pivot tables, queries that have Refresh Upon Opening Workbook CHECKED, bring back an error. Once I unchecked that setting on any/all datasets, pivots, queries it worked!

Also, I noticed that Recalculate workbook action only recalculates formulas and does not trigger a RefreshAll action on any datasets, which is incorrectly stated in another posting.