EO products may start child process at runtime to perform certain tasks. For example, EO.WebBrowser always starts child process and then run the native Chromium browser engine inside the child process.
You will receive "Failed to start image manager" message when EO library can not create a child process at all, or created the process but can not establish any connection to it. You will receive "child process exited unexpectedly" when EO library created a child process, but it crashed before it is fully initialized. In either case a functioning child process can not be established.
The most common cause for this problem is third party AntiVirus/security software incorrectly identifies the child process as a threat and prevented it from being created or killed it. To verify if this is the case, you can try to temporarily turn off your AntiVirus/security software, check their logs or your system event logs to see if you can find any confirmation about the security software being the root cause.
Another common cause for this problem is due to Windows permission settings. For example, by default EO library uses rundll32.exe inside Windows's system32 directory to start child process, so if your current user does not have permission to read this directory, then process creation can fail.
To avoid these issues, you can try to enable EO Worker process first:
https://www.essentialobjects.com/doc/common/eowpThe easiest way to enable eowp.exe is to copy eowp.exe to the same directory as in your application's main executable.
You may also need to explicitly set eowp.exe (or your own customized executable file name) to your security software's whitelist in order to avoid such false alarm.
If you do not believe it is related to security software, please try to catch the runtime log and send the runtime log to us using code like this:
Code: C#
try
{
//do something that triggers the error
....
}
catch
{
string log = EO.Base.Runtime.GetLogs();
System.IO.File.WriteAllText(log_file_name, log);
}
Once you have collected the log, you can send it to us through
contact us page. Make sure you send the log file as an attachment instead of just copy and paste into the message details.