I am seeing this too. I saw a posting on another list that said that the
problem could be a corrupt attachment in a filed message.   Doubt it...Did
not have this error before the update. Hopefully this is addressed. I am
running a G5 1gb memory...



Brian K. Spahr
Network/IT Manager
SSPC
40 24th St. Pittsburgh, Pa. 15222
(412) 281-2331 x220
fax (412) 281-9992
[EMAIL PROTECTED]
http://www.sspc.org
SSPC:  The Society for Protective Coatings, Promoting Coatings. Providing
Knowledge. 
Visit http://www.sspc.org for more information on SSPC.



> From: David Morganstein <[EMAIL PROTECTED]>
> Reply-To: "Entourage:mac Talk" <[email protected]>
> Date: Sat, 25 Mar 2006 15:00:19 -0500
> To: "Entourage:mac Talk" <[email protected]>
> Conversation: Problems after 11.2.3 Update
> Subject: Re: Problems after 11.2.3 Update
> 
> 
> I haven't seen any replies with a 'fix' for this.  I'm getting the same
> error the day after updating.  I repaired permissions, rebooted, rebuilt
> twice.  I did see a problem after the first repair (followed by a Verify
> that said all was well), namely 'gray lines' in the middle of a folder of
> email.  Either some emails were not appearing or the window was not drawn
> correctly.
> 
> I have had NO problems with Ent 2004 prior to  this update.
> 
> Rather disappointing...
> 
> Anyone seen a fix yet?
> 
> David
> 
>> I also received this error numerous times. I did a total rebuild which took
>> a long time and then still received the errors multiple times. I haven't
>> gotten the error message for a couple days, but don't know what it was.
>> After the total rebuild and getting an error I scanned the database and it
>> said there were no problems.
>  
>>> However, it also began producing this error message:
>>> 
>>> Your Office database is damaged.
>>> Do you want to quit MSN Messenger and all Microsoft Office programs so that
>>> the Database Utility can run?
>>> Cancel         Quit Office Programs
>>> 
>>> I ran the Database Utility and, after a couple of attempts, arrived at
>>> what seemed like a successful end. I then compacted the data base.
>>> 
>>> After restarting Entourage, I got the same error message again; I redid the
>>> steps to try to fix the problem. Following that, the same error message
>>> reappeared and I cancelled it. I see now that it has come back again, and
> 
> --
> David Morganstein
> [EMAIL PROTECTED]
> 
> 
> -- 
> 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/>

Reply via email to