2003 Update Failure

[Miss Perspicacia Tick]

Hi,

Whenever I try to update Office 2003 I get "Installation ended
prematurely because of error.

I have tried running one update at a time. I have tried downloading
the adminstrative pack and run the patch from my hard drive. I still
got the error.

I have another computer with Office 2003 and have never had this
problem on it (Setting up a new computer).

I'd be glad of some advice.

Tom

Please adjust your timezone. According to your IP you're in Perth, Western
Australia, yet your time zone is set to -0700 (which is the default when you
install Windows, so I'm sure it's just an oversight). You're posting from
the future. It's in your own best interests as many won't reply to postdated
posts (other than to inform the poster their clock is wrong) and MS also
remove posted dated posts - as well as some servers as it's a tactic used by
spammers.

 

[Chad Harris]

Lindsay--

I'm not sure I'm up to the philosophical and poossibly pragmatic nuances Ms. Tick raises as to time zones, but I'll leave this to Ms. Tick and Martin Heidegger. I have a couple ideas that might help.

http://www.philosophypages.com/ph/heid.htm

1) Go to services by putting "services.msc" in your run box, and make sure you have the service "Office Source Engine" either on manual or automatic and started.

2) Put "eventvwr.msc" in the run box and check to see if you can find any additional error message information that could help.

hth,

Chad Harris

_________________________________________

 

[Lindsay Bryceson]

Hi,

Whenever I try to update Office 2003 I get "Installation ended prematurely
because of error.

I have tried running one update at a time. I have tried downloading the
adminstrative pack and run the patch from my hard drive. I still got the
error.

I have another computer with Office 2003 and have never had this problem on
it (Setting up a new computer).

I'd be glad of some advice.

Tom

 

[Chad Harris]

Tom--

