Opening Access causes Office to repair itself everytime

[ChrisR]

Hello-

We have several users that when Access is opened from the program shortcut
or by double clicking an access database file, Office will repair itself
before Access opens. Event viewer just notes an Event ID 11728 with the
message "Product: Microsoft Office Professional Edition 2003 -- Configuration
completed successfully."

The other Office applications open with no problems. We are using Office Pro
2003 SP2.

I have not been able to find much help searching on google... it's a little
frustrating actually to not be able to find much of anything to point us in
any direction...

Thanks

 

[Stockwell43]

Hi Chris,

I'm not sure what the problem is but maybe something was clicked or
activated to make Access do that or it could be corrupted. This may not work
but try it anyway.

Make a copy of your database and import everything into a newly created
database and see what happens. Usually if it's corrupted this is the fix. You
won't hurt anything but it's like giving the database a fresh start. BUT make
sure you make a copy first. This should only take about 10 minutes.

Good Luck!!

 

[Stefan Hoffmann]

hi Chris,

We have several users that when Access is opened from the program shortcut
or by double clicking an access database file, Office will repair itself
before Access opens. Event viewer just notes an Event ID 11728 with the
message "Product: Microsoft Office Professional Edition 2003 -- Configuration
completed successfully."

Normally not an Access problem. Try running Regmon/Filemon

http://technet.microsoft.com/de-de/sysinternals/default(en-us).aspx

to determine what registry keys/files are repaired. Maybe this will give
you a clue.


mfG
--> stefan <--

 

[ChrisR]

Thanks, but the issue is happening even when Access is opened fresh from the
Program group shortcut. We can even browse to the Access exe, open and have
the same problem so it does not appear to be database related. Many of the
affected users are accessing different databases anyway and not all users are
experiencing this issue.