(imported topic written by slybel)
I get this error after I push down a task.
It gets a completed status but is not succeeded.
Here is the command lines that I have used without success:
MSIEXEC /I Antidote_HD.msi /update “Maj_AntidoteHD_v4.msp” TRANSFORMS=Reseau.mst /qn
MSIEXEC /I Antidote_HD.msi /update “\server\directory\Maj_AntidoteHD_v4.msp” TRANSFORMS=Reseau.mst /qn
MSIEXEC /I Antidote_HD.msi /qn (even this plain one did the same thing)
thanks
(imported comment written by mmcgough91)
Sounds like file corruption or some other problem with the .msi. If you double-click the .msi will it launch?
One thing you can try is to turn on Windows Installer logging. Add:
/Lv* “path to logfilename.log”
to the end of your command line string to see if you get any more useful information in that log file. Usually 1619 is pretty vague but you might get lucky.
(imported comment written by slybel)
Yes, the MSI works fine when I run it from the download directory of the workstation.
Pushed it again with the /lv and it comes back as completed but does not install.
Here is the log file from the MSIEXEC:
=== Verbose logging started: 17/08/2010 9:57:40 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI © (18:E4)
09:57:40:115
: Resetting cached policy values
MSI © (18:E4)
09:57:40:115
: Machine policy value ‘Debug’ is 0
MSI © (18:E4)
09:57:40:115
: ******* RunEngine:
******* Product: C:\Program Files\BigFix Enterprise\BES Client__BESData\actionsite__Download\Antidote_HD.msi
******* Action:
******* CommandLine: **********
MSI © (18:E4)
09:57:40:147
: Client-side and UI is none or basic: Running entire install on the server.
MSI © (18:E4)
09:57:40:178
: Grabbed execution mutex.
MSI © (18:E4)
09:57:40:334
: Cloaking enabled.
MSI © (18:E4)
09:57:40:334
: Attempting to enable all disabled priveleges before calling Install on Server
MSI © (18:E4)
09:57:40:334
: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (1C:68)
09:57:40:428
: Grabbed execution mutex.
MSI (s) (1C:A4)
09:57:40:428
: Resetting cached policy values
MSI (s) (1C:A4)
09:57:40:428
: Machine policy value ‘Debug’ is 0
MSI (s) (1C:A4)
09:57:40:428
: ******* RunEngine:
******* Product: C:\Program Files\BigFix Enterprise\BES Client__BESData\actionsite__Download\Antidote_HD.msi
******* Action:
******* CommandLine: **********
MSI (s) (1C:A4)
09:57:40:490
: Note: 1: 2203 2: C:\Program Files\BigFix Enterprise\BES Client__BESData\actionsite__Download\Antidote_HD.msi 3: -2147287038
MSI (s) (1C:A4)
09:57:40:506
: MainEngineThread is returning 2
MSI © (18:E4)
09:57:40:506
: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI © (18:E4)
09:57:40:600
: MainEngineThread is returning 2
=== Verbose logging stopped: 17/08/2010 9:57:40 ===
Here is the log from bigfix:
At 09:54:22 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Relevant - _Deploy Antidote HD v4 (fixlet:4100)
At 09:54:22 -0400 -
ActionLogMessage: (action 4100 ) Action signature verified
At 09:55:18 -0400 -
ActionLogMessage: (action 4100 ) Non-Distributed - DownloadsAvailable
ActionLogMessage: (action 4100 ) starting action
At 09:55:18 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Using download manager collected file) download http://server.gc.ca:52611/Uploads/e4931eb5db3a6130e71c28b3347864a0cf4d2d92/Antidote_HD_v3_Windows.tmp (fixlet 4100)
At 09:55:58 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Command succeeded (evaluated true) continue if {(size of it = 804160357 AND sha1 of it = “e4931eb5db3a6130e71c28b3347864a0cf4d2d92”) of file “Antidote_HD_v3_Windows.tmp” of folder “__Download”} (fixlet 4100)
At 09:57:38 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Command succeeded extract Antidote_HD_v3_Windows.tmp (fixlet 4100)
At 09:57:49 -0400 -
Report posted successfully.
At 09:57:49 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Exit Code=1619) wait “C:\WINDOWS\system32\msiexec.exe” /i “C:\Program Files\BigFix Enterprise\BES Client__BESData\actionsite__Download\Antidote_HD.msi” TRANSFORMS=Reseau.mst /lv* “c:/log/logfile.log” /qn (fixlet 4100)
At 09:57:49 -0400 -
ActionLogMessage: (action 4100 ) ending action
At 09:57:49 -0400 - actionsite (http://server.gc.ca:52611/cgi-bin/bfgather.exe/actionsite)
Not Relevant - _Deploy Antidote HD v4 (fixlet:4100)
At 09:59:11 -0400 -
Report posted successfully.
Any help would be appreciated.
thank you.
Sylvain
(imported comment written by mmcgough91)
Hi slybel -
The WI log is unsurprisingly vague since the installation didn’t even get through the install execute sequence but it was worth a shot.
In the bigfix client log the only thing that looks off is the path to the .mst isn’t the same as the .msi. They can exist in different directories without causing a problem but I wonder if msiexec is finding the .mst. Try putting the full path to the .mst.
(imported comment written by slybel)
Changing the path for the MST gave my the same errors or non-errors.
(imported comment written by mmcgough91)
Is the error occurring on one client machine or many? What happens on that system (or others) when another .msi with a transform is executed via a fixlet?
(imported comment written by rdamours91)
I think I ran into this one before. Try prefacing the path of the .mst with it’s location as I believe it will look in the root of __download unless you tell it otherwise.
Here’s mine for a Office 2010 install
wait __Download\setup.exe /adminfile “{(pathname of client folder of current site) & “__Download\Updates\Office2010.msp”}”