Thanks guys!  I'll start going through my list. 

-----Original Message-----
From: Petschow, Jeff [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 29, 2003 11:54 AM
To: Exchange Discussions

You have to find the mailbox and remove the permissions for Journal for
this zombie user. I've had these a few times during our migration. When
I see it in the log I first see if I can figure out which department
that person used to work for and go and check the permissions of his
former co-workers and that usually locates the offending mailbox.
Usually takes less then 15 minutes to find.

Jeff


> -----Original Message-----
> From: Carmila Fresco [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 29, 2003 1:19 PM
> To: Exchange Discussions
> Subject: Zombie ACL's
> 
> 
>  
> We're getting this kind of warning on 3 of our E2K servers.  
> The warning
> has different aliases in the x500 address though.  I saw this KB
> http://support.microsoft.com/default.aspx?scid=kb;en-us;318549 but it 
> applies to SP1 & SP2.  We're on SP3.  Tried it anyways but it didn't 
> fix anything.
>  
> Does anyone have any other ideas on how to fix this?
>  
> Thanks,
> Carmila
>  
> --------------------------------------------------------------
> ----------
> Source: MSExchangeIS Mailbox
> Category: General
> Event ID: 9551
>  
> An error occurred while upgrading the ACL on folder [MBX:Mailbox Store

> (NYMAIL)]/Journal located on database "Storage group 1\Store 1A".
> 
> The Information Store was unable to convert the security for 
> /O=BABCOCK & BROWN/OU=BBIMAIL/CN=RECIPIENTS/CN=CSHELBY into a Windows 
> 2000 Security Identifier.
> 
> It is possible that this is caused by latency in the Active Directory 
> Service, if so, wait until the user record is replicated to the Active

> Directory and attempt to access the folder (it will be upgraded in 
> place). If the specified object does NOT get replicated to the Active 
> Directory, use the Microsoft Exchange System Manager or the Exchange 
> Client to update the ACL on the folder manually.
> 
> The access rights in the ACE for this DN were 0x0. 
> 
> 
> 
> 
> 
> 
> This email message may contain information that is confidential and 
> proprietary to Babcock & Brown or a third party.  If you are not the 
> intended recipient, please contact the sender and destroy the original

> and any copies of the original message.  Babcock & Brown takes 
> measures to protect the content of its communications.  However, 
> Babcock & Brown cannot guarantee that email messages will not be 
> intercepted by third parties or that email messages will be free of 
> errors or viruses.
> 
> 
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Web Interface: 
> http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t
ext_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]






This email message may contain information that is confidential and proprietary to 
Babcock & Brown or a third party.  If you are not the intended recipient, please 
contact the sender and destroy the original and any copies of the original message.  
Babcock & Brown takes measures to protect the content of its communications.  However, 
Babcock & Brown cannot guarantee that email messages will not be intercepted by third 
parties or that email messages will be free of errors or viruses.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to