New system install of Office 2000

[raht]

I just completed a new install of Office 2K Pro during a system rebuild. I
can immediately open an Office App (Word, Excel, Access, PowerPoint, Outlook,
or Visio) by clicking on the shortcut from the "Start > Programs Menu" while
signed on as an Administrator (BTW, I'm using WIN 2K OS), but when signed on
as a Power User each app tries to reinstall when the shortcut is clicked. If
I just keep clicking OK to each "....failed to open product" error dialog box
the app eventually opens, also, if I click cancel when the first installation
dialog box appears the app will open. This, as you might expect can become a
real pain. The MS Knowledge Base discussed some similar situations, though
none exactly matched mine and I could not find the suggested fixes over on
the Office 2000 Resources Kit site that were referenced.

Thank you in advance for any help offered.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.

 

[raht]

I found a solution to this problem; I followed a suggestion I found in a
reply to one of the other questions dealing with same problem.

The suggestion was, temporarily assign the user to the Administrators Group,
have the user sign-on and open a Microsoft Office App in order for Installer
to work. After installation, check each App to be sure it will open, then,
reassign the user's original privileges.

The reason Installer fails is because the user has to have administrative
privileges in order for Installer to initially establish a path from the
User's Shortcuts (Start > Programs > Office App) to the file that executes
the Office Apps. At least that's what I think happens.

Anyway, it worked for me.

Thanks guys.