IA18: Error at Install process

[mikKummerfeld]

Hey Guys,

I created a very small setup (exe) and I can reproduce the "Error" Message Bug at the install process.
UAC is set to requireAdministrator but its happens also with highestAvailabke.

The Error does only appear if ALLUSERS is set to TRUE AND if the Version number has a specific number.

- Project A: Product version: 4.0.5 (ERROR MESSAGE)
- Project B: Product version: 10.0.0 (NO Error MESSAGE)

4.0.5 will result in 4.0.5.0 ! 4 digits separated by .
10.0.0 will result in 10.0.00 ! 3 digits separated by . and double zero at end

This is the only difference. It is strange but I am quality assurance specialist and that combination causes the problems !

We WILL buy an update if the latest version has fixed this bug !

Attached projects and setups...

Please look and help, because we must roll out the version and my boss is really angry

Thanks !

[FrancescoT]

I'll check it as soon as I can.

Regards

[mikKummerfeld]

Thanks Francesco

[FrancescoT]

Dear Heiko,

I am not able to replicate any of the problems you reported and please note that I used the compiled SETUP.EXE included with your Archives.

In all honesty, I don't know if you had such issues when running the installers on a particular system that may have a specific configuration. You didn't specify anything about this. At any rate, I tested both packages on a Win 7 X64 system and both get installed fine for all users!

Furthermore, I used a limited user account to test the installers (UAC Enabled) and for what I see, both package get correctly elevated as expected.

For what concerns the product versions, these get properly reported under Add Remove Program.

prjA_version.png (28.89 KiB) Viewed 9323 times

prjB_version.png (23.24 KiB) Viewed 9323 times

Please note that under ARP the version number is Always limited to "major.minor.build", due the fact that Windows Installer uses only the first three fields of the product version (If you include a fourth field in your product version, the Windows Installer ignores the fourth field).

For what concerns the version number reported by the setup file, this will be Always reported as "major.minor[.build[.revision]]" or "major.minor[.maintenance[.build]]" (four fields format). So having "4.5.0" as version number, this will be Always reported by the system as ""4.5.0.0" with the respective file version property.

Regards

[mikKummerfeld]

In our Company the 4.5.0 one fails on Every machine. Win 7 64Bit, windows 10, windows server 2008.

The error only occures when Option 'shortcuts for all Users' is Selected. The behaviour with 4.5.0.0 is identical.

40.5.0 also works Fine! It Must be a bug at a Special constellation.

What can we do now ?

BTW: it is really Bad that the error Message does Not include Information about the Problem. An Information should be added at every error! Why is that Not included in Version 18 of a Product? We have Information at all error messageboxes in our products because its a Must have and it shows professionality.

[FrancescoT]

Dear Heiko,

I didn't use any special trick to install the packages you sent me. I just executed them on a test machine and as you can see from the screen shots with my previous reply, all your installers get installed correctly.

As it happens with any other process, the setup engine process can report detailed information about an error, exclusively when this gets raised within the same identical process. For example; you may run an external process from your installer, but if this last one fails without returning any error value, it'll be quite impossible to handle the error condition from the calling process.

I used a clean machine to test both packages, did you try to install your package on a clean machine (...where JUST the OS is installed)?

Which is the exact configuration of your test machine (OS, system version, service pack installed, system Language and so on)?

Regards

[mikKummerfeld]

German - Windows 7 64 bit - SP1

screenPC.png (50.83 KiB) Viewed 9311 times

[FrancescoT]

Dear Heiko,

I just tried to run your installer on a German version of WIN 7 sp1 x64 and I haven't found any problem.
As you can see it gets installed correctly.

win7sp1x64_german.png (92.37 KiB) Viewed 9237 times

Please note that I used a FRESH WIN 7 MACHINE, did you try to install your package on a clean machine (...where JUST the OS is installed)?

I have asked this already, but it seems that you missed my question.

I can only suppose that your problem it's directly related with the systems you used to run your tests, as for example, a conflict due an installed component.

Hope this helps you.

Regards

[mikKummerfeld]

We also tested on a clean machine

But why does it work/not work by changing the product Version. I want to understand this...And why only when ALLUSERS=TRUE?

[FrancescoT]

Dear Heiko,

obviously I cannot reply to your question without having your system. At any rate and if you are not able to replicate the problem using a Clean Machine, for sure it exists a problem with the other system.

Maybe it still exist an image of a previous version of your product ...and maybe, a damaged/altered image of it. Anyway, I am just supposing this and without having any possibility to prove it.

Regards

[Wolfgang Guertl]

Hi Heiko & Franceso!

Maybe the problem is related in the regional setting. Try to reproduce the case with reginonal settings Germany (current user AND Local System) or better with an german OS. (faulty comma separation)
@Heiko: Try to change regional Settings to en-US. Here in Austria we have to install an german SQL-Server with regional settings set to Germany.

Wolfgang

[FrancescoT]

Dear Wolfgang,

I used in fact a German Win 7 X64 OS where the regional settings was natively set to Germany.

Regards

[mikKummerfeld]

On englisch os no bug ! Only on German Os.
Clean machine also.

Still buggy with IA X5!