Rank: Newbie
Groups: Member
Joined: 4/23/2018
Posts: 2
|
We are using EO.WebBrowser library version 2017 for WinForms application. Its working as expected for most of our users but it is crashing for some of the users stating error "Failed to create child process, Win32 Error: 1260". We've connected to user's computer and gather following system information.
Operation System: Windows 8.1
.Net Framework Version: 4.5.2
No Group policies in place
EXCEPTION: Failed to create child process, Win32 Error: 1260
TYPE: System.Exception
STACK TRACE: at EO.Internal.ji.a(Exception A_0, Boolean A_1)
at EO.Internal.ji.a(Int32 A_0, String A_1, Boolean A_2)
at EO.Internal.ji.f..ctor(ji A_0, String A_1, String A_2)
at EO.Internal.ji.a(j A_0, a0g A_1, String A_2, String A_3)
at EO.Internal.ji.a(Boolean& A_0, String[] A_1, String A_2, String A_3, String A_4, String A_5)
at EO.Internal.ji.a(String[] A_0, String A_1, String A_2, String A_3, String A_4)
at EO.Internal.ji.o.c()
at EO.Internal.ji.o.f()
at EO.Internal.ji.o()
at EO.Internal.ji.a(Boolean& A_0, String[] A_1, String A_2, String A_3, String A_4, String A_5)
at EO.Internal.ji.a(String[] A_0, String A_1, String A_2, String A_3, String A_4)
at EO.Internal.aqh.a(String A_0, String A_1)
at EO.Internal.awk.f()
at EO.WebEngine.Engine.Start()
at EO.Internal.cm..ctor(WebView A_0)
at EO.WebBrowser.WebView.x()
at EO.WebBrowser.WebView.b(IntPtr A_0, Boolean A_1)
at EO.WebBrowser.WinForm.WebControl.a(Object A_0)
Any help resolving this issue is much appriciated.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi, Windows error 1260 means "Windows cannot open this program because it has been prevented by a software restriction policy". This means some software restriction policy on the target computer has set to prevent a specific process from being executed. By default, our library uses Windows' system file rundll32.exe to create child process. So if you have a policy that prevent rundll32.exe from being instantiated under certain circumstance (for example, from any non-MS application), then you will run into this error. You can try to resolve this issue from one of the two fronts: 1. Change your software restriction policy to remove the restriction; 2. Change your code so that it no longer uses rundll32.exe. For option 1 you can search online for more details about software restriction policy. For option 2 you can see here for more details: https://www.essentialobjects.com/doc/common/eowp.aspxNote that this option does not exist in early builds. So you may need to update your DLL version in order to use this option. Additionally, depending on how your restriction policy is configured, merely switching from rundll32.exe to eowp.exe may not resolve the problem. For example, if you have a policy that prevent any unsigned application from creating child process and your application is not signed, then no matter what exe your application use to create child process (through our library), it still won't work. In that case you will have to find out the specific policy and modify the policy instead. Thanks!
|
Rank: Newbie
Groups: Member
Joined: 4/23/2018
Posts: 2
|
Thank you very much for the quick reply. Distributing the eowp.exe along with the application has worked for us:)
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Great. Glad to hear that it works for you!
|