Windows Office 2000 installer tries to execute everytime I compose or respond to a message

  • Thread starter Thread starter Spin
  • Start date Start date
S

Spin

In OWA, Every time I try to compose or respond to a message, the Windows
Office 2000 installer tries to execute and asks for the CD. Unfortunately,
this Office 2000 problem has come up again even after all the updates to
Office 2000.

Also I am having trouble logging out. When I hit the logoff button, it
brings up a sign-in screen asking for ID & password again. Whether I cancel
it or fill it in and type OK, it then gives me a screen that says "access
denied". I never get a screen which says that logout was successful.
 
I have the same problem here...

From what I've seen most people refer to MS Q257886 that basicaly
tells you to give it the Office 2000 pro CD so it will shut up or just
cancell and it will stop bothering you.

This is crap because our system are configured using an image that was
created in another office. The installation dialog box does not give
you the option to point it to the installation files. It just wants to
go automaticaly to where it was originaly installed from. In my case
the original install point was on a server in an office on the other
side of the country! Letting it try to install over internet is
impossible....I've let the system sit for hours and it wasn't even
near 1/4 completed.

Further more clicking cancel just bring the dialog box up 15 times
before it "gives up" and let's you work as expected. This also happens
everytime you use OWA and click on the reply button.

I've even tried upgrading the system to Office 2003 and stupid OWA
still asks for the Office 2000 pro installation files!!!

I'm sure there is a fix out there somewhere for this...I'm assuming it
will be to edit the registry keys that contain the original install
point to something like the CD or a local server with the installtion
files...

This is not a great fix for me either as I have 15,000 systems that
have recently been upgraded to Exchange 2003 OWA....way to go
Microsoft!!!

I hope this helps people out there...
 
SirOssis said:
This is not a great fix for me either as I have 15,000 systems that
have recently been upgraded to Exchange 2003 OWA....way to go
Microsoft!!!
Click to expand...

How did you deploy Office 2003? Are you using GPO or LIS? With MST?

--
Alex Yu
http://mucha.us/blogs/alex/

This posting represents my own opinion, and in no way claims
to represent the views of Microsoft Corporation. This posting
is provided "as is" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias
is for newsgroup purposes only. Remove "online." if you would
like to reach me privately.
 
Office was installed by mapping a network drive to a server containing
the setup files.

This was performed on 1 master workstation that was then images and
deployed to all other systems.

Problem is that the image was created in lets say California now when
a system in lets say Boston tries to update it has to connect to the
server in California to do the updates..........
 
Office was installed by mapping a network drive to a server containing
the setup files.

This was performed on 1 master workstation that was then images and
deployed to all other systems.

Problem is that the image was created in lets say California now when
a system in lets say Boston tries to update it has to connect to the
server in California to do the updates..........
 
SirOssis said:
Office was installed by mapping a network drive to a server containing
the setup files.

This was performed on 1 master workstation that was then images and
deployed to all other systems.

Problem is that the image was created in lets say California now when
a system in lets say Boston tries to update it has to connect to the
server in California to do the updates..........
Click to expand...

Did you expect a different behavior? All network installs behave this way.
 
Back
Top