Snapin isseus ...

[robza]

Hello,
my config:
fedora 22 64bit
fog Version: 6120
I have problems with installing snapins.
I have created snapin for msi package:

Task is finished with windows error 1603 (net helpmsg 1603 “Fatal error during installation”)
But when I run this task

from cmd with elevated priviliges (Run cmd as administrator) task is done with success.
Client runs win7 pro.
FOGService in services.msc in column “Log ON as” is local system.
My question:
why I can’t use fog service to install msi package.
Regards

[Tom Elliott]

@robza Is this with ALL msi’s or just this particular MSI? What’s the error code being returned when it attempts to install?

[robza]

@Tom-Elliott other msi’s works fine. I just installed 7-zip msi package and Return code was 0.
Error code for this particular is 1603

[Tom Elliott]

@robza That I’d say is then the snapin itself. You created the MSI? See I see the same type of problem with Java, but that’s just java’s own msi files being problematic. You may have better luck, with this particular msi, using an Active directory GPO.

[robza]

@Tom-Elliott this msi package is provided by Kaspersky Lab. GPO not available.
Hmm I’m going to contact with Kaspersky support.
Any other ideas?
Regards

[Joe Schmitt]

Change Snapin Run With Args to

/quiet /i

[robza]

@Jbob
still the same error 1603

[ITSolutions]

@robza Have you tried removing the “/qn” from the msi as the /quiet should be the same thing and /quiet is the normal msi style?

Also can you install the file using that command manually on the machine?

[ITSolutions]

@robza In your original screenshot I just noticed that the MSI file has spaces in it, can you remove the spaces? This would cause msiexec to error finding the file. 1603 is a common catch all error on MSI files, so this could be the issue also.

[robza]

@ITSolutions from cmd with elevated priviliges (Run cmd as administrator) task is done with success.
Spaces in msi package are removed

and /quiet command used but still got 1603 error.
Regards

[Thiago]

@robza
Try put \ before server ip in SSInstall settings… \172…

[robza]

@Thiago still the same 1603 error after your advice:

Regards

[Thiago]

@Thiago said:
Try put \\ before server ip in SSInstall settings… \172…
sorry for the typo… the forum “eat” other \

[robza]

@Thiago no change, still 1603 error occured.

[Thiago]

@robza
Try to use log verbosity option of msi. Maybe something appears in log file.

C:\Windows\System32\msiexec.exe /i Kaspersky_Network_Agent.msi /l*v C:\msi.log SSINSTALL="172..." /qn

[robza]

@Thiago below log
0_1453980384596_ccc.txt
This script works fine when I start cmd as administrator (cmd with elevated priviliges).
Kaspersky service answered that is connected with UAC (User Account Control) or “operating system permissions” - what ever thats mean.
Regards

[Thiago]

@robza
if i could see properly, the error begins here:

MSI (s) (7C:E0) [12:20:19:742]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI756D.tmp, Entrypoint: CheckRequirements
Pocz\Ufffffffftek akcji 12:20:19: CheckRequirements.
CustomAction CheckRequirements returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Sorry, but i can’t help with this specifically.
Do you have this agent in a exe version? Exe has hability for silent install too.
Last time that this occurred to me, i removed the options for silent install and send snapin task to host, at the computer client i saw that it asked for elevated privileges (that was my issue).

[robza]

@Thiago no difference after removing /qn - 1603 error generated in fog log.
I have folder with few files and there is setup.exe, but after starting there is installation wizard, where is necessary to define few variables. If installing msi there is xml file used.
Tomorrow I’ll try with exe.
Regards

[robza]

I have found solution but in my opinion is half-hearted success. After disabling UAC scripts installed with code 0.
Regards

[Jaymes Driver]

Why not code in a script to disable the UAC (or disable it by default in the image) and use a script to re-enable after your snap in is complete.

This way, yes it’s still half hearted, but it seems the issue is on the windows side of things rather than FOG, but you won’t be leaving your systems UAC disabled.