[wpkg-users] upgrade adobe acrobat reader 8.1.2 to 8.1.3

[K.E.Jones at bton.ac.uk]

Hi,

- -----Original Message-----
- From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-
- bounces at lists.wpkg.org] On Behalf Of Thomas Stegbauer
- Sent: 06 November 2008 08:43
- To: Leon Hedding (ICT); wpkg-users at lists.wpkg.org
- Subject: Re: [wpkg-users] upgrade adobe acrobat reader 8.1.2 to 8.1.3
- 
- Am 06.11.2008 07:42, schrieb Leon Hedding (ICT):
- > I have found that installing Adobe 8.1.3 already uninstalls 8.1.2.
- >
- 
- but even then i get
- 
- 2008-11-06 01:07:53, DEBUG  : Executing command :
- \\wpkg\wpkg\packages\adobe\AdbeRdr813_de_DE.exe /sAll /rs
- 2008-11-06 01:07:55, ERROR  : Could not process (upgrade) package
- 'Adobe
- Acrobat Reader' (adobeacrobat8):|Exit code returned non-successful
- value
- (-529697949) on command
- '\\wpkg\wpkg\packages\adobe\AdbeRdr813_de_DE.exe /sAll /rs'.
- 2008-11-06 01:07:55, DEBUG  : Restoring previous environment.
- 
- greetings
- Thomas

 That doesn't look like a "normal" exit code to me. A quick play with
Windows calculator says -52969697949 is E06D7363 in hex. Google'ing that
brings up a lot of different articles suggesting that it might actually
be an exception code rather than an exit code. If it's an exception then
it's most likely that something is happening deeper beyond WPKG's scope.


 The articles all seem to centre around an MSI/Windows Installer issue
and
I know that Adobe are now using windows installer stuff created by
InstallShield.
InstallShield basically creates MSI files nowadays and wraps them in its
own
awkward self extracting .EXE file.

 Perhaps the best move is to see if you get Windows Installer to produce
a log and check that out?

 Turning on Windows Installer logging
(http://support.microsoft.com/kb/223300)

 Once logging is on it should create MSIXXXXX.log files in the 'temp'
directory.
The 'temp' directory will be in the user profile if you running the
install at
user login or in the Windows temp folder if you're running WPKG at start
up)

 You'll probably find a bunch of files in those directories so clean the
temp
directories before attempting the re-install so you've got a clean
slate. You'll
also probably find you have more than one MSIXXXXXX.log files after the
reboot.
(It's a side effect of Windows Installer checking packages to see if
they're
"advertised" for users to install)

 If you have more than one log file in there then use a text editor on
them
and find the one that contains references to the Acrobat reader.

 If you're feeling brave you can probably find the spot in the log file
where
it goes wrong otherwise e-mail it to me and I'll see if I can find the
error :-)

 Usually doing a search for "error" will get you close to the bit where
its gone
wrong and it only takes a bit of hunting to spot the real error code :-)
 
Hope this is useful,

 Keefy

PS: Don't forget to turn logging off. It's nice information to have but
it
does add a good few seconds to startup/login times.

PPS: I have a vague feeling that there is a known issue with the Adobe
installer
that needs you to forcibly uninstall one of the versions. It's been a
long time
since I had a look at that though...

-
-----------------------------------------------------------------------
- --
- wpkg-users mailing list archives >>
- http://lists.wpkg.org/pipermail/wpkg-users/
- _______________________________________________
- wpkg-users mailing list
- wpkg-users at lists.wpkg.org
- http://lists.wpkg.org/mailman/listinfo/wpkg-users