B
Bunnyslippers
BACKGROUND: I'm running Entourage 11.2.5 under Mac OS 10.4.8. Recently,
I started experiencing the application slowing to a crawl (click on a
folder; 5 minutes later, the folder respond) or just not responding at
all. I used FontBook to find and remove some damaged fonts (I recalled
this trick from a similar problem a couple of years ago), and
voila--problem fixed. I have no idea if this problem relates to the
current problem; I offer it as background.
CURRENT PROBLEM: This week, I began getting the dreaded "Your Office
database is damaged...do you want to quit and run the repair utility
yada yada" message. I ran the utility to repair the DB, but after a
few minutes of the app working fine, the message would appear again.
Canceling it only caused it to reappear moments later I ran the repair
4 or 5 times before looking in this forum for help. I saw several
messages saying it had to do with upgrading to 11.2.3 from 11.2.1 (I'm
way past that), and others with other suggestions. But I also noticed
that several replies from MS people happened to mention that you need
to quit Microsoft Notifications before running the repair. I'm sure I
did that--the app won't let you run the utility otherwise--but this
triggered something in my lizard brain about Office Notifications, and
I began to suspect it. So I trashed its preferences
(/Users/username/Library/Preferences/com.microsoft.OfficeNotifications.plist).
Lo and behold, I haven't had a problem since.
Hope this helps someone who's having the problem.
I started experiencing the application slowing to a crawl (click on a
folder; 5 minutes later, the folder respond) or just not responding at
all. I used FontBook to find and remove some damaged fonts (I recalled
this trick from a similar problem a couple of years ago), and
voila--problem fixed. I have no idea if this problem relates to the
current problem; I offer it as background.
CURRENT PROBLEM: This week, I began getting the dreaded "Your Office
database is damaged...do you want to quit and run the repair utility
yada yada" message. I ran the utility to repair the DB, but after a
few minutes of the app working fine, the message would appear again.
Canceling it only caused it to reappear moments later I ran the repair
4 or 5 times before looking in this forum for help. I saw several
messages saying it had to do with upgrading to 11.2.3 from 11.2.1 (I'm
way past that), and others with other suggestions. But I also noticed
that several replies from MS people happened to mention that you need
to quit Microsoft Notifications before running the repair. I'm sure I
did that--the app won't let you run the utility otherwise--but this
triggered something in my lizard brain about Office Notifications, and
I began to suspect it. So I trashed its preferences
(/Users/username/Library/Preferences/com.microsoft.OfficeNotifications.plist).
Lo and behold, I haven't had a problem since.
Hope this helps someone who's having the problem.