EZCA - Resh.exe cannot initialize. - SimForums.com Discussion

Hi All !

Over the past few days, we have studied the problem of Resh.exe.

To date, the cause of the failure of the initialization of Resh.exe is not completely studed , but I found a few controversial points in a code of EZCA about the initialization sequence Resh.

Now I present for test 2 versions of EZCA (.28 build).

#1 - "Time out extended"

#2 - "Resh launch first"

You can download thise versions below.

These are the same versions with the functions like .27 build , but with different algorithms for initializing Resh.

After installing .28 build, probably your internet Brandmauer will ask for access to EZCA.EXE. Agree by clicking Yes.

Test both versions of .28 build. Tell me, is there an initialization error Resh.exe?

Resh is an important bridge between the simulator and the EZCA. Without Resh.exe, the .27 version is not possible.

Now, if an resh initialization error appears, then the continuation of EZ work will not be possible and EZ will be closed. This is done specially, because EZ can not work without Resh.

I ask you to carefully approach the topic, because the problem is not pleasant to users and requires quick elimination, but for this I need to collect as much data as possible. I hope that you will help me to do this as soon as possible.

Download #1

2.6.0.28 "time out extended"

Downlоad #2

2.6.0.28 "Resh launch first"

Remember , you can roll back to .27 build. Just download it then install.

If the Resh initialization problem does not appear in the .28 build, be sure to tell which build of 0.28 the problem was resolved.

(Edited by Marniftarr)

===================

Hi,

I have tried every variation of the instructions given setting admin rights for the ezca.exe and the resh.exe programs but always get this message in the sim.

I have tried running P3D as administratorand not.

This was all working fine, now it isn't. Basically the cameras do not work at all.

I am using Windows 10 and have added the EZCA2 folder as an exclusion for windows defender.

Please advise.

Hi All

I have the same problem and have tried everything I can think off with no luck. Please help. Thank you.

Best regards

Hi All
Guys, I think the problem may be in the last Windows update. Specific cases should be addressed individually. You have to write to support (the form at the bottom of the page).
http://www.ezdok-camera.com/troubleshooting

Before doing this, check one option - disable firewall in Windows Defender, sometimes it helps to solve the problem with the initialization Resh.exe.

Hi,

I have tried every variation of the instructions given setting admin rights for the ezca.exe and the resh.exe programs but always get this message in the sim. Plese help

Thank you

Hi Nick,

the problem is a recent windows update indeed. Specifically KB4056892.

I experienced the exact same problem as described but I solved it by deinstalling KB4056892. Of course this only a temporary solution - it would be great to get a small update for Ezca from you guys so that Ezca runs with the latest version of windows again.

Regards

David

P.S.: I contacted the support form last weekend but didnt get a reply since...

I have the same problem but do not have KB4056892 installed, however I only have it with the FSL A320. It has only happened in the last few days, before that it was working fine.

Yes I uninstalled that update and all is working fine now. Thank you for that.

Best regards

Same issue here, appears to only affect FSL A320 and not on every launch.

Support ticket sent.

I think the problem with FSL320 can be caused by an incorrect entry in the file EXE.XML. Can be broken syntax. Look at the topic with a similar problem, there is described the solution.
http://www.simforums.com/forums/reinstalling-ezdok-2_topic59437_post378124.html#378124

Nickbe wrote:

I think the problem with FSL320 can be caused by an incorrect entry in the file EXE.XML. Can be broken syntax. Look at the topic with a similar problem, there is described the solution.
http://www.simforums.com/forums/reinstalling-ezdok-2_topic59437_post378124.html#378124

Whilst I did not have the specific issue linked I rebuilt the exe.xml and thus far have a 100% load success. Hopefully it holds out.

Same problem.

Regards

Asad

Think I may have a solution to the problem, at least in my case.

If I load Active sky before I load P3D, I get ezca.exe and the resh.exe program message. If I run P3D first, place aircraft at a field then start Active sky I have no problem. I can only assume that it is something to do with Active sky trying to get top billing in the EXE config.

I now plan my flights while the aircraft is at the gate, or fly X-Plane which has a lot less issues.

Hi,

This thread (7th post down) has just cured my problem

