|
|
Rank: Member
Groups: Member
Joined: 9/1/2015
Posts: 23
|
I have a customer running our app that gets this error on 2 computers, I suspect something in their corporate IT is blocking something in EO. Based on the screenshot, the error could be happening where I EnableLargeAddressSpace. Version is 18.2.74.0. Below is the exception text.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Exception: Failed to create child process, Win32 Error: 5
at EO.Internal.jr.a(Exception A_0, Boolean A_1)
at EO.Internal.jr.b(String A_0, Boolean A_1)
at EO.Internal.jr.f..ctor(jr A_0, String A_1, String A_2, String A_3)
at EO.Internal.jr.a(j A_0, az8 A_1, String A_2, String A_3)
at EO.Internal.jr.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jr.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.jr.o.c()
at EO.Internal.jr.o.f()
at EO.Internal.jr.o()
at EO.Internal.jr.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jr.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.av9.b()
at EO.Internal.av9.a(WindowsIdentity A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.av9.c()
at EO.Internal.ct..ctor(WebView A_0)
at EO.WebBrowser.WebView.y()
at EO.WebBrowser.WebView.a(IntPtr A_0, Boolean A_1)
at EO.WinForm.WebViewHost.a(Object A_0)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
Trader
Assembly Version: 8.0.0.4
Win32 Version: 8.0.0.4
CodeBase: file:///C:/Users/therrald/AppData/Local/NRGSTREAM/Trader%208/Trader.exe
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
NRGSTREAM.Xtractor.Client
Assembly Version: 2.1.6946.18116
Win32 Version: 2.1.6946.18116
CodeBase: file:///C:/Users/therrald/AppData/Local/NRGSTREAM/Trader%208/NRGSTREAM.Xtractor.Client.DLL
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
EO.Base
Assembly Version: 18.2.74.0
Win32 Version: 18.2.74.0
CodeBase: file:///C:/Users/therrald/AppData/Local/NRGSTREAM/Trader%208/EO.Base.DLL
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
EO.WebBrowser
Assembly Version: 18.2.74.0
Win32 Version: 18.2.74.0
CodeBase: file:///C:/Users/therrald/AppData/Local/NRGSTREAM/Trader%208/EO.WebBrowser.DLL
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3282.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
System.Deployment
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.ServiceModel
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
EO.WebEngine
Assembly Version: 18.2.74.0
Win32 Version: 18.2.74.0
CodeBase: file:///C:/Users/therrald/AppData/Local/NRGSTREAM/Trader%208/EO.WebEngine.DLL
SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
System.ServiceModel.Channels
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Channels/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Channels.dll
System.ServiceModel.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Web/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll
System.Web.Services
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Services/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
System.IdentityModel
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.IdentityModel/v4.0_4.0.0.0__b77a5c561934e089/System.IdentityModel.dll
System.Net.Http
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
Yes. That seems to be the cause. By default we use Window's rundll32.exe to start child process. If their corporate IT blocks this then you may get this error. You can either try to get their corporate IT to update their policy or try the following workaround:
1. Make sure you are on the latest build (early build won't work);
2. Copy eowp.exe to the same directory as your main exe file;
This way our library will automatically use eowp.exe to start child process and no code change on your end is required. Note that you do need to use the latest build in order for this to work. Earlier builds won't automatically "pick up" eowp.exe.
Please let us know if this resolves the issue for you.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/1/2015
Posts: 23
|
What do you mean by latest build vs early build? EOWP.exe is in the same folder as my main exe file, I check to make sure it's there before enabling large address space.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
The latest build is the build that is currently on our download page with DLL version number 18.3.46.0. This is the only build that will automatically enable eowp.exe as soon as the file is present. In your case, since you have explicitly enabled it in your code, then it is not necessary for you to be using exactly that build.
If you are already using eowp.exe, then you need to check to make sure your application indeed can create a process from this file. You can try two things:
1. Start a command prompt and run eowp.exe directly from command line. This should simply print a message and does not give you an error;
2. Call Process.Start in your code to start eowp.exe and it should succeed as well;
Once those two succeed, you can try your application again and see if it works properly. We can then go from there if it still doesn't work.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/1/2015
Posts: 23
|
As this is at a customer's site, I can't really make a new version for him. Should I get him to try to manually run EOWP to see if he's able? Would that tell me if it's blocked?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
You can. That's what suggestion #1 in our previous reply is. However because ultimate the error comes from your application, not from the interactive user, so the ultimate test would still be your application. In another word, it is perfectly possible that the exe file will run fine interactively but not from within your application, that's why we also suggested #2 in our previous reply. You will need to pass both in order to troubleshoot further.
|
|
Rank: Newbie
Groups: Member
Joined: 3/1/2019
Posts: 2
|
I didn't see if anything was resolved with this issue. I am running into something very, very similar with Windows Server 2016 with an application. I am wondering what the root cause was? Environment or Application?  Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
The root cause for this particular issue is environment. However exactly what to check in you environment can depend on your application (specifically whether you use eowp.exe or not).
|
|
Rank: Newbie
Groups: Member
Joined: 3/1/2019
Posts: 2
|
eo_support wrote:The root cause for this particular issue is environment. However exactly what to check in you environment can depend on your application (specifically whether you use eowp.exe or not). We are not using eowp.exe. We are trying to troubleshoot the environment specifically at this time. Interestingly we have two apps using the same form call. One works as expected the other gets access denied. Logins are exactly the same. Also appears to only affect Windows Server 2016 Datacenter. Our testing in 2016 standard did not show this issue. I am wondering what exactly environment related may have affected the mentioned earlier. Is the use of eowp.exe the preferred method regardless of issues with rundll32? Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
noitchave wrote:I am wondering what exactly environment related may have affected the mentioned earlier. This is something you need to find out. The only thing we can tell you from our side is whether you are getting error code 5 on eowp.exe or getting error code 5 on rundll32.exe because we know when eowp.exe will be used and when rundll32.exe will be used. Exactly why you are getting this error on either file is something you must find out yourself. We have no way of knowing what security settings you have on your system and we are no expert on that either. This is purely a Windows administration issue and it's neither within the scope of our support nor within the scope of our expertise. noitchave wrote:Is the use of eowp.exe the preferred method regardless of issues with rundll32? There is no preferred method on our side. It has to do with your preference or which one is more convenient for you. Our product can work with either one: either eowp.exe or rundll32.exe, as long as your system is configured to allow either one to work. Your previous access denied error (error code 5) is an example of where your system is configured not to allow it work properly and you will have to fix this. Let's say this is the only issue, then is it easier for you to fix this access denied error for eowp.exe or is it easier for you to fix it on rundll32.exe? If it is easier for you to fix it on eowp.exe then use eowp.exe, if it is easier for you to fix it on rundll32.exe then use rundll32.exe. The point here is which one to use does not depend on us, it depends on which one works for you --- hope this makes sense to you.
|
|