Failed to start image manager error

[aaronssh (Aaron Shaffer)]

I have a new install of 11.2.200.38 with the Demo database. On a client machine I am having an issue when not logged in as a Windows admin.

When logged in as a regular (non-admin) Windows user, I cannot log in using the Kinetic view because of this error (see screenshot). However I can open Classic view without issues.

When logged in as admin, both Kinetic and Classic view work ok. Normally that suggests a file rights issue, but I have already granted all users full read/write access to the Epicor client folder. Any ideas what is causing this or how to fix it?

[jgehling (Jeff Gehling)]

Hmmm,

Is this computer running anti virus software? I’d try the steps here:

https://www.essentialobjects.com/doc/common/eowp.aspx

[aaronssh (Aaron Shaffer)]

It does but if it was a Symantec issue then

1. it would alert me
2. it would happen to both admin and non-admin users
   … so it is not that.

[jgehling (Jeff Gehling)]

This is the only KB on this issue:

KB0110522

Other than that def seems local to the specific config of the PC being used.

[aaronssh (Aaron Shaffer)]

Tried disabling Symantec completely but no change.
Tried totally removing and re-installing Epicor client but no change.

I guess I’ll open a ticket with Epicor.

[aaronssh (Aaron Shaffer)]

Well I figured it out before Epicor replied. We use Windows AppLocker which by default blocks .EXE files which are not in Program Files. Since Epicor deviates from Microsoft’s recommendation for all programs to be installed to the Program Files folder and instead installs to the root of C:\ , it needed a manual whitelisting.

As to why this wasn’t whitelisted like older version of Epicor already are, that specific file is signed by “Essential Objects Inc” instead of Epicor. Anything signed by Epicor is already allowed in our environment, but because they are adding third party code we had to whitelist that third party too.