+1
Started

FixInsight 2015.4 xml log files are cut off

Lübbe Onken 10 years ago updated by Roman 10 years ago 9
The xml files created by FixInsight 2015.4 are cut off at some random location. I have not found out why. The number of messages doesn't seem to be an issue, because it happens with files that are 50 lines long or > 500 lines long.

Example:
<file name="xxxxx.pas">
    <message line="85" col="3" id="W508">W508 Variable is assigned twice successively</message>
    <message line="102" col="3" id="W508">W508 Variable is assigned twice successively</message>
    <message line="140" col="17" id="W512">W512 Odd ELSE-IF condition (review lines 140 and 144)</message>
    <message line="574" col="7" id="W521">W521 Return value of function 'ParseFixVarUnion' might be undefined</message>
    <message line="799" col="3" id="W521">W521 Return value of function 'ParseBLOCK' might be undefined<
It is just cut off in the middle of an xml tag.
It's getting even stranger. I have uninstalled 2015.04 and installed 2015.03upd1. When this is in "trial" mode, everything works as expected. After loading the license, FixInsightCL suddenly fails with:
Exception EOleException in module FixInsight.Services.dll at 0020202C.
Uninstall/Reinstall 2015.04 and the XML files are cut off. No matter whether its trial or registered.
Uninstall/Reinstall 2015.03upd1 in trial mode and I can at least work.
Under review
Hi Lübbe,

Could you please try to replace FixInsightCL.exe in 2015.04 installation with this one
https://www.dropbox.com/s/teg5lm4v59spaws/FixInsightCL.exe.zip?dl=0 ?

Sorry no, it still fails with the version that you placed in the dropbox. The log files look exactly the same.
Do you mean it still cuts off the file, or it fails with that AV?
The files are still cut off with that 2015.04 version from the drop box.

The A/V only occurs, when I install 2015.03upd3 *and* load the license. 2015.03upd3 works without license. 2015.04 works with and without license.

Is it possible that 2015.04 has changed something (not backwards compatible) in the registry?!?
Nope, nothing was changed in the registry...

Do you use the latest build of 2015.03upd1? Please try to download it from the website.
http://sourceoddity.com/download/FixInsight_2015.03upd1_setup.exe
I remember it had a problem with licensing, but this was fixed.
Hi Roman,
looks like I didn't have the latest version of 2015.03upd1. The one I dowloaded from your server now doesn't crash anymore.

Do you see what we are doing here? We are comparing 2015.03upd1 with 2015.03upd1. I have to install one of the two in order to find out which is the correct one. This is an absolute no go.

Please Roman, please: insert a build number or a repository revision into your exe and dll file version and into your installer, so that everybody can find out which version is installed by checking the installations in windows control panel and/or by looking at the details of one of the installed files properties.

I'll make this an extra "ticket" in userecho to remind you :)
I will do this Lübbe, I promise. Sorry about that :(