http://www.simforums.com/forums/reinstalling-ezdok-2_topic59437.html

barrywells found his exe.xml didn't look right, so he edited it,

Mine was missing the Trackir5 section, so I copied it from Barrys post, and it has cured my problem, so worth a try.

good luck

Steve

Hi,

any news from the developers regarding the problem with the windows update? My exe file is correct, the problem just occurs with the named windows version.

Regards
David

Hi, I'd like to have news too. Got the same problem aswell with Win 10 64b up to date.

I have already done a clean uninstall/reinstall of Ezdok with Fligh1 wrapper and update to latest version.

regards

Pascal

Just confirming it is the KB4056892 update.. uninstalling it does fix the issue. I also checked the exe.xml file and all is correct there.

Thank you for finding the cause of this 777-Pilot, of course windows keeps trying to reinstall the update.. had to uninstall it 3 times so far. So a developer released update that fixes this would be great.

Hi, All!
Guys, Marniftarr is aware of this issue. We are thinking of a solution. Wait a while and Marniftarr will report here on how we will solve this problem.

My Fix was short lived, it was worked for 2 days Cry

Guys hello everyone.

Now, with some users through the mail directly I solve this issue.

First, I need to understand the reason for this behavior EZ.

I can not change the code in rush style ,because everything worked fine. But there are some thoughts on this problem.

Now it became clear that in some way is affected sequence of launch add-ons.

This week I want to change some parts of the code regarding the interaction of resh.exe with ezca.exe and I want to change the startup sequence of resh.exe.

I analyzed code again . and now the sequence of the launch I have some doubts.

Only I can change sequence of launch resh.exe. But if you give even more information about this problem, it will speed up the bug fix.

Either way, be patient, the EZ team is working on this problem.

Hi Marniftarr

I am not sure if any of this information is of any help but this is what I have found

I have just reformatted and installed a fresh downloaded copy of windows 10, so I do not have KB4056892 installed as an update.

Windows 10 professional

Asus Z170

1080ti

Prepar3D 4.1

Orbx various regions

PMDG NGX & 747

UK 2000

FSGX2010 Mesh

The main thing I have looked at is exe.xml which editing cures the problem for a short while

My original xml.exe after reinstalling everything including Trackir and Ezdok

<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

-<Launch.Addon>

<Name>EZdok camera addon2</Name>

<Disabled>false</Disabled>

<Path>C:\Program Files (x86)\EZCA2\ezlauncher.exe</Path>

</Launch.Addon>

</SimBase.Document>

Adding the missing trackir section cured the problem for 2 days

<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

-<Launch.Addon>

<Name>TrackIr5</Name>

<Disabled>False</Disabled>

<Path>C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe</Path>

</Launch.Addon>

-<Launch.Addon>

<Name>EZdok camera addon2</Name>

<Disabled>false</Disabled>

<Path>C:\Program Files (x86)\EZCA2\ezlauncher.exe</Path>

</Launch.Addon>

</SimBase.Document>

Today I noticed (3rd line down) <Filename>dll.xml</Filename> not exe.xml so I changed that to exe

I still get the same error message (not after closing Prepar3d as before but in the prepar3d window) but the everything works

Steve

Here's what I found so far :

I have FSX-Steam and P3V4.1 installed on my rig.

Under FSX-SE, Ezdok works ! Here's a screenshot :

Under P3D4.1, I got Resh not initialising message after 5 seconds when the flight has loaded :

Here's a screenshot of Ezdok status then :

So, looks like a simconnect problem no ?

Anyway, here's my EXE.XML from P3D :

<?xml version="1.0" encoding="utf-8"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>exe.xml</Filename>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>EZdok camera addon2</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\EZCA2\ezlauncher.exe</Path>

</Launch.Addon>

<Launch.Addon>

<Name>as_btstrp_config_manager</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>as_srv\as_btstrp_config_manager.exe</Path>

</Launch.Addon>

<Launch.Addon>

<Name>AutogenConfigurationMerger</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\SceneryDesign.org\AutogenConfigurationMerger\AutogenConfigurationMerger.exe</Path>

</Launch.Addon>

</SimBase.Document>

My rig : Asus Z170 Hero

