AFP548 - Topic: Office 12.2.1 update failing

This topic has 11 replies, 9 voices, and was last updated 15 years, 7 months ago by alantrewartha.

Viewing 12 posts - 1 through 12 (of 12 total)

Author

Posts
August 11, 2009 at 10:07 pm #376836

thegooch49
Participant

Hi everyone, has anyone gotten the 12.2.1 update to run properly in instaDMG? We have an enterprise copy of Office, so it’s not serialized. So I put it in the image. I have an installer for 12.2.0. When I put 12.2.1 to install, it does not run. I’m left with 12.2.0 still. The .pkg log shows:

“Installing Quit Microsoft Applications”

So I take that this is a metapackage, that runs a sub routine that first quits any open MS applications. The problem is, it’s not running the other routines. Anyone gotten around this yet?

Thanks!

August 12, 2009 at 12:39 pm #376839

rossmg
Participant

I’m not sure if you’ve looked at this already, but the Office 12.2.1 update doesn’t update the version numbers on Word, Excel, or PowerPoint. If you launch one of those apps and click on the About menu entry, Latest Installed Update will show 12.2.1 if it installed correctly.

Sorry if you already knew that!

August 12, 2009 at 1:23 pm #376841

dead2sin
Participant

I’ve always had speed issues with the office updates (specific parts would hang) so I’ve started repackaging Office 2008 with all the updates. This makes my images build faster and I *know* its updating correctly. I use Composer 7 for it.

Hope that helps,

Nate

August 12, 2009 at 6:51 pm #376842

Chris George
Participant

There’s also a droplet/shell script combo in the “My Downloads” section of this site that claims to patch Office updaters so that they work with InstaDMG. Doesn’t look like it’s been verified for use with the most recent updates to Office and/or InstaDMG, so use with caution.

[url]https://www.afp548.com/filemgmt/index.php?id=84[/url]

August 12, 2009 at 7:01 pm #376844

thegooch49
Participant

Thanks Chris, I didn’t know that something like that existed. I just downloaded it. The GUI app won’t launch. I looked at the shell script that is included (which I’m guessing does the work for the GUI applescript app) and it just removes the volume check, and deletes a binary called ‘find_office’. It looks like it won’t modify the update package like needed. Thanks though!

-Jeff

August 12, 2009 at 8:40 pm #376847

jasonkstupski
Participant

Jeff –

I can verify the same issue happening with my latest build – the log just says “Installing Quit Microsoft Applications….”

Any help would be much appreciated!

Thanks,
Jason

August 18, 2009 at 10:40 pm #376895

jasonkstupski
Participant

I ended up creating a snapshot package of the 12.2.1 update using InstallEase, and it worked just fine.

Thanks,
Jason

August 19, 2009 at 5:24 pm #376903

Anthony Reimer
Participant

Just for the record, I had no problem applying SP 2 (12.2.0) and 12.2.1 in my build once I patched the installers with the PatchOfficeUpdate droplet (as I normally do). My original installer is a repack of 12.1.x (I wanted to get rid of Entourage, among other things), so YMMV.

Anthony

August 21, 2009 at 12:34 am #376921

knowmad
Participant

I am also having no issues with patchofficeupdate and 12.2.0 and 12.2.1
it just works….

August 26, 2009 at 9:18 am #376962

trondah
Participant

Seems like a problem with the Volume License Key version. I can’t get it to work either. Had no problems with the first release of Office 2008 with all updates on top.

August 31, 2009 at 8:36 pm #377019

knowmad
Participant

{nevermind}
replied to wrong thread… in the wrong way… sorry

September 17, 2009 at 3:04 pm #377179

alantrewartha
Participant

i’m using v211 instaDMG, and i’m finding that the MS office updates (sp1 sp2, 12.2.X) all crap out on me because the ‘quit running applications’ steps in the installers fail, and that’s the ‘preflight’ step, so the whole mpkg is abandoned.

to hack this do

find /path/to/updater.mpkg -name “quit_apps.app”

which will show you where the various quit apps are located, and what you are after are the perl scripts called ‘preflight’. comment out (with a #) BOTH lines near the end that start ‘exec’

you could probably blank the whole script in each case TBH, but this seems more clinical.
Author

Posts