I'm glad the reinstall worked things out for you . I have noticed with SP2 that I often have to start that service to put in an Office update--I suppose I could make it automatic, but I tend to want to be a minimilist with services when I don't actually need them running (like the ones to run Business Contact Manager's data base engine) to maximize speed and keep CPU from being sucked. It's bad enough Office and Office related applications default load wisptis.exe when installed for the tablet pen when most people aren't using a tablet pen, despite Mr. Gates' forcasts of steep reductions in tablet prices.

Make it a habit whenever you do have a problem that if the error isn't obvious enough to let you search the MSFT KB and nail it at http://support.microsoft.com to go to Event Viewer and under application and system categories stretch it out and see if you get anything that will help. It can be useful. The problem that MSFT has yet to solve and claims to be working with toward Longhorn release is to start giving error information to people on the street that's not hex. Hex is of value to a very limited group of people--perhaps the developers who have the tools to decode it. I don't see the people with the obligatory cell phone glued to their ear in supermarket checkout lines and generously making you part of their conversation talking in hex.

I hope someone can say why Word is starting "ahead of" Outlook or how to stop it. I think if you go to the microsoft.public.outlook group and post this, you may get a faster answer than this one.

It may have to do with Word as your email editor, but in that case Word usually comes up with Outlook for a time or I notice a little box when I fire up Outlook that it's starting. If I'm not going to use Word mail in that case (the version of Word used as Outlook's email editor, I just go to Task Manager by right clicking the taskbar and kill winword.exe (a two second workaround). The problem for you is to have Word designated as your email editor and not start. You can always stop this by going to Tools>Options>Mail Format tab and taking the check out of the box to use Word as your email editor, and then it shouldn't start up when you fire up Outlook, and then put the check in when you want to send a message with Word as your editor. This may work particularly if you spend a lot of time using Outlook for tasks other than to send email messages. Again, someone might have a better more simple solution.

hth,

Chad Harris

_________________________________________________________________________________________________________

 

[Lindsay Bryceson]

Thanks so much for that. I did as you said and ask the questino about Outlook/Word on the outlook newsgroup and we are making some progress.

Tom
Tom--

I'm glad the reinstall worked things out for you . I have noticed with SP2 that I often have to start that service to put in an Office update--I suppose I could make it automatic, but I tend to want to be a minimilist with services when I don't actually need them running (like the ones to run Business Contact Manager's data base engine) to maximize speed and keep CPU from being sucked. It's bad enough Office and Office related applications default load wisptis.exe when installed for the tablet pen when most people aren't using a tablet pen, despite Mr. Gates' forcasts of steep reductions in tablet prices.

Make it a habit whenever you do have a problem that if the error isn't obvious enough to let you search the MSFT KB and nail it at http://support.microsoft.com to go to Event Viewer and under application and system categories stretch it out and see if you get anything that will help. It can be useful. The problem that MSFT has yet to solve and claims to be working with toward Longhorn release is to start giving error information to people on the street that's not hex. Hex is of value to a very limited group of people--perhaps the developers who have the tools to decode it. I don't see the people with the obligatory cell phone glued to their ear in supermarket checkout lines and generously making you part of their conversation talking in hex.

I hope someone can say why Word is starting "ahead of" Outlook or how to stop it. I think if you go to the microsoft.public.outlook group and post this, you may get a faster answer than this one.

It may have to do with Word as your email editor, but in that case Word usually comes up with Outlook for a time or I notice a little box when I fire up Outlook that it's starting. If I'm not going to use Word mail in that case (the version of Word used as Outlook's email editor, I just go to Task Manager by right clicking the taskbar and kill winword.exe (a two second workaround). The problem for you is to have Word designated as your email editor and not start. You can always stop this by going to Tools>Options>Mail Format tab and taking the check out of the box to use Word as your email editor, and then it shouldn't start up when you fire up Outlook, and then put the check in when you want to send a message with Word as your editor. This may work particularly if you spend a lot of time using Outlook for tasks other than to send email messages. Again, someone might have a better more simple solution.

hth,

Chad Harris

_________________________________________________________________________________________________________

 

[Lindsay Bryceson]

Thanks Chad (and Ms Tick),

I did as you said and the services.msc was not started and so it is now
started.

I attempted an update again and it failed again.

I went into the event viewer as you said and there are dozens of failures.
The last one is thus:

The description for Event ID ( 0 ) in Source ( OfficeUpdateV3 ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
V3_2|511485|INSTALL|MSO11_1399_INTL||2004-07-15 16:29:05|9|FAIL|00000000|The
operation completed successfully.|.

It would be wonderful if you can blow me away again with your knowledge of
Microsoft internals!

Thanks

Tom (actually it isn't Lindsay ... Lindsay is the guy who is going to use
this computer when I finish setting it up for him).

Lindsay--

I'm not sure I'm up to the philosophical and poossibly pragmatic nuances Ms.
Tick raises as to time zones, but I'll leave this to Ms. Tick and Martin
Heidegger. I have a couple ideas that might help.

http://www.philosophypages.com/ph/heid.htm

1) Go to services by putting "services.msc" in your run box, and make sure
you have the service "Office Source Engine" either on manual or automatic
and started.

2) Put "eventvwr.msc" in the run box and check to see if you can find any
additional error message information that could help.

hth,

Chad Harris

_________________________________________

 

[Lindsay Bryceson]

Hi again,

Given that the message had stuff about the registry having incorrect
information I decided to reinstall Office. It worked, it went on and
updated without a problem.

I now have another problem (it was doing this before I resintalled Office).
Everytime I open Outlook Word opens too, in front of Outlook.

Any suggestions?

Tom

 

[Chad Harris]

Tom--

Please let me know if you are getting your Office Updates in okay now (of course you know that you can put that service on automatic and it should load started that way when you reboot. If CPU is scarce on a machine with less memory, then of course you can set any of those services to manual and just fire up services when you know you will need one of them for a specific reason and then it doesn't have to run in the background taking up its CPU/resources.

I want the Word/Outlook annoyance to go away for you, but right now we aren't sure exactly what is popping up to get in your face when obviously everyone who wants to use Word has to check that box but neither a Word doc or a new mail message with word the editor should spring up until you're ready to ask for it.

Best,

Chad Harris
_____________________________________________
Thanks so much for that. I did as you said and ask the questino about Outlook/Word on the outlook newsgroup and we are making some progress.

Tom
Tom--

I'm glad the reinstall worked things out for you . I have noticed with SP2 that I often have to start that service to put in an Office update--I suppose I could make it automatic, but I tend to want to be a minimilist with services when I don't actually need them running (like the ones to run Business Contact Manager's data base engine) to maximize speed and keep CPU from being sucked. It's bad enough Office and Office related applications default load wisptis.exe when installed for the tablet pen when most people aren't using a tablet pen, despite Mr. Gates' forcasts of steep reductions in tablet prices.

Make it a habit whenever you do have a problem that if the error isn't obvious enough to let you search the MSFT KB and nail it at http://support.microsoft.com to go to Event Viewer and under application and system categories stretch it out and see if you get anything that will help. It can be useful. The problem that MSFT has yet to solve and claims to be working with toward Longhorn release is to start giving error information to people on the street that's not hex. Hex is of value to a very limited group of people--perhaps the developers who have the tools to decode it. I don't see the people with the obligatory cell phone glued to their ear in supermarket checkout lines and generously making you part of their conversation talking in hex.

I hope someone can say why Word is starting "ahead of" Outlook or how to stop it. I think if you go to the microsoft.public.outlook group and post this, you may get a faster answer than this one.

It may have to do with Word as your email editor, but in that case Word usually comes up with Outlook for a time or I notice a little box when I fire up Outlook that it's starting. If I'm not going to use Word mail in that case (the version of Word used as Outlook's email editor, I just go to Task Manager by right clicking the taskbar and kill winword.exe (a two second workaround). The problem for you is to have Word designated as your email editor and not start. You can always stop this by going to Tools>Options>Mail Format tab and taking the check out of the box to use Word as your email editor, and then it shouldn't start up when you fire up Outlook, and then put the check in when you want to send a message with Word as your editor. This may work particularly if you spend a lot of time using Outlook for tasks other than to send email messages. Again, someone might have a better more simple solution.

hth,

Chad Harris

_________________________________________________________________________________________________________