Office 2004 Install quits after accepting license agreement

[Peter Stelman]

Hi.

I got Office 2004 Student Edition for my kids, who both have Powerbooks. I
installed it on one without any problem. When I try to install it on the
other, I can start the installation program, get to where the window pops up
where you "Accept" the license agreement, but when I click on "Accept" the
window whole installation window disappears and nothing else happens.

This is a Powerbook Ti 667MHz, 1Gb memory, about 30Gb free disk space. I've
run the Disk Utility to clean up permissions.

I also tried the 2nd install method, where you just drag it to the
Applications folder. When I do that, I can try to start up one of the
applications, which brings up the setup screen (like the first method does),
and it quits at the same spot.

I had already removed Office v.X from the computer, and after I was unable
to install 2004, I had no trouble re-installing v.X.

Has anyone else experienced this, and found a workaround?

Thanks.
Peter

 

[Shell VC]

I am having the exsact same problem. Its the same when you drag and drop
the whole folder and do a complete intall: when you go to start any
application the EULA comes up, you click accept then <POOF> it's all gone.
I plan on calling tomarrow, If I get it fiexed I'll post the solution :>

I am using S&T edt. On a Powerbook 867Mhz, and have seen more people
are having this problem... Haven't seen a fix yet though .

 

[Ramón G Castañeda]

I am having the exsact same problem. Its the same when you drag and drop
the whole folder and do a complete intall: when you go to start any
application the EULA comes up, you click accept then <POOF> it's all gone.
I plan on calling tomarrow, If I get it fiexed I'll post the solution :>
....

Try Repairing Permissions BEFORE and after the install.

Here's an excerpt from the Apple support site (links below):

It is absolutely essential to repair permissions before and after you run
any update that uses Apple's installer application!

Any installer that asks you for your password needs to do so, because it has
to write to files or folders that are usually not available to users other
than administrator or root. In order to do so the permissions have to be
exactly as expected by the installer application, otherwise it cannot finish
the installation and may even damage your system.

There are certain files whose permissions get more easily changed than
others. This is the reason why some installations are immune to this sort of
problems and others are very sensible - depending on which files and folders
get changed. You can tell by the number of trouble-reports on [the Apple]
discussion board.

Permissions can get broken by installations of third-party applications that
use Apple's installer app. This did happen e.g. with Norton Antivirus 9.0.0,
LimeWire and many others. If people use their OS 9 Classic folder to boot
into OS 9 natively (e.g. to install required firmware upgrades) they also
have a high probability of permissions being changed.

Furthermore there are many users who did simple upgrades since 10.0. 10.0
and 10.1 are known to do weird things to permissions.

So you might not need to repair permissions if you:
1. Never installed an application that asked for your password
2. Never did a simple upgrade
3. Never booted into OS 9 natively from the same system folder that you use
as Classic.


http://discussions.info.apple.com/WebX?13@@.68941aef/1

and

http://discussions.info.apple.com/WebX?128@@.6890d19d

Hope that helps.

 

[Mickey Stevens]

Try Repairing Permissions BEFORE and after the install.

Here's an excerpt from the Apple support site (links below):

It is absolutely essential to repair permissions before and after you run
any update that uses Apple's installer application!

For what it's worth, Microsoft Office doesn't use Apple's installer
application (it uses VISE), so I don't know if this would be an issue here.
It's a good idea to give it a try, though.

 

[meh]

For what it's worth, Microsoft Office doesn't use Apple's installer
application (it uses VISE), so I don't know if this would be an issue here.
It's a good idea to give it a try, though.

This is even less likely causing the problem you are mentioning, but
it is worth having a look at. May be helpful for other users in
general too:

http://docs.info.apple.com/article.html?artnum=25725