Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

EO.WebBrowser not working under Windows 10 update 1809 Options
hmireault
Posted: Tuesday, October 9, 2018 2:06:39 PM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
Hello,

A few of our clients have updated to Windows 10 update 1809. After doing so, they started getting a freeze when using the EO.WebBrowser controls. This happens every time, but only on machines that updated to 1809. Since then, Microsoft has pulled back the update, but the clients are still experiencing the issue since they already updated.

We were able to reproduce the issue using the test application code provided in the samples when installing EO.Total. Is this a known issue?

Regards.
eo_support
Posted: Tuesday, October 9, 2018 3:42:22 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Hi,

We do have other customers reporting this issue on a much older version. We have no way of verifying it since Microsoft has already pulled the update. So we will have to wait until the "final" update is pushed.

In the mean time you can follow these steps and see if it resolves the issue for you:

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

Thanks!
hmireault
Posted: Wednesday, October 10, 2018 8:06:19 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
We tested using eowp.exe and it seems to work well on machines running 1809. For now we'll let our users use this as an option. Thanks for the help!

Regards,
eo_support
Posted: Wednesday, October 10, 2018 9:31:57 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Thanks for the update. We will keep a close eye on this issue and as soon as the final update is available, we will check again.
hmireault
Posted: Thursday, December 13, 2018 8:29:37 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
Hello,

We have a client now that gets a blank screen when using eowp.exe over rundll32, so the workaround doesn't work for them. Is there any news regarding a fix for Windows 10 update 1809?

Regards.
eo_support
Posted: Thursday, December 13, 2018 4:51:06 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
hmireault wrote:
Hello,

We have a client now that gets a blank screen when using eowp.exe over rundll32, so the workaround doesn't work for them. Is there any news regarding a fix for Windows 10 update 1809?

Regards.


We have no way to address that now because we are not able to get 1809 in our environment yet. As soon as it is pushed to us we will visit this issue again.
hmireault
Posted: Friday, December 14, 2018 7:49:55 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
Ah, I thought they released the update since the client said they had just upgraded, my bad. Thanks once again.
Bortis
Posted: Thursday, January 24, 2019 6:25:32 AM
Rank: Newbie
Groups: Member

Joined: 1/24/2019
Posts: 3
As 1809 is now available again is there any more news on a fix for this?

Thank you
Julie Allen
Posted: Friday, January 25, 2019 7:31:25 AM
Rank: Newbie
Groups: Member

Joined: 6/26/2017
Posts: 5
Any updates on a fix for the windows 10 1809 update? This is a serious problem for us.
We have an Outlook COM Add-in which uses the EO browser. Updating to 1809 (which is most definitely available and has been for some time - ) causes Outlook to hang for about 15 minutes before writing to our log file:

Error; GlobalErrorHandler.HandleException; ; Failed to resolve LoadLibrary. - EO.Base - at EO.Internal.jq.b.d()
at EO.Internal.jq.b.a(bae[] A_0, String A_1, String A_2)
at EO.Internal.jq.a(Boolean& A_0, bae[] A_1, String A_2, String A_3)
at EO.Internal.jq.a(bae[] A_0, String A_1, String A_2)
at EO.Internal.jq.o.c()
at EO.Internal.jq.o.f()
at EO.Internal.jq.o()
at EO.Internal.jq.a(Boolean& A_0, bae[] A_1, String A_2, String A_3)
at EO.Internal.jq.a(bae[] A_0, String A_1, String A_2)
at EO.Internal.av5.b()
at EO.Internal.av5.a(WindowsIdentity A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.av5.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)

Copying eowp.exe into our programs directory allows Outlook to start but makes our add-in inactive and we cannot enable it. We have thousands of users who are very likely to upgrade to the latest version of windows 10 in the very near future and we are extremely concerned about this failure of the EO browser.

