Déploiement de ViaScreenSharing

[guillaume]

Bonjour tout le monde,

J'essaye de déployer l'application ViaScreenSharing mais je rencontre des difficultés et je ne trouve pas la raison du dysfonctionnement de mon installation.

Source du fichier : http://via.sviesolutions.com/Applicatio ... /Setup.msi

L'installation se lance et l'application apparaît pourtant bien installée sur le PC, cependant, dans l'interface de déploiement voici le retour que j'ai :
viascreensharing I unknow I failed (setup)

Code: Alles auswählen

(163)     [6] [mai 28 11:15:00:127] [viascreensharing]   ~~~~~~~ Start Sub ~~~~~~~  Sub_check_exitcode
(164)     [5] [mai 28 11:15:00:128] [viascreensharing]   comment: Test for installation success via exit code
(165)     [6] [mai 28 11:15:00:128] [viascreensharing]   Set  $ExitCode$ = getLastExitCode
(166)     [6] [mai 28 11:15:00:128] [viascreensharing]     The value of the variable "$ExitCode$" is now: "1603"
(167)     [6] [mai 28 11:15:00:128] [viascreensharing]   If
(168)     [6] [mai 28 11:15:00:128] [viascreensharing]     ($ExitCode$ = "0")   <<< result false
(169)     [6] [mai 28 11:15:00:128] [viascreensharing]   Then
(170)     [6] [mai 28 11:15:00:128] [viascreensharing]   Else
(171)     [5] [mai 28 11:15:00:129] [viascreensharing]     comment: Setup program gives a exitcode unequal zero: 1603
(172)     [6] [mai 28 11:15:00:129] [viascreensharing]     If
(173)     [6] [mai 28 11:15:00:129] [viascreensharing]       ($ExitCode$ = "1605")   <<< result false
(174)     [6] [mai 28 11:15:00:129] [viascreensharing]     Then
(175)     [6] [mai 28 11:15:00:129] [viascreensharing]     Else
(176)     [6] [mai 28 11:15:00:129] [viascreensharing]       If
(177)     [6] [mai 28 11:15:00:129] [viascreensharing]         ($ExitCode$ = "1641")   <<< result false
(178)     [6] [mai 28 11:15:00:129] [viascreensharing]       Then
(179)     [6] [mai 28 11:15:00:129] [viascreensharing]       Else
(180)     [6] [mai 28 11:15:00:129] [viascreensharing]         If
(181)     [6] [mai 28 11:15:00:129] [viascreensharing]           ($ExitCode$ = "3010")   <<< result false
(182)     [6] [mai 28 11:15:00:129] [viascreensharing]         Then
(183)     [6] [mai 28 11:15:00:129] [viascreensharing]         Else
(184)     [3] [mai 28 11:15:00:129] [viascreensharing]           Error: Fatal: Setup program gives an unknown exitcode unequal zero: 1603
(185)     [2] [mai 28 11:15:00:130] [viascreensharing]           Error level set to fatal
(186)     [6] [mai 28 11:15:00:130] [viascreensharing]           Process aborted
(187)     [6] [mai 28 11:15:00:130] [viascreensharing]   
(188)     [6] [mai 28 11:15:00:130] [viascreensharing]   ~~~~~~~ End Sub   ~~~~~~~  Sub_check_exitcode
(189)     [6] [mai 28 11:15:00:130] [viascreensharing]   
(190)     [6] [mai 28 11:15:00:130] [viascreensharing]   Process aborted

Je ne comprends pas bien ce qui provoque une erreur puisque l'application s'installe et semble fonctionnelle ?
Avez vous une piste sur cette erreur 1603 ?

Merci pour votre aide !!

[SisterOfMercy]

http://docs.netecm.ch/launcher/troubles ... codes.html

So you probably want to look in the msi logfile what has happened.

This is what I use from opsiscript:
"%SystemRoot%\system32\msiexec.exe" /qb-! /l*v "$LogDir$\$ProductId$-setup.log" /package "%ScriptPath%\files\Setup.msi" REBOOT=ReallySuppress

So on a testmachine, I would dump the msi file in c:\tmp, and run this:
msiexec /qb-! /l*v "c:\tmp\stupid-thing-setup.log" /package "c:\tmp\Setup.msi" REBOOT=ReallySuppress

[guillaume]

Tks a lot SisterOfMercy, going to try this ASAP and give a feedback to the community.

[SisterOfMercy]

Ok, I've downloaded the msi file, it's a stupid one.

It's a wrapper for a bunch of customactions. And the binary it contains is a pure innosetup installer.
I can see this because of these msi properties:
BZ.UINONE_UNINSTALL_ARGUMENTS /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
BZ.UIBASIC_UNINSTALL_ARGUMENTS /SILENT /SUPPRESSMSGBOXES /NORESTART
BZ.UIREDUCED_UNINSTALL_ARGUMENTS /SUPPRESSMSGBOXES /NORESTART

Extract the binary from the customactions (I used InstEd for this). Then create a setup.inf with the /SAVEINF=c:\setup.inf parameter when you install it on a test machine.

(In this case the setup.inf is really simple)

Code: Alles auswählen

[Setup]
Lang=english
Dir=C:\Program Files\Via ScreenSharing
Group=Via ScreenSharing
NoIcons=0
Tasks=

edit it to remove the line with Dir, and perhaps set NoIcons to 1 if you want to create your own shortcuts (recommended for programs that dump a lot of unneeded shortcuts... it even seems this program does not create shortcuts?)

Code: Alles auswählen

[Setup]
Lang=english
Group=Via ScreenSharing
NoIcons=0
Tasks=

Then use this in your opsiscript, for example:
"%ScriptPath%\files\setup.exe" /VERYSILENT /NORESTART /SUPPRESSMSGBOXES /DIR="$InstallDir64$" /LOADINF="%ScriptPath%\files\setup.inf"
See the opsi templates for more information.

[guillaume]

Hi SisterOfMercy,

Do you know Open Source and free alternative to convert in .EXE the .MSI file ? And in addition tha'ts going to be a little bit boring to me if i have to convert it each time i have to update it.
Going to think about it of find another way ... This is not what i expected from this apps (simple is better) !!

Tks a lot for searching a solution for me, really appreciated.

[SisterOfMercy]

Do you know Open Source and free alternative to convert in .EXE the .MSI file ? And in addition tha'ts going to be a little bit boring to me if i have to convert it each time i have to update it.

Lessmsi can not yet do it. The free version of InstEd can do it, but it is not open source.