Unable to open Axiom forms within the Desktop Client
When opening an Axiom form in Axiom Rolling Forecasting, you may see either of the following errors:
- Failed to create child process, Win 32 Error: 5
- Failed to start image manager
These errors can occur when attempting to open an Axiom form within the Axiom Desktop Client (either the Windows Client or the Excel Client). This applies to client-created Axiom forms, as well as product-delivered Axiom forms such as Month End Dashboard or Update VCC Threshold Table.
Axiom Rolling Forecasting uses an embedded browser to display Axiom forms within the Desktop Client. This embedded browser is run using an executable file located in the client installation directory. The executable file allows the rendering of web-based content within the Desktop Client, using Microsoft .NET Framework and Essential Objects.
If the executable file for the embedded browser is blocked by third-party antivirus software, the "failed to create child process" or "failed to start image manager" errors listed in the summary occur, and the Axiom form does not open.
Example error when the embedded browser is blocked by antivirus software
The embedded browser is only used when opening an Axiom form within the Desktop Client. The issue does not occur when opening an Axiom form within a stand-alone browser, or when opening the spreadsheet source file for an Axiom form within the Desktop Client.
To resolve this issue, the administrator of your antivirus software needs to add the following file to the list of exclusions: eowp.exe
Organizations that use Cylance Software have seen this issue, and have used the following steps from their help website to whitelist the application: How to Safelist a File. This has been the most common cause of the issue, and the most common fix.
In earlier versions of Axiom Rolling Forecasting, the executable file was named eopw.exe, which contained an accidental misspelling of the original file name. Starting with Axiom Rolling Forecasting version 2019.2, the executable file uses the Essential Objects name of eowp.exe. If your organization had already created an exclusion rule for the old file name, they must update the rule for the new file name when upgrading to Axiom Rolling Forecasting 2019.2.
Once the executable file for the embedded browser has been excluded from antivirus scanning, you can open Axiom forms within the Desktop Client.
|
Category |
Reports |
|
Applies To |
Axiom Rolling Forecasting version 2018.3 and up |
|
Tags |
Axiom Forms, Error, AntiVirus, EOWP |
|
Issue Number(s) |
N/A |
