Enterprise 2007 Configuration Loop

[Reodd]

I have recently completed a system restore to a designated restore point.
This resolved my immediate issue but has caused considerable damage to my
Office 2007 Enterprise Installation.
I have Windows XP sp3 with a full installation of Office Enterprise 2007.
The Installation was OK untill the restore.

When I try to open any of the office suite I am presented with a
configuration loop. The system launces into the configuration process. If
left to complete this then tries to install the application.

I can access the application if I just cancel this configuration process but
this is a real problem when trying to integrate my applications and open from
within other systems

I have tried to complete a repair from the CD with no luck. I have even
tried to reinstall the application with noo luck.
I do not want to have to rebuild my laptop as this is core to my daily
operation as systems manager for my company.

Any assistance would be appreciated and as this issue seems to have affected
others (web search) then resolving this issue cooudl save many people a lot
of time.

Thanks in advance.

 

[Peter Foldes]

Try this
http://support.microsoft.com/kb/290301

 

[Reodd]

Thanks for the information, unfortunately I have already tried this one and
it does not solve the problem.
At this point I need to advise that I have resolved the issue.
The thought of rebuilding my laptop was not an option so I had to manually
uninstall all MS Office 2007 enterprise products and any other MS products
that could have been causing the problem.
In my case I had to remove
Web Expressions, Project, Visio, and the full office 2007 suite.

The following Knowledgebase assisted in this process.
http://support.microsoft.com/kb/928218

Once removed and rebooted I undertook a full reinstall of the office
applications suite.
All issues have been resolved.
I suspect that you could run through teh standard uninstall process “go to
control panel, add remove progs, etc.†But this does not remove all the
directories and registry entries that may be causing the issue.
I hope that this is of some use to anyone else out there.