The windows 10 update is available here:
https://www.microsoft.com/en-us/software-download/windows10?irgwc=1&OCID=AID681541_aff_7794_1246483&tduid=(ir__v13mtdsa6wkfrhltxcm9pyfc6f2xhoknljmtlqvb00)(7794)(1246483)(%288f1c84af5dfb2a4936ab8c2bf2c2b43d%29%28266696%29%281503186%29%2884412X1536482X391e54d52a5ee7336766e7fcad14b472%29%28%29)(8f1c84af5dfb2a4936ab8c2bf2c2b43d)&irclickid=_v13mtdsa6wkfrhltxcm9pyfc6f2xhoknljmtlqvb00
eo_support
Posted: Saturday, January 26, 2019 8:52:38 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Hi,

Based on our own test as well as feedbacks from other customers, the issue can be resolved by either:

1. Explicitly setting EO.Base.Runtime.EnableEOWP to true;
-- or --
2. With the latest build from our download page (2018.3.46.0), copy eowp.exe into the same folder as your main exe file or in your bin folder;

Either option will switch EO library into using eowp.exe instead of rundll32.exe which should solve the problem. As to issues reported in this thread:

1. For hmireault: We are not able to reproduce the problem mentioned earlier where a user switched to eowp.exe but still not working;
2. For Julie Allen: We have not tested outlook plugin. The most common reason for Outlook to disable the plugin is it crashes every time when it loads. You can try to handle EO.Base.Runtime.Exception event to log the event to see if you can find more information about it;

We are still investigating the exact cause of the issue when eowp.exe is not used.

Thanks!
Bortis
Posted: Monday, January 28, 2019 7:26:04 AM
Rank: Newbie
Groups: Member

Joined: 1/24/2019
Posts: 3
Sadly, our add-in doesnt even load so we cant even handle the exception.
eo_support
Posted: Monday, January 28, 2019 11:42:20 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Bortis wrote:
Sadly, our add-in doesnt even load so we cant even handle the exception.


You will need to troubleshoot this part first. Whether your add-in load successfully would depend on what you are trying to do at load. For example, if your code does nothing at load, then there is no reason for it to fail. Likely wise, simply attaching an event handler should not cause any problem so there is no reason that you can't attach the event handler. Once you attach the event handler and then if you try to do anything additional (for example, creating a WebView), then it may fail and cause your add-in not to load. And that's exactly why you need to attach the exception event handler first so when this happens you will have more information to troubleshoot.
Bortis
Posted: Tuesday, January 29, 2019 7:07:07 AM
Rank: Newbie
Groups: Member

Joined: 1/24/2019
Posts: 3
Many apologies, wasnt pointing to latest EO dlls! Its looking good now. Thank you very much.
eo_support
Posted: Tuesday, January 29, 2019 9:49:19 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Bortis wrote:
Many apologies, wasnt pointing to latest EO dlls! Its looking good now. Thank you very much.


Great. Glad that you got it working.
hmireault
Posted: Monday, February 4, 2019 7:43:29 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
eo_support wrote:
Hi,

Based on our own test as well as feedbacks from other customers, the issue can be resolved by either:

1. Explicitly setting EO.Base.Runtime.EnableEOWP to true;
-- or --
2. With the latest build from our download page (2018.3.46.0), copy eowp.exe into the same folder as your main exe file or in your bin folder;

Either option will switch EO library into using eowp.exe instead of rundll32.exe which should solve the problem.


Is there any plan to support the browser without EnableEOWP / eowp.exe on Windows update 1809 or is this the expected solution for the foreseeable future?

Regards.
eo_support
Posted: Monday, February 4, 2019 8:09:13 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Yes. Our up coming 2019 release will support 1809 without EnableEOWP.

Thanks!
hmireault
Posted: Monday, February 4, 2019 8:25:34 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
Thank you, that's great news.
hmireault
Posted: Tuesday, February 19, 2019 9:39:32 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 34
I confirm it now works without EnableEOWP, thanks!
eo_support
Posted: Tuesday, February 19, 2019 10:18:03 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 20,984
Great. Thanks for confirming the fix!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.