Software Distribution - Adobe Reader XI action cout no changempleted b

(imported topic written by Braian)

Hello Everyone,

We are deploying Adobe Reader XI to all work Station, all completedbut some PC the adobe version didnot change.

Action Completed:

Completed prefetch AdbeRdr11000_mui_Std.tmp sha1:bd6b3cf442bd4ef56a63b4a6c5efeb69a47a4d77 size:137456365
http://SMITSTEM.smg.ph:52311/Uploads/bd6b3cf442bd4ef56a63b4a6c5efeb69a47a4d77/AdbeRdr11000_mui_Std.tmp

Completed extract AdbeRdr11000_mui_Std.tmp

Completed wait __Download\setup.exe /sAll /rs

client log:

At 14:33:05 +0800 -

Report posted successfully.

At 14:33:10 +0800 -

ActionLogMessage: (action 2266) Non-Distributed - DownloadsAvailable

ActionLogMessage: (action 2266) starting action

At 14:33:11 +0800 - actionsite (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/actionsite
)

Command succeeded (Prefetch download manager collected file) prefetch AdbeRdr11000_mui_Std.tmp sha1:bd6b3cf442bd4ef56a63b4a6c5efeb69a47a4d77 size:137456365
http://SMITSTEM.smg.ph:52311/Uploads/bd6b3cf442bd4ef56a63b4a6c5efeb69a47a4d77/AdbeRdr11000_mui_Std.tmp
(fixlet 2266)

At 14:33:36 +0800 - actionsite (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/actionsite
)

Command succeeded extract AdbeRdr11000_mui_Std.tmp (fixlet 2266)

Command started - wait __Download\setup.exe /sAll /rs (fixlet 2266)

At 14:33:36 +0800 - opsite2 (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite2
)

FAILED to Synchronize - General transport failure. - ‘http://SMITSTEM.smg.ph:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite2&Time=06Nov14:33:36&rand=34dced53&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709’ http failure code 404 - gather url -
http://SMITSTEM.smg.ph:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite2&Time=06Nov14:33:36&rand=34dced53&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709

At 14:33:37 +0800 - opsite3 (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite3
)

FAILED to Synchronize - General transport failure. - ‘http://SMITSTEM.smg.ph:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite3&Time=06Nov14:33:37&rand=f8041425&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709’ http failure code 404 - gather url -
http://SMITSTEM.smg.ph:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/opsite3&Time=06Nov14:33:37&rand=f8041425&ManyVersionSha1=da39a3ee5e6b4b0d3255bfef95601890afd80709

At 14:34:19 +0800 -

Report posted successfully.

At 14:34:22 +0800 - actionsite (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/actionsite
)

Command succeeded (Exit Code=1602) wait __Download\setup.exe /sAll /rs (fixlet 2266)

At 14:34:28 +0800 -

ActionLogMessage: (action 2266) ending action

At 14:34:28 +0800 - actionsite (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/actionsite
)

Not Relevant - Software Distribution - Deploy: AdobeReader11 (fixlet:2266)

Thanks,

Braian

(imported comment written by martinc)

Hi Braian,

Well to start with, Adobe is a pain in the backside! Always has been and probably always will be. :frowning:

If you look at the log you have attached, you will see the following line:

At 14:34:22 +0800 - actionsite (
http://SMITSTEM.smg.ph:52311/cgi-bin/bfgather.exe/actionsite
)

Command succeeded (Exit Code=1602) wait __Download\setup.exe /sAll /rs (fixlet 2266)

Notice that the exit code is 1602, which means that the setup.exe failed with a 1602 error. Now normally I would just look up the msiexec error code for 1602 (
ERROR_INSTALL_USEREXIT 1602 User cancel installation.
) but we know that is not correct. So googling a bit, I saw this older hit that might still be the reason why.

http://support.adminarsenal.com/entries/20468378-Error-1602-from-Adobe-causes-confusion-with-Windows-Installer-1602-originally-titled-How-does-a-user

In the end though, does it say that the fixlet was successful or failed? Each line in the action can say completed (because the action was started and did complete, ignore that it was an error), but the fixlet could have still failed.

Hope that helps.

(imported comment written by Braian)

Thanks martinc this is what im looking for.