question

Mischa Spelt avatar image
0 Likes"
Mischa Spelt asked Phil BoBo edited

WebKit errors on Windows 7

A customer of ours was running FlexSim 17.0.2 on Windows 7 Enterprise edition and after upgrading to 17.0.5 (initially) got the following error:

On FlexSim 17.0.11, instead of error 182 they get error 5:

After continuing it later appears as the earlier seen error code 182 when opening the Experimenter.

On my recommendation, based on another post here at Answers, they have already installed the Visual C++ Runtime redistributable from https://www.microsoft.com/en-us/download/details.aspx?id=48145 but it did not fix the problem.

Although it seems like the problem may have been solved in 18.0.0, we would still like to know what more to install, if possible, to get FlexSim 17.0 running on their computer. It's worth noting that they are on a fairly locked down computer, so updates are strictly controlled and installing anything beyond that is quite a lengthy process for them.

FlexSim 17.0.11
flexsim 2017webkitvisual c++ redistributable for visual studio 2015.
webkiterror11.png (221.5 KiB)
webkiterror.png (186.1 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Phil BoBo avatar image
0 Likes"
Phil BoBo answered Phil BoBo edited

The problem still exists in 17.0 when you have both 17.0 and 18.0 installed?

If 18.0 is working correctly, then 17.0 shouldn't have any issues with missing dependencies; 18.0 should have installed them.

18.0 is built with the Visual Studio 2017 platform toolset (v141) though, instead of the Visual Studio 2013 toolset (v120) that 17.0 uses. Maybe that's making a difference?

The WebKit dlls haven't been updated since 16.1. FlexSim 17.0 and 18.0 are using the same version of WebKit.

I also don't understand why 17.0.2 would work and then upgrading to 17.0.5 would break it.

· 5
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Mischa Spelt avatar image Mischa Spelt commented ·

Yes, the message is still there despite version 2018 being installed. Issue has low priority because it does work in 2018, but if you have any brilliant insights later on feel free to share them!

0 Likes 0 ·
Mischa Spelt avatar image Mischa Spelt commented ·

@phil.bobo just realized of something I should have mentioned before: due to administrative constraints on their locked down PCs they will often script one version (in this case 17.0.2) through their IT department and then I just send them compressed versions of the newer releases that they extract somewhere on their machine. So are you sure that none of the newer installers (17.0.5 or 11) actually does anything relevant beyond copying files, such as registering DLLs or upgrading other dependencies outside the FlexSim program folder?

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Mischa Spelt commented ·

So is 17.0.2 still installed? And 17.0.5 is just a copy of the application installation directory?

When you say they "upgraded" to 17.0.5, what does that actually mean?

Is 18.0 installed? Or is it also just a copied application directory?

All of the installers do things relevant beyond copying files, such as registering dlls and installing dependencies. But I don't think that 17.0.2's installer is any different in that regard than 17.0.5.

Are all of the versions you are testing with the same platform (64-bit vs 32-bit)? Is the actual installed version the same platform as the copied directories? Do you have mismatched 64-bit and 32-bit files?

0 Likes 0 ·
Mischa Spelt avatar image Mischa Spelt Phil BoBo ♦♦ commented ·

I checked: 17.0.2 was properly installed, 17.0.5/11 were just copied to a clean directory. But the error sounds like a webkit issue and aside from that being a Windows component, you say that hasn't changed since 16.1. Also I think that this trick did work on another user's PC who was running Windows 10.

Obviously they did run the installer for 18.0.

0 Likes 0 ·
Show more comments