OMG!!!!!!!!!!!
You are ALL going to kick yourselves when you read the following...
----
OK, so it happened AGAIN earlier this afternoon, and again the only
indication was an increase in CPU usage for the Database Daemon. I then get
a dialog box pop-up that says something along the lines of:
"Operaton could not be completed. Error 16008"
...or something close to that (I was too quick to dismiss the dialog).
So I started thinking back to my original thought...which was some kind of
database upkeep of some sort. Here is what I posted:
> It did happen to me again this morning, and looking at the list of
> applications via the Activity Monitor program I did notice the Database
> Daemon application was taking much more CPU time than usual (anywhere from 4
> to 5%), but nothing else was unusually high. I really does seem like the
> database is going through some sort of "optimization" cycle...but I don't
> think there is such a thing on Entourage.
>
> Any other ideas? :-(
Well, guess what?!?!?! I'm pretty certain that is EXACTLY what is going on.
I launched Entourage with the <option> key down and on the database utility
there it was. The last radio-button is to set the preferences for your
database, and once you go there you are faced by the following option:
"Perform Database integrity check in the background."
So then Entourage (actually the Database Daemon) is INDEED doing some kind
of integrity check in the background. The question now is, why would this
check happen in the middle of the day AND why would it just make Entourage
completely unusable? Anyone? Jud?
I could still be wrong, but I need more info as to how this "feature" works
before being 100%.
________________________________________________________________________
Luis Vallecillo - http://weborican.com - [EMAIL PROTECTED]
> From: Allen Watson <[EMAIL PROTECTED]>
> Reply-To: "Entourage:mac Talk" <[EMAIL PROTECTED]>
> Date: Wed, 01 Sep 2004 17:10:51 -0700
> To: "Entourage:mac Talk" <[EMAIL PROTECTED]>
> Subject: Re: Entourage 2004 becomes unresponsive (freezes, hangs, pauses,
> etc.) for minutes at a time
>
> On or near 8/31/04 14:13, Luis Vallecillo at [EMAIL PROTECTED] observed:
>
>> I think there is a bit of confusion as to what I describe as "delays". I am
>> well aware of the delays caused by SpamSieve's AppleScripts, but that is not
>> the case here. Unless there is some crazy runaway script loop that can
>> linger well past the check-email schedule, I don't think they are related at
>> all.
>>
>> When I'm checking email, and ONLY when I'm checking email, are those scripts
>> running...and ONLY then do I see that particular delay (as a matter of fact,
>> it is happening right now as I type). Once all messages have been processed,
>> and SpamSieve is done handling all of those messages (which you can see by
>> looking at SpamSieve's icon on the dock) then we are out of the woods on
>> that particular delay.
>>
> You are correct; the SpamSieve delay is indicated by its icon in the Dock,
> so you are clearly seeing a different problem.
>
>> The delay I'm experiencing is different. This delay will last for probably
>> 15 minutes at a time, and while it is happening SpamSieve is doing
>> absolutely nothing. The only things you notice is:
>>
> Fifteen MINUTES?! Good grief! I have never seen anything like that.
>
>> - ZERO response to clicks on Entourage's interface
>> - Increased hard disk activity
>> - Increased CPU usage for the Database Daemon (about 5%)
>>
> The only thing comparable I have seen has been when some AppleScript times
> out entirely...for instance, throwing up a dialog in Finder that is in the
> background so you don't see it, and then waiting for a response. It hangs
> Entourage. But generally, scripts time out after about 2 minutes. Another
> thing that I've known to do it (also in a script) is a time-consuming
> "whose" clause searching a very large contact database, such as
>
> Every contact whose (first name begins with "B" or last name begins with "B"
> or Company begins with "B")
>
> But I can hardly conceive of such an operation that would take fifteen
> mnutes.
>
> It has to be something Entourage is initiating, since only Entourage is
> affected. A script, a schedule, or something like that.
>
> One other thing that used to hang up for a moderately long time was
>
>
> --
> To unsubscribe:
> <mailto:[EMAIL PROTECTED]>
> archives:
> <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
> old-archive:
> <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
>
>
--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
archives:
<http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