I7 6700k

16 Go Ram

GTX 1080

Win10 64b v1709 16299.192 with KB4056892 installed

Hope it can help you !

Regards

Pascal

Here are my findings:

After KB4056892 has reinstalled, EZCA started for about 3-4 times properly in the sim. It took a bit longer then normally to start after the flight has loaded but it worked. After those 3-4 times however, it started to show the same resh.exe error again.

Then I deinstalled KB4056892 again and EZCA loads without problems.

Hope this helps.

David

P.S.: For all those of you were KB4056892 keeps reinstalling: Search for the tool "wushowhide". With that tool you can stop Windows from downloading and installing a certain update everytime you shutdown your PC.

Hi All !

Over the past few days, we have studied the problem of Resh.exe.

To date, the cause of the failure of the initialization of Resh.exe is not completely studed , but I found a few controversial points in a code of EZCA about the initialization sequence Resh.

Now I present for test 2 versions of EZCA (.28 build).

#1 - "Time out extended"

#2 - "Resh launch first"

You can download thise versions below.

These are the same versions with the functions like .27 build , but with different algorithms for initializing Resh.

After installing .28 build, probably your internet Brandmauer will ask for access to EZCA.EXE. Agree by clicking Yes.

Test both versions of .28 build. Tell me, is there an initialization error Resh.exe?

Resh is an important bridge between the simulator and the EZCA. Without Resh.exe, the .27 version is not possible.

Now, if an resh initialization error appears, then the continuation of EZ work will not be possible and EZ will be closed. This is done specially, because EZ can not work without Resh.

Download #1

2.6.0.28 "time out extended"

Downlоad #2

2.6.0.28 "Resh launch first"

Remember , you can roll back to .27 build. Just download it then install.

If the Resh initialization problem does not appear in the .28 build, be sure to tell which build of 0.28 the problem was resolved.

Hi Marniftarr

#1 - "Time out extended"

Ran P3d everything worked, no error messages

Shut down computer and cold boot (not just Restart)

ran p3d again everything worked no error messages.

#2 - "Resh launch first"

Ran P3d everything worked, no error messages

Shut down computer and cold boot

Ran p3d this time ezdok did not work and was not in the addon menu but still no error messages.

restarted p3d ezdok this time in addon menu so had to right click to get ezdok view

Reinstalled #1 - "Time out extended" again and everything seems to work after several shut down and cold boot, but no error messages with either.

So for me at the moment #1 has fixed my problem.

thank you for your work

Steve

Well .. Continue testing. I need your reports.

I thought it just affected the FSL A320 but it just happened on default plane with Active Sky. Ran P3D without activesky, loaded up default plane and error again, this time came up with exception code but dissapeared before I could copy it.

Will try the above builds and report back.

Guys, please do not write here the reports of the version .27 ..

Write only reports of .28 builds after testing.

Please report here ...

Working or do not working #1 ?

I will make official update to .28 build.

Hi !

#1 Time out extended" works perfectly for me now.

But I didn't have enough time to test #2.

Nanolab wrote:

Hi !

#1 Time out extended" works perfectly for me now.

But I didn't have enough time to test #2.

Hi,

it's the same for me.

Thank you!

Second day, still #1 - "Time out extended" working perfect

Ok , Guys , thanks.

I will release .28 build in Tuesday or Wednesday.

Can confirm that for me the timeout version works.

Thank you for the continued support with this product.

hank you for the continued support with this product.

===

The product is developing. Now many details are under secrets.

#2 - "Resh launch first" solved the issue for me so far.

Regards,

Asad

asadkamal,

#1 - do not working ?

My turn to have experienced the issue and, after contacting the EZDOK assistance, they immediately advised me to apply the 2 patches (beta 0.28), the first one and, if no success, the second one.

Hopefully the Times Out patch solved my issue. I tested all my referenced aircraft and everything is back.

Thanks

The Timeout patch made the trick - EZDOK is working again.

Torben

TorbenJA wrote:

The Timeout patch made the trick - EZDOK is working again.

Torben

Where did you get the timeout patch ...??

Terblanche wrote:

Where did you get the timeout patch ...??

Note that this was for v2. Big smile