Office 2007 Unusable in Limited User Account

sigh...I thought I had this problem licked, but I was wrong.

I use Windows XP Home SP 3. I installed portions of Office Enterprise 2007 (Word, Excel and Outlook) from my Administrator account. I used the software in my Administrator account for a few days, and everything was going well. Then I switched back to my Limited User account.

In the Limited User account, each and every time I start Word or Excel, Office Enterprise 2007 wants to configure itself. This process lasts about 5 minutes. (I haven't used Outlook yet in the Limited User account.)

Since the problem only manifests in the Limited User account, I thought there might an issue somehow with permissions. I switched back to my Administrator account, completely uninstalled Office, and then installed SubInAcl and reset my registry permissions. After that, I installed Office 2007 again (Word, Excel and Outlook.) I switched back to my Limited User account and...you guessed it...same problem. Every time I start Word or Excel, Office 2007 spends 5 minutes configuring itself. Since I use Office just about every day, this behavior is not acceptable.

As a result, I have gone back to using my Administtator account for day-to-day computing, which is not an ideal situation. If anyone can help me to solve this problem I'll be very grateful.

Daddy

As I understand it Office 2007 needs to be installed on an account that has
administrative permissions - That doesnt mean that you use the administrator
account, just that the account used has appropriate permissions

"Daddy" wrote in message
...
sigh...I thought I had this problem licked, but I was wrong.

I use Windows XP Home SP 3. I installed portions of Office Enterprise 2007
(Word, Excel and Outlook) from my Administrator account. I used the software
in my Administrator account for a few days, and everything was going well.
Then I switched back to my Limited User account.

In the Limited User account, each and every time I start Word or Excel,
Office Enterprise 2007 wants to configure itself. This process lasts about 5
minutes. (I haven't used Outlook yet in the Limited User account.)

Since the problem only manifests in the Limited User account, I thought
there might an issue somehow with permissions. I switched back to my
Administrator account, completely uninstalled Office, and then installed
SubInAcl and reset my registry permissions. After that, I installed Office
2007 again (Word, Excel and Outlook.) I switched back to my Limited User
account and...you guessed it...same problem. Every time I start Word or
Excel, Office 2007 spends 5 minutes configuring itself. Since I use Office
just about every day, this behavior is not acceptable.

As a result, I have gone back to using my Administtator account for
day-to-day computing, which is not an ideal situation. If anyone can help me
to solve this problem I'll be very grateful.

Daddy

Well, this is really disappointing. It's a shame that two Microsoft products -- Office 2007 and Windows XP -- can't work together.

As I previously said, resetting registry permissions with SubInAcl didn't help.

Applying MSKB 911682 didn't help. ("Windows Installer-related event IDs are logged in the Applications Log when you start an Office program")

Completely uninstalling and reinstalling Office (with security software turned off, of course) made no difference.

Resetting permissions on Office registry keys did nothing.

Office 2007 is not practical to use in a Limited User account on XP Home.

Now I must choose between using Office in Administrator accounts exclusively, forgoing the increased security afforded by the Limited User account, or using OpenOffice, which works just fine in a Limited User account. Since I am unwilling to give the children Administrator accounts, it looks like they're going to be using OpenOffice.

Daddy

"Daddy" wrote in message ...
sigh...I thought I had this problem licked, but I was wrong.

I use Windows XP Home SP 3. I installed portions of Office Enterprise 2007 (Word, Excel and Outlook) from my Administrator account. I used the software in my Administrator account for a few days, and everything was going well. Then I switched back to my Limited User account.

In the Limited User account, each and every time I start Word or Excel, Office Enterprise 2007 wants to configure itself. This process lasts about 5 minutes. (I haven't used Outlook yet in the Limited User account.)

Since the problem only manifests in the Limited User account, I thought there might an issue somehow with permissions. I switched back to my Administrator account, completely uninstalled Office, and then installed SubInAcl and reset my registry permissions. After that, I installed Office 2007 again (Word, Excel and Outlook.) I switched back to my Limited User account and...you guessed it...same problem. Every time I start Word or Excel, Office 2007 spends 5 minutes configuring itself. Since I use Office just about every day, this behavior is not acceptable.

As a result, I have gone back to using my Administtator account for day-to-day computing, which is not an ideal situation. If anyone can help me to solve this problem I'll be very grateful.

Daddy

This is not a solution to my problem, but it is a workaround:

Since Office 2007 is forever wanting to reinstall itself in the Limited User account, I looked for some kind of installation log. Bingo, The installation log has this filename:

SetupExe([date-of-install][hexadecimel number]).log .

Reading the installation log it is obvious that some process is calling this setup file:

%program files%\common files\microsoft shared\office12\Office Setup Controller\SETUP.EXE .

I renamed SETUP.EXE to SETUP.EX_ and the problem vanished.

I may have to rename SETUP.EX_ if I want to add or remove Office features, or if I need to repair Office, and it remains to be seen whether I'll be able to update Office through Microsoft Update. But for at least now Office 2007 has stopped trying to reinstall itself in the Limited User account every time it starts.

I'll investigate this problem further as I have time, however, Open Office works without a hitch in the Limited User account, so that's what my Limited Users are using now..

I got my copy of Office 2007 under the Home Use Program, so I only paid a nominal amount for it. Had I paid full price I would be angry with this mess. As it is I'm just bemused that Microsoft seems to have hoisted itself with its own petard.

Daddy

"Daddy" wrote in message ...
Well, this is really disappointing. It's a shame that two Microsoft products -- Office 2007 and Windows XP -- can't work together.

As I previously said, resetting registry permissions with SubInAcl didn't help.

Applying MSKB 911682 didn't help. ("Windows Installer-related event IDs are logged in the Applications Log when you start an Office program")

Completely uninstalling and reinstalling Office (with security software turned off, of course) made no difference.

Resetting permissions on Office registry keys did nothing.

Office 2007 is not practical to use in a Limited User account on XP Home.

Now I must choose between using Office in Administrator accounts exclusively, forgoing the increased security afforded by the Limited User account, or using OpenOffice, which works just fine in a Limited User account. Since I am unwilling to give the children Administrator accounts, it looks like they're going to be using OpenOffice.

Daddy

"Daddy" wrote in message ...
sigh...I thought I had this problem licked, but I was wrong.

I use Windows XP Home SP 3. I installed portions of Office Enterprise 2007 (Word, Excel and Outlook) from my Administrator account. I used the software in my Administrator account for a few days, and everything was going well. Then I switched back to my Limited User account.

In the Limited User account, each and every time I start Word or Excel, Office Enterprise 2007 wants to configure itself. This process lasts about 5 minutes. (I haven't used Outlook yet in the Limited User account.)

Since the problem only manifests in the Limited User account, I thought there might an issue somehow with permissions. I switched back to my Administrator account, completely uninstalled Office, and then installed SubInAcl and reset my registry permissions. After that, I installed Office 2007 again (Word, Excel and Outlook.) I switched back to my Limited User account and...you guessed it...same problem. Every time I start Word or Excel, Office 2007 spends 5 minutes configuring itself. Since I use Office just about every day, this behavior is not acceptable.

As a result, I have gone back to using my Administtator account for day-to-day computing, which is not an ideal situation. If anyone can help me to solve this problem I'll be very grateful.

Daddy

Hello y'all,

I have been dealing with this issue for three months and I have not
given it any thought until I had to rebuild my machine to give it to
someone else. following on everyone's leads here, it is definately
access rights permissions on certain registry folders for the
Administrators groups as well as the system account. I did a search for
'HKEY_CLASSES_ROOT\.pip\' problem that appeared in the application logs
and this is the result. Here's the link:

http://support.microsoft.com/kb/911682

Problem description:
--------
Event ID: 1001
Event Source: MsiInstaller
Description:
Detection of product '{90280409-6000-11D3-8CFE-0050048383C9}', feature
'WORDFILES'
failed during request for component
'{8E46FEFA-D973-6294-B305-E968CEDFFCB9}'Event ID: 1015
Event Source: MsiInstaller
Description:
Failed to connect to server. Error: 0x80004001Event ID: 1004
Event Source: MsiInstaller
Description:
Detection of product '{90120409-6000-11D3-8CFE-0050048383C9}', feature

'ProductFiles', component '{66CD2C91-2A15-4DA4-BBD2-5EC1075F3C0E}'
failed. The
resource 'HKEY_CLASSES_ROOT\.pip\' does not exist.Event ID: 1000
Event Source: MsiInstaller
Description:
No installer is running when launching the applications
-----------------

Solution:

Note You can perform this procedure on a Terminal Server console or on
the local computer, depending on the location on which the Office
program is installed
Start a Terminal Server client session, and then log on as a user.

Note If you have installed the Office product on the local computer, go
to step 2.
Click Start, click Run, type regedit in the Open box, and then click
OK.
In the left pane, locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer
On the Edit menu, click Permissions.
In the permissions for Installer dialog box, click Administrators in
the Group or user names list, and then make sure that the Full Control
permission is set for the Administrators group. If this permission is
not set, click to select the Full Control check box under Allow.
Click OK.
Repeat steps 5 through 6 for the SYSTEM group.
Repeat steps 5 through 6 for the Everyone group. Verify that only the
Read permission is set for the Everyone group. If this permission is not
set, click to select the Read check box under Allow.
Repeat steps 4 through 8 for the following registry subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\Compo
HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT\.pip
HKEY_CLASSES_ROOT\Installer
HKEY_CLASSES_ROOT\Installer\Components
HKEY_CURRENT_USER\Software\Classes
Clear the Application log, start the Office program, and then see
whether you receive the event IDs that are mentioned in the “Symptoms”
section.
If you still receive event ID 1004, delete the UsrClass.dat and
UsrClass.dat.log files for every user on the terminal server or on the
local computer. To do this, follow these steps:
Click Start, point to Programs, point to Accessories, and then click
Windows Explorer.
In the left pane, locate and then click the following folder:
Drive:\Documents and Settings\USERNAME\Local Settings\Application
Data\Microsoft\Windows
NoteDrive represents the drive letter for the hard disk drive partition
on which Windows is installed.

This Windows folder is in a hidden folder. To view the Windows folder,
you must configure the folder settings to display hidden files and
folders. If you cannot locate the Windows folder, verify that the folder
settings on the computer are configured to display hidden files and
folders. To do this, follow these steps:
On the Tools menu, click Folder Options.
In the Folder Options dialog box, click the View tab.
Under Hidden files and folders, click Show hidden files and folders,
and then click OK.
Verify that the Windows folder is now available.
In the right pane, right-click UsrClass.dat, and then click Delete.
Click Yes when you are prompted to confirm the file deletion.
Repeat steps 3 and 4 for the UsrClass.dat.log file.
Start the Office program, and then verify that the event IDs that are
mentioned in the "Symptoms" section are not logged in Application log.
Back to the top

--------------------------------------------------------------------------------

APPLIES TO
Microsoft Office Professional Edition 2003
Microsoft Office Standard Edition 2003
Microsoft Office Student and Teacher Edition 2003
Microsoft Office Small Business Edition 2003
Microsoft Office Basic Edition 2003
Microsoft Office XP Professional
Microsoft Office XP Small Business Edition
Microsoft Office XP Standard Edition
Microsoft Office XP Standard Edition for Students and Teachers
Microsoft Office 2000 Premium Edition
Microsoft Office 2000 Professional Edition
Microsoft Office 2000 Standard Edition
Microsoft Office 2000 Small Business Edition


--
Pade
------------------------------------------------------------------------
Pade's Profile: http://forums.techarena.in/members/pade.htm
View this thread: http://forums.techarena.in/office-setup/1078878.htm

http://forums.techarena.in

Hi Pade:

Have you actually tried that solution?

I know about the MSKB article...been there, done that...it did not solve my problem. Nor does it address the issue of type libraries in Excel 2007 (stdole32.tlb). I haven't even attempted to run Outlook 2007 in Limited User accounts.

It certainly is an issue with registry permissions. So far, I have found no solution for XP Home. Microsoft appears to have shot itself in the foot this time. My Limited Users are using OpenOffice.

[OT: Office 2007 Enterprise does work in an Administrator account, but not without a separate set of problems. I would advise anyone offered Office 2007 Enterprise under the Home Use Program to think twice, particularly if they have XP Home.]

Daddy

"Pade" wrote in message ...

Hello y'all,

I have been dealing with this issue for three months and I have not
given it any thought until I had to rebuild my machine to give it to
someone else. following on everyone's leads here, it is definately
access rights permissions on certain registry folders for the
Administrators groups as well as the system account. I did a search for
'HKEY_CLASSES_ROOT\.pip\' problem that appeared in the application logs
and this is the result. Here's the link:

http://support.microsoft.com/kb/911682

Problem description:
--------
Event ID: 1001
Event Source: MsiInstaller
Description:
Detection of product '{90280409-6000-11D3-8CFE-0050048383C9}', feature
'WORDFILES'
failed during request for component
'{8E46FEFA-D973-6294-B305-E968CEDFFCB9}'Event ID: 1015
Event Source: MsiInstaller
Description:
Failed to connect to server. Error: 0x80004001Event ID: 1004
Event Source: MsiInstaller
Description:
Detection of product '{90120409-6000-11D3-8CFE-0050048383C9}', feature

'ProductFiles', component '{66CD2C91-2A15-4DA4-BBD2-5EC1075F3C0E}'
failed. The
resource 'HKEY_CLASSES_ROOT\.pip\' does not exist.Event ID: 1000
Event Source: MsiInstaller
Description:
No installer is running when launching the applications
-----------------

Solution:

Note You can perform this procedure on a Terminal Server console or on
the local computer, depending on the location on which the Office
program is installed
Start a Terminal Server client session, and then log on as a user.

Note If you have installed the Office product on the local computer, go
to step 2.
Click Start, click Run, type regedit in the Open box, and then click
OK.
In the left pane, locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer
On the Edit menu, click Permissions.
In the permissions for Installer dialog box, click Administrators in
the Group or user names list, and then make sure that the Full Control
permission is set for the Administrators group. If this permission is
not set, click to select the Full Control check box under Allow.
Click OK.
Repeat steps 5 through 6 for the SYSTEM group.
Repeat steps 5 through 6 for the Everyone group. Verify that only the
Read permission is set for the Everyone group. If this permission is not
set, click to select the Read check box under Allow.
Repeat steps 4 through 8 for the following registry subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\Compo
HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT\.pip
HKEY_CLASSES_ROOT\Installer
HKEY_CLASSES_ROOT\Installer\Components
HKEY_CURRENT_USER\Software\Classes
Clear the Application log, start the Office program, and then see
whether you receive the event IDs that are mentioned in the “Symptoms”
section.
If you still receive event ID 1004, delete the UsrClass.dat and
UsrClass.dat.log files for every user on the terminal server or on the
local computer. To do this, follow these steps:
Click Start, point to Programs, point to Accessories, and then click
Windows Explorer.
In the left pane, locate and then click the following folder:
Drive:\Documents and Settings\USERNAME\Local Settings\Application
Data\Microsoft\Windows
NoteDrive represents the drive letter for the hard disk drive partition
on which Windows is installed.

This Windows folder is in a hidden folder. To view the Windows folder,
you must configure the folder settings to display hidden files and
folders. If you cannot locate the Windows folder, verify that the folder
settings on the computer are configured to display hidden files and
folders. To do this, follow these steps:
On the Tools menu, click Folder Options.
In the Folder Options dialog box, click the View tab.
Under Hidden files and folders, click Show hidden files and folders,
and then click OK.
Verify that the Windows folder is now available.
In the right pane, right-click UsrClass.dat, and then click Delete.
Click Yes when you are prompted to confirm the file deletion.
Repeat steps 3 and 4 for the UsrClass.dat.log file.
Start the Office program, and then verify that the event IDs that are
mentioned in the "Symptoms" section are not logged in Application log.
Back to the top

--------------------------------------------------------------------------------

APPLIES TO
Microsoft Office Professional Edition 2003
Microsoft Office Standard Edition 2003
Microsoft Office Student and Teacher Edition 2003
Microsoft Office Small Business Edition 2003
Microsoft Office Basic Edition 2003
Microsoft Office XP Professional
Microsoft Office XP Small Business Edition
Microsoft Office XP Standard Edition
Microsoft Office XP Standard Edition for Students and Teachers
Microsoft Office 2000 Premium Edition
Microsoft Office 2000 Professional Edition
Microsoft Office 2000 Standard Edition
Microsoft Office 2000 Small Business Edition


--
Pade
------------------------------------------------------------------------
Pade's Profile: http://forums.techarena.in/members/pade.htm
View this thread: http://forums.techarena.in/office-setup/1078878.htm

http://forums.techarena.in

Hi Daddy,

I didn't experience it. Maybe because I created limited users after
2007 installation. Will it be?

Regards,

Fanfoe


On Dec 29, 1:11*am, "Daddy" wrote:
Hi Pade:

Have you actually tried that solution?

I know about the MSKB article...been there, done that...it did not solve my problem. Nor does it address the issue of type libraries in Excel 2007 (stdole32.tlb). I haven't even attempted to run Outlook 2007 in Limited User accounts.

It certainly is an issue with registry permissions. So far, I have found no solution for XP Home. Microsoft appears to have shot itself in the foot this time. My Limited Users are using OpenOffice.

[OT: Office 2007 Enterprise does work in an Administrator account, but not without a separate set of problems. I would advise anyone offered Office 2007 Enterprise under the Home Use Program to think twice, particularly if they have XP Home.]

Daddy



"Pade" wrote in ...

Hello y'all,

I have been dealing with this issue for three months and I have not
given it any thought until I had to rebuild my machine to give it to
someone else. *following on everyone's leads here, *it is definately
access rights permissions on certain registry folders for the

Thus far in my research, the only users I have come across who do not
experience this issue are those who installed Office 2007 Enterprise after a
clean install of Windows. Prior to this drastic step, they had either
upgraded a pre-existing version of Office or installed Office 2007
Enterprise after having removed a previous installation of Office. (I
removed Office XP prior to installing Office 2007 Enterprise.)

You did not mention which version of Windows you have. I can only speak from
experience for Windows XP Home. Other versions of Windows may yield
different results.

This work-around prevents continual re-installing: Rename this file --

C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup
Controller\SETUP.EXE

to SETUP.EX_

This prevents the Office 2007 setup routine from starting. You'll need to
rename the file back to SETUP.EXE whenever you need to invoke a setup
operation, viz. when adding or removing features, when repairing an Office
installation, and (probably) when installing updates.

Daddy

wrote in message
...
Hi Daddy,

I didn't experience it. Maybe because I created limited users after
2007 installation. Will it be?

Regards,

Fanfoe


On Dec 29, 1:11 am, "Daddy" wrote:
Hi Pade:

Have you actually tried that solution?

I know about the MSKB article...been there, done that...it did not solve
my problem. Nor does it address the issue of type libraries in Excel 2007
(stdole32.tlb). I haven't even attempted to run Outlook 2007 in Limited
User accounts.

It certainly is an issue with registry permissions. So far, I have found
no solution for XP Home. Microsoft appears to have shot itself in the foot
this time. My Limited Users are using OpenOffice.

[OT: Office 2007 Enterprise does work in an Administrator account, but not
without a separate set of problems. I would advise anyone offered Office
2007 Enterprise under the Home Use Program to think twice, particularly if
they have XP Home.]

Daddy



"Pade" wrote in
...

Hello y'all,

I have been dealing with this issue for three months and I have not
given it any thought until I had to rebuild my machine to give it to
someone else. following on everyone's leads here, it is definately
access rights permissions on certain registry folders for the

I had this problem with Office 2003. It's not new. Its something about
the setup process and it's per user. I think the clean install thing is
what really works to prevent problems in the first place, but I 'fixed'
this in a different way.

-For the limited user, add them to the machine's administrators group.
-Login as Limited User.
-While they are an Admin, open the Office program and let it run the
setup process.
-Once that is done, remove their administrative permissions.

That should work fine.

PS: I know that this is a dead thread, but no one posted a good
solution so I wanted people who search this in the future to have one.


--
andrewkoldwell
------------------------------------------------------------------------
andrewkoldwell's Profile: http://forums.techarena.in/members/andrewkoldwell.htm
View this thread: http://forums.techarena.in/office-setup/1078878.htm

http://forums.techarena.in

Hi Andrew:

I still check this thread from time to time, just to see if anything has been added. Thanks for your suggestion.

I have XP Home, not Pro, but I did temporarily make my Limited Users into Computer Administrators and then ran setup. All went well, but as soon as I changed them back to Limited Users again, the problem returned.

When Office Enterprise 2007 starts, it's checking to see if something or things have been installed. It will re-install what it finds missing. I haven't pinned down quite yet what setup is looking for, but I know that if I disable setup with the workaround I discovered, then all is well.

Daddy

"andrewkoldwell" wrote in message ...

I had this problem with Office 2003. It's not new. Its something about
the setup process and it's per user. I think the clean install thing is
what really works to prevent problems in the first place, but I 'fixed'
this in a different way.

-For the limited user, add them to the machine's administrators group.
-Login as Limited User.
-While they are an Admin, open the Office program and let it run the
setup process.
-Once that is done, remove their administrative permissions.

That should work fine.

PS: I know that this is a dead thread, but no one posted a good
solution so I wanted people who search this in the future to have one.


--
andrewkoldwell
------------------------------------------------------------------------
andrewkoldwell's Profile: http://forums.techarena.in/members/andrewkoldwell.htm
View this thread: http://forums.techarena.in/office-setup/1078878.htm

http://forums.techarena.in