If you have problems running Excel Command on Server

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: