Office 2000 network installs cannot access original install share anymore

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a feature
is needed Office grabs it from the shared folder where it came from. No
problem.

All of a sudden one morning recently, some of our computers try and install
a feature of Office at login time and cannot access the share anymore! It
gets an error stating that access is denied. No changes have been made to
the share or the Office installs. In fact the group "everyone" has been
given read access to the share. I can browse to the folder manually from
the desktop and access the filesno problem. However, if I browse using the
MS Office install dialog, it has no access to the share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines, yet
at login time on occasions, MS Office will try to install/update a feature
from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have no
up to now installed any Office 2000 service packs.

regards,
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[grolschie]

Hi there,

I have deploy MS Office 2000 from a 2003 Server by doing a network install
and sharing the folder. I have installed onto about 80 odd XP Pro SP2
machines. This setup has been working fine for over 18 months. If a
feature is needed Office grabs it from the shared folder where it came
from. No problem.

All of a sudden one morning recently, some of our computers try and
install a feature of Office at login time and cannot access the share
anymore! It gets an error stating that access is denied. No changes have
been made to the share or the Office installs. In fact the group
"everyone" has been given read access to the share. I can browse to the
folder manually from the desktop and access the filesno problem. However,
if I browse using the MS Office install dialog, it has no access to the
share!!!

We have made no changes to our Server 2003 where the share is located, yet
all of a sudden this is broken. Why is it trying to install a feature
anyways?

I tried doing a complete full install from the server on these machines,
yet at login time on occasions, MS Office will try to install/update a
feature from the share. What gives? Can anyone please help me?

I wonder if a Windows XP or Server 2003 update has messed things? We have
no up to now installed any Office 2000 service packs.

regards,
grol

Could it be the recent upgrade to Windows Installer 3.1 via Auto-Updates?
grol

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[Gerry Hickman]

Hi,

Check the keys below to see if they've been changed. The long number may be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList



and



HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

 

[grolschie]

Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.