Home > Event Id > Event Id 9548 Exchange 2003

Event Id 9548 Exchange 2003

Is there not a hotfix for Exchange 2000? —Mark S. ****************************************** No, as far as I know there is no hotfix for Exchange 2000 for this issue, only Exchange 2003. —Serdar Is this script it? The tool queries any objects that have no msExchMasterAccountSid attribute and will attempt, with your guidance, to repair them if needed. Any comments on the message by White Ninja for BES compatibility ? Check This Out

Wait for AD Replication or Force AD Replication. Oldeman says: May 9, 2006 at 2:49 am When I installed the hotfix (E2003 SP1, Bes 3.6), Blackberry users could no longer send. This event is also seen in application logs of Exchange 2000 and 2003 servers and in the following KB Articles 291151, 326990, 278966, 328880, 316047. It *seems* that 916783 includes MS06-029 as it also has a much later build date/time (despite MS06-029 being released months after 916783.) Thanks hugely for this patch! have a peek at this web-site

No problem! Merely ensuring that event ID 9548 isn't logged in the application event log for cosmetic purposes isn't the only reason you should set the SELF account with Associated External Account rights. I'd like to do that with all the users -- add the 'self' object. This fix definitely falls into the category in the "Cause" section of 912918.

This was actually preventing access to the mailbox using the "Open Other Users Folder" command. Have others run that script with success. One option you  can do is to delete the corresponding user from the AD, and purge everything related to the said user. ADModify.Net has always worked well in the past.

thanks! First, let's take a look at why this error is logged. I didn't see mention of this limitation anywhere. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=9548&EvtSrc=MSExchangeIS&LCID=1033 x 35 EventID.Net There are two potential causes for this problem: 1.The Active Directory directory service does not have a trust set up to the Microsoft Windows NT Server 4.0 domain

If a disabled Windows account does not have the msExchMasterAccountSID attribute set, the 9548 event ID may be logged under certain conditions. MEMBER FEEDBACK TO THIS TIP A few weeks ago, I obtained this hotfix from Microsoft. The last 2 descriptions are not clear (to me) because, in one instance, there is MAS, and in another, there isn't. They've just told me four times that the fix is included in SP2 (including after talking to an "engineer") How are we meant to find out that the SP2 patch is

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent. https://outhereinthefield.wordpress.com/2010/08/11/exchange-2003-msexchangeis-event-id-9548/ See the link to "NoMas Tool from Microsoft PSS" for information on this tool. Just unzip, and then doubleclick the nomas.exe file to start. The solution was to use logon hours setting to prevent them from ever logging in while leaving their account enabled.

Actually, I have always preferred MsAccntSidFixer, and I use it to this day. his comment is here This is because in order for a mailbox to function within the store, a SID must be associated with the mailbox. x 36 Aaron Schifman I changed the security template on my Domain Controller, which disabled the account. This will fix the problem listed in KB article 555410 http://support.microsoft.com/kb/555410/en-us without having to give the SELF account any privileges.

If the SELF account is not already listed in the Permissions dialog box, you can add it by typing SELF as the account name. We'll then go on to talk about why this error can cause you problems you might not have expected it to. Any other ideas? this contact form If this sounds confusing let me know, and I'll try to make more sense for you :) Posted by: David Fike at Dec 16, 2003 4:50:57 PM Glad to hear it

The later being my preference.   Open the Active Directory Editor tool. Scott. All SELF accounts share a well-known security identifier (SID) that is the same across all domains.

Please use Active Directory MMC to set an active account as this user's master account.

To simplify the transition, break down and tailor the ... even just one disabled user and the backup job reports as having failed. If you receive a non-delivery report when you send a message to a disabled account, then read ME319047 for information on this particular situation. SearchSQLServer DATEADD and DATEDIFF SQL functions for datetime values DATEADD and DATEDIFF SQL functions allow you to easily perform calculations, like adding a time interval from a datetime value. ...

This is more than likely because you disabled a users account for whatever reason. This email address doesn’t appear to be valid. Michel says: March 24, 2006 at 2:22 pm Hmm, have to wait until the PostSP2 version arrives, but since we've waited a long time for this a few more days/weeks don't navigate here See ME328880 and ME324354 for more details.

Open the Mailbox Store properties Select the Limits tab. AD accounts in mixed mode Load More View All Evaluate How to approach white space during an Exchange server 2003 migration Event logs shed light on Exchange Server DSAccess issues ExMerge Everyone elsewill receive an NDR as expected, though the actual NDR that is generated will be one for delivery restrictions (i.e. Submit your e-mail address below.

No problem with that. Logichere: Messages will be received on this account "ONLY FROM" the dummy account/the user itself. x 30 Private comment: Subscribers only. The only time we would use the SID in MAS as-is is when the attribute is populated and not SELF (like an NT4 SID or a SID from a different forest).

My question is, how do you stop the 9548 event from occuring when you have already deleted the AD account? The corresponding KB articlesare 916783(2003 SP2) and 903158(2003 SP1). Now I will be able to stop doing that once applied. Privacy Please create a username to comment.