Office 2003 Pro installer keeps running...

Hi,

PC is an XP Pro machine, fully updated.

The PC is setup in a workgroup, and fast user switching is operating.

Two accounts on this computer: one Administrator privilege, the other,
limited access.

Office 2003 Pro installed (Complete install used).

Runs fine on the Admin user a/c.

The Office installer pops up opening *any* Office program on the other
(limited access) account.

As a test I have:
* set the other a/c privilege to admin, and it works fine.
* from that account, demoted the admin account (where office was
installed from) to limited access, logged out and into that a/c - and
the installer runs.

*Surely* - Office 2003 is not meant to be like this ???

PS: other things noted, Office 2002 (XP) is installed, and when we
installed 2003 there was no prompting to update it. (I noted when in
Add/Remove programs that Office XP was installed. Could this cause any
problems?).

Have tried a Repair and Reinstall from the original limited a/c
(promoted to admin) - but to no avail. Please note that demoting the
original a/c (admin privilege) causes the problem to occur on that user
also. As said, surely it's' not meant to be like this ???

--
Duncan

Its not. Whenever the installer kicks off everytime, it generally means
that something is funky with the user profile under XP (hence find under
admin but not limited access). Best bet is to backup what you want to keep
under the limited account and then delete said user profile using the admin
account.

"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1f035a1d905e4153989843@news.microsoft.com...
> Hi,
>
> PC is an XP Pro machine, fully updated.
>
> The PC is setup in a workgroup, and fast user switching is operating.
>
> Two accounts on this computer: one Administrator privilege, the other,
> limited access.
>
> Office 2003 Pro installed (Complete install used).
>
> Runs fine on the Admin user a/c.
>
> The Office installer pops up opening *any* Office program on the other
> (limited access) account.
>
> As a test I have:
> * set the other a/c privilege to admin, and it works fine.
> * from that account, demoted the admin account (where office was
> installed from) to limited access, logged out and into that a/c - and
> the installer runs.
>
> *Surely* - Office 2003 is not meant to be like this ???
>
> PS: other things noted, Office 2002 (XP) is installed, and when we
> installed 2003 there was no prompting to update it. (I noted when in
> Add/Remove programs that Office XP was installed. Could this cause any
> problems?).
>
> Have tried a Repair and Reinstall from the original limited a/c
> (promoted to admin) - but to no avail. Please note that demoting the
> original a/c (admin privilege) causes the problem to occur on that user
> also. As said, surely it's' not meant to be like this ???
>
> --
> Duncan

In article <#DCWtfYlGHA.4044@TK2MSFTNGP03.phx.gbl>, neo@online.mvps.org
says...
>
> "Duncan McC" <hard@work.ok> wrote in message
> news:MPG.1f035a1d905e4153989843@news.microsoft.com...
> > Hi,
> >
> > PC is an XP Pro machine, fully updated.
> >
> > The PC is setup in a workgroup, and fast user switching is operating.
> >
> > Two accounts on this computer: one Administrator privilege, the other,
> > limited access.
> >
> > Office 2003 Pro installed (Complete install used).
> >
> > Runs fine on the Admin user a/c.
> >
> > The Office installer pops up opening *any* Office program on the other
> > (limited access) account.
> >
> > As a test I have:
> > * set the other a/c privilege to admin, and it works fine.
> > * from that account, demoted the admin account (where office was
> > installed from) to limited access, logged out and into that a/c - and
> > the installer runs.
> >
> > *Surely* - Office 2003 is not meant to be like this ???
> >
> > PS: other things noted, Office 2002 (XP) is installed, and when we
> > installed 2003 there was no prompting to update it. (I noted when in
> > Add/Remove programs that Office XP was installed. Could this cause any
> > problems?).
> >
> > Have tried a Repair and Reinstall from the original limited a/c
> > (promoted to admin) - but to no avail. Please note that demoting the
> > original a/c (admin privilege) causes the problem to occur on that user
> > also. As said, surely it's' not meant to be like this ???
> >
> > --
> > Duncan

> Its not. Whenever the installer kicks off everytime, it generally means
> that something is funky with the user profile under XP (hence find under
> admin but not limited access). Best bet is to backup what you want to keep
> under the limited account and then delete said user profile using the admin
> account.

OK, so what I don't get, is that my test (see above) didn't work either.
ie no profile on the PC works in limited access mode.

I will get the PC owner to create a new user (profile) and set that as
an Admin privilege, install Office, and then demote to a limited user.
This should work, right ???

--
Duncan

Yep, but I've never had to take it that far.

"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1f051118b938fd5e989846@news.microsoft.com...
> In article <#DCWtfYlGHA.4044@TK2MSFTNGP03.phx.gbl>, neo@online.mvps.org
> says...
>>
>> "Duncan McC" <hard@work.ok> wrote in message
>> news:MPG.1f035a1d905e4153989843@news.microsoft.com...
>> > Hi,
<snip>
>> Its not. Whenever the installer kicks off everytime, it generally means
>> that something is funky with the user profile under XP (hence find under
>> admin but not limited access). Best bet is to backup what you want to
>> keep
>> under the limited account and then delete said user profile using the
>> admin
>> account.
>
> OK, so what I don't get, is that my test (see above) didn't work either.
> ie no profile on the PC works in limited access mode.
>
> I will get the PC owner to create a new user (profile) and set that as
> an Admin privilege, install Office, and then demote to a limited user.
> This should work, right ???
>
> --
> Duncan

By the way, the installer will post something into the application event log
whenever the installer kicks off. One of those entries will state what
component is missing (it will be a long alpha-numeric number). If you can
post the text of that entry, I might be able to get someone from Microsoft
to identify component part to see if it tied to Office or some other MS
program that uses Office shared components.

"neo [mvp outlook]" <neo@online.mvps.org> wrote in message
news:OUDb8BhlGHA.4244@TK2MSFTNGP02.phx.gbl...
> Yep, but I've never had to take it that far.
>
> "Duncan McC" <hard@work.ok> wrote in message
> news:MPG.1f051118b938fd5e989846@news.microsoft.com...
>> In article <#DCWtfYlGHA.4044@TK2MSFTNGP03.phx.gbl>, neo@online.mvps.org
>> says...
>>>
>>> "Duncan McC" <hard@work.ok> wrote in message
>>> news:MPG.1f035a1d905e4153989843@news.microsoft.com...
>>> > Hi,
> <snip>
>>> Its not. Whenever the installer kicks off everytime, it generally means
>>> that something is funky with the user profile under XP (hence find under
>>> admin but not limited access). Best bet is to backup what you want to
>>> keep
>>> under the limited account and then delete said user profile using the
>>> admin
>>> account.
>>
>> OK, so what I don't get, is that my test (see above) didn't work either.
>> ie no profile on the PC works in limited access mode.
>>
>> I will get the PC owner to create a new user (profile) and set that as
>> an Admin privilege, install Office, and then demote to a limited user.
>> This should work, right ???
>>
>> --
>> Duncan
>
>

I have the same problem - I have reinstalled office, no luck. I have tried a
brand new limited account and still no luck

"neo [mvp outlook]" wrote:

> Its not. Whenever the installer kicks off everytime, it generally means
> that something is funky with the user profile under XP (hence find under
> admin but not limited access). Best bet is to backup what you want to keep
> under the limited account and then delete said user profile using the admin
> account.
>
> "Duncan McC" <hard@work.ok> wrote in message
> news:MPG.1f035a1d905e4153989843@news.microsoft.com...
> > Hi,
> >
> > PC is an XP Pro machine, fully updated.
> >
> > The PC is setup in a workgroup, and fast user switching is operating.
> >
> > Two accounts on this computer: one Administrator privilege, the other,
> > limited access.
> >
> > Office 2003 Pro installed (Complete install used).
> >
> > Runs fine on the Admin user a/c.
> >
> > The Office installer pops up opening *any* Office program on the other
> > (limited access) account.
> >
> > As a test I have:
> > * set the other a/c privilege to admin, and it works fine.
> > * from that account, demoted the admin account (where office was
> > installed from) to limited access, logged out and into that a/c - and
> > the installer runs.
> >
> > *Surely* - Office 2003 is not meant to be like this ???
> >
> > PS: other things noted, Office 2002 (XP) is installed, and when we
> > installed 2003 there was no prompting to update it. (I noted when in
> > Add/Remove programs that Office XP was installed. Could this cause any
> > problems?).
> >
> > Have tried a Repair and Reinstall from the original limited a/c
> > (promoted to admin) - but to no avail. Please note that demoting the
> > original a/c (admin privilege) causes the problem to occur on that user
> > also. As said, surely it's' not meant to be like this ???
> >
> > --
> > Duncan
>
>
>

also when I look at the application logs like you suggest below i see one for
the limited account that says not Hkey_classes_Root\.pip\ - could that be
causing my problem? if so what to do to fix it

"neo [mvp outlook]" wrote:

> Its not. Whenever the installer kicks off everytime, it generally means
> that something is funky with the user profile under XP (hence find under
> admin but not limited access). Best bet is to backup what you want to keep
> under the limited account and then delete said user profile using the admin
> account.
>
> "Duncan McC" <hard@work.ok> wrote in message
> news:MPG.1f035a1d905e4153989843@news.microsoft.com...
> > Hi,
> >
> > PC is an XP Pro machine, fully updated.
> >
> > The PC is setup in a workgroup, and fast user switching is operating.
> >
> > Two accounts on this computer: one Administrator privilege, the other,
> > limited access.
> >
> > Office 2003 Pro installed (Complete install used).
> >
> > Runs fine on the Admin user a/c.
> >
> > The Office installer pops up opening *any* Office program on the other
> > (limited access) account.
> >
> > As a test I have:
> > * set the other a/c privilege to admin, and it works fine.
> > * from that account, demoted the admin account (where office was
> > installed from) to limited access, logged out and into that a/c - and
> > the installer runs.
> >
> > *Surely* - Office 2003 is not meant to be like this ???
> >
> > PS: other things noted, Office 2002 (XP) is installed, and when we
> > installed 2003 there was no prompting to update it. (I noted when in
> > Add/Remove programs that Office XP was installed. Could this cause any
> > problems?).
> >
> > Have tried a Repair and Reinstall from the original limited a/c
> > (promoted to admin) - but to no avail. Please note that demoting the
> > original a/c (admin privilege) causes the problem to occur on that user
> > also. As said, surely it's' not meant to be like this ???
> >
> > --
> > Duncan
>
>
>