<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx</link><description>No doubt many of you are familiar with the event commonly seen in application logs of Exchange 2000 and 2003 servers, MSExchangeIS event 9548, indicating that the information store came across a disabled user who is missing the msExchMasterAccountSid</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422807</link><pubDate>Wed, 22 Mar 2006 19:36:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422807</guid><dc:creator>Scott Bueffel</dc:creator><description>Thank you, thank you, thank you. &amp;nbsp;I used to have a one-off script to set the attribute for disabled accounts (since we wanted the mailboxes to still function) until NoMAS came along. &amp;nbsp;Actually, I have always preferred MsAccntSidFixer, and I use it to this day. &amp;nbsp;Now I will be able to stop doing that once applied. &amp;nbsp;Thank you so much.&lt;br&gt;&lt;br&gt;Scott.</description></item><item><title>Finally a hotfix to change how Exchange handles user accounts without a master account SID.</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422811</link><pubDate>Wed, 22 Mar 2006 20:06:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422811</guid><dc:creator>Aaron Tiensivu's Blog</dc:creator><description>I'm sure a lot of you have seen event 9548 in your event logs from time to time.&lt;br&gt;If 9548 isn't ringing a bell, maybe this example text will:&lt;br&gt;&lt;br&gt;Disabled user /o= Organization Name /ou= Administrative Group Name /cn=Recipients/cn= Computer Name does not</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422818</link><pubDate>Wed, 22 Mar 2006 20:31:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422818</guid><dc:creator>Deji</dc:creator><description>Well done.&lt;br&gt;&lt;br&gt;Now, let's examine #2 more closely:&lt;br&gt;&lt;br&gt;You wrote: If the user account is enabled ...then use objectSid.&lt;br&gt;&lt;br&gt;No problem with that.&lt;br&gt;&lt;br&gt;You wrote:&lt;br&gt;if it is disabled and has msExchMasterAccountSid set to the well-known SELF SID...then use objectSid&lt;br&gt;&lt;br&gt;My question: Which ObjectSID? The disabled account's SID or SELF?&lt;br&gt;&lt;br&gt;You wrote:&lt;br&gt;if the user is disabled has does not have msExchMasterAccountSid...then use objectSid&lt;br&gt;&lt;br&gt;Again, a question:&lt;br&gt;Which ObjectSID? The disabled account's SID or SELF?&lt;br&gt;&lt;br&gt;The last 2 descriptions are not clear (to me) because, in one instance, there is MAS, and in another, there isn't. So, which SID are we using? The way I read KB903158 is that Exchange will always assume that MAS is equal to SELF SID and will ALWAYS use SELF SID even when there is no MAS associated with the disabled account. But your description does not make this clear when you mentioned objectSID.&lt;br&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422819</link><pubDate>Wed, 22 Mar 2006 20:45:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422819</guid><dc:creator>Deji</dc:creator><description>Forget what I wrote, ladies and gentlemen. The effects of the morning coffee just set in :)</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422820</link><pubDate>Wed, 22 Mar 2006 20:46:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422820</guid><dc:creator>Alex Seigler</dc:creator><description>For both questions, the answer is the objectSID of the disabled user account. &amp;nbsp;When the store sees &amp;quot;SELF&amp;quot;, it grabs the objectSID and uses that (because that is what SELF means).&lt;br&gt;&lt;br&gt;So, for disabled user, if MAS is set to SELF, or if it is not set at all, we use the objectSID of the disabled user. &amp;nbsp;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).&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422835</link><pubDate>Wed, 22 Mar 2006 21:48:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422835</guid><dc:creator>JamesK</dc:creator><description>I think I am missing something. I got the hotfix from support. When I run the hotfix it says: &amp;quot;You can install this hotfix on Service Pack 1 only&amp;quot;.&lt;br&gt;I didn't see mention of this limitation anywhere.</description></item><item><title>Henrik Walther Blog  &amp;raquo; Blog Archive   &amp;raquo; Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422836</link><pubDate>Wed, 22 Mar 2006 21:50:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422836</guid><dc:creator>Henrik Walther Blog  » Blog Archive   » Fix available to alleviate event ID 9548</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msexchange.org/walther/2006/03/22/fix-available-to-alleviate-event-id-9548/"&gt;http://blogs.msexchange.org/walther/2006/03/22/fix-available-to-alleviate-event-id-9548/&lt;/a&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422838</link><pubDate>Wed, 22 Mar 2006 21:55:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422838</guid><dc:creator>Kevin Bingham</dc:creator><description>Beautiful, Andy. &amp;nbsp;The KBarticle indicates a pre-SP2 version, though, with a February date. &amp;nbsp;Will there be a post-SP2 version?</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422840</link><pubDate>Wed, 22 Mar 2006 21:57:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422840</guid><dc:creator>Kevin Bingham</dc:creator><description>That should read &amp;quot;Alex&amp;quot;, of course...</description></item><item><title>re: "You can install this hotfix on Service Pack 1 only</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422841</link><pubDate>Wed, 22 Mar 2006 21:57:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422841</guid><dc:creator>aseigler</dc:creator><description>Correct, the build available right now is for SP1 only. &amp;nbsp;The fix for SP2 servers will be out very shortly.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>Beat Exchange Event ID 9548!</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422886</link><pubDate>Thu, 23 Mar 2006 06:29:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422886</guid><dc:creator>(e)Mail Insecurity</dc:creator><description /></item><item><title>Beat Exchange Event ID 9548!</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422887</link><pubDate>Thu, 23 Mar 2006 06:31:09 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422887</guid><dc:creator>(e)Mail Insecurity</dc:creator><description /></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422938</link><pubDate>Thu, 23 Mar 2006 12:34:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422938</guid><dc:creator>Kevin</dc:creator><description>Thankyou.&lt;br&gt;This has been a major annoyance for us when running daily backup jobs, as backup exec always complains when it finds a mailbox without the SELF permission thats associated to a disabled user. even just one disabled user and the backup job reports as having failed. Thankyou again for finally fixing this up.</description></item><item><title>/var/log  &amp;raquo; Exchange hotfix: finally!</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#422978</link><pubDate>Thu, 23 Mar 2006 19:43:49 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422978</guid><dc:creator>/var/log  » Exchange hotfix: finally!</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://www.varlog.us/2006/03/23/exchange-hotfix-finally/"&gt;http://www.varlog.us/2006/03/23/exchange-hotfix-finally/&lt;/a&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423041</link><pubDate>Fri, 24 Mar 2006 10:10:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423041</guid><dc:creator>Ilja Summala</dc:creator><description>5 years of waiting...finally. Way things are going AD and Exchange might start to be better together after all.</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423050</link><pubDate>Fri, 24 Mar 2006 13:22:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423050</guid><dc:creator>Michel</dc:creator><description>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 mind.&lt;br&gt;&lt;br&gt;I would like a peek on the 'Accepted CDCR' list....</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423055</link><pubDate>Fri, 24 Mar 2006 14:03:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423055</guid><dc:creator>Dave Trevallion</dc:creator><description>Quick question, if we apply the pre SP2 fix onto a SP1 build is it likely that we will then have to apply the post SP2 fix after we apply SP2.&lt;br&gt;&lt;br&gt;We are just planning our SP2 rollout and need to decide to apply the fix now or wait for the post SP2 hotfix version.&lt;br&gt;&lt;br&gt;Very pleased to see this fix though as it's a big issue to us</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423063</link><pubDate>Fri, 24 Mar 2006 16:07:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423063</guid><dc:creator>aseigler</dc:creator><description>Dave Trevallion, that is correct. &amp;nbsp;I expect the SP2 version to be released any day now.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423100</link><pubDate>Fri, 24 Mar 2006 22:23:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423100</guid><dc:creator>Veno Mouse</dc:creator><description>Hmm. ADModify.Net has always worked well in the past. Maybe it's just not well known.</description></item><item><title>re: Exchange 12 setup error</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423109</link><pubDate>Sat, 25 Mar 2006 01:24:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423109</guid><dc:creator>Jewel</dc:creator><description>Total: 6 objects. 5 succeeded, 1 failed. &lt;br&gt;&lt;br&gt;Copy Exchange Files&lt;br&gt;Completed&lt;br&gt;Status: Completed.&lt;br&gt;Elapsed Time: 00:34:16&lt;br&gt;&lt;br&gt;&lt;br&gt;Organization Preparation&lt;br&gt;Completed&lt;br&gt;Status: Completed.&lt;br&gt;Elapsed Time: 00:20:15&lt;br&gt;&lt;br&gt;&lt;br&gt;Bridgehead Server Role&lt;br&gt;Completed&lt;br&gt;Status: Completed.&lt;br&gt;Elapsed Time: 00:02:00&lt;br&gt;&lt;br&gt;&lt;br&gt;Mailbox Server Role&lt;br&gt;Completed&lt;br&gt;Status: Completed.&lt;br&gt;Elapsed Time: 00:04:16&lt;br&gt;&lt;br&gt;&lt;br&gt;Client Access Server Role&lt;br&gt;Completed&lt;br&gt;Status: Completed.&lt;br&gt;Elapsed Time: 00:01:32&lt;br&gt;&lt;br&gt;&lt;br&gt;Unified Messaging Server Role&lt;br&gt;Failed&lt;br&gt;Installing product E:\server\en\i386\Setup\ServerRoles\UnifiedMessaging\esenus32.MSI failed. Fatal error during installation. Error code is 1603.&lt;br&gt;	Fatal error during installation&lt;br&gt;&lt;br&gt;Elapsed Time: 00:14:22&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423157</link><pubDate>Sun, 26 Mar 2006 16:33:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423157</guid><dc:creator>Athif</dc:creator><description>How come the fix is released only for SP1?!!</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423159</link><pubDate>Sun, 26 Mar 2006 17:47:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423159</guid><dc:creator>Alex Seigler</dc:creator><description>Please read the previous comments, the SP2 fix will be available very soon.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423194</link><pubDate>Mon, 27 Mar 2006 09:43:33 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423194</guid><dc:creator>Yonkey</dc:creator><description>This wont work on Exchange 2000 SP3 correct?&lt;br&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423225</link><pubDate>Mon, 27 Mar 2006 16:55:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423225</guid><dc:creator>aseigler</dc:creator><description>Yonkey:&lt;br&gt;&lt;br&gt;Correct, there are no plans at this time to release a fix for Exchange 2000.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423313</link><pubDate>Tue, 28 Mar 2006 05:54:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423313</guid><dc:creator>Matt</dc:creator><description>Alex,&lt;br&gt;PSS needs to get it's act together then. They've just told me four times that the fix is included in SP2 (including after talking to an &amp;quot;engineer&amp;quot;)&lt;br&gt;How are we meant to find out that the SP2 patch is still on its way when PSS don't know and neither the KB article nor this blog entry say so?</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423360</link><pubDate>Tue, 28 Mar 2006 16:14:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423360</guid><dc:creator>Dan Sheehan</dc:creator><description>Well done Alex, you are as usual an exceptional coder!&lt;br&gt;And I suspected Mr.NOMAS wrote this hot fix when I saw the KB article independant of this post. :)&lt;br&gt;&lt;br&gt;Please keep the good mods coming!&lt;br&gt;Dan.</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423773</link><pubDate>Fri, 31 Mar 2006 18:34:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423773</guid><dc:creator>Alan</dc:creator><description>Okay... what I don't understand is. How am I supposed to get this Hotfix? Why isn't it just &amp;quot;available&amp;quot; like every other hotfix Microsoft has ever released. Am I supposed to pay $250 to call PSS so I can get this one hotfix... that's rediculous!! Can't someone just send it to me, I have Exchange 2003 SP1.</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423794</link><pubDate>Fri, 31 Mar 2006 19:31:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423794</guid><dc:creator>Exchange</dc:creator><description>Alan,&lt;br&gt;&lt;br&gt;if you call us and ask for the hotfix up front - you will not be charged for the call.&lt;br&gt;&lt;br&gt;There is actually a pretty good reason for you having to call in for this: this is a hotfix and as such, it did not go through as much testing as rollups or service packs do. So - by calling in, you give us your contact information. If there is a regression or a problem found in the hotfix later, we have a way to contact you and tell you about it and what to do. So - I'd suggest you call in. :)</description></item><item><title>Weekend reading</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#423929</link><pubDate>Sun, 02 Apr 2006 16:05:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423929</guid><dc:creator>subject: exchange</dc:creator><description>Today this list is longer, since I hadn't the time to post it last week. Sorry... &lt;br&gt;&lt;br&gt;Exchange on NAS:...</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424116</link><pubDate>Tue, 04 Apr 2006 04:13:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424116</guid><dc:creator>Shannon</dc:creator><description>PSS do seem to think this fix is *included* in SP2. Apparently, the keyword &amp;quot;kbexchange2003presp2fix&amp;quot; in the KB article means to them that &amp;quot;this fix is included in SP2&amp;quot;.&lt;br&gt;&lt;br&gt;Could the KB be updated to include a definitive statement about SP2 support?&lt;br&gt;&lt;br&gt;I await the SP2 version with bated breath!</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424117</link><pubDate>Tue, 04 Apr 2006 04:23:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424117</guid><dc:creator>White Ninja</dc:creator><description>BEWARE of hotfix 903158 if you are using BlackBerry handheld devices in your environment.&lt;br&gt;&lt;br&gt;I applied 903158 on March 24th and it broke the ability for users to send email from their handheld devices -- everything else seemed to work fine; running E3SP1 and BES 4.0.3.11.&lt;br&gt;&lt;br&gt;KB 912918 did not fix the problem, had RIM and Rogers -- Service Provider on the horn for 8 hours attempting to resolve. End result, removed the hotfix.&lt;br&gt;&lt;br&gt;RIM suggested upgrading to 4.0.4 or 4.1; though could not confirm if this would solve the problem.&lt;br&gt;&lt;br&gt;Still waiting to hear back from RIM SE's for a workaround or fix.&lt;br&gt;&lt;br&gt;BES = POS</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424186</link><pubDate>Tue, 04 Apr 2006 16:09:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424186</guid><dc:creator>Alex Seigler</dc:creator><description>The fix has now been released for SP2. &amp;nbsp;The fix is KB916783. &amp;nbsp;The article is not ready, but the content will be identical to 903158.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424415</link><pubDate>Thu, 06 Apr 2006 00:27:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424415</guid><dc:creator>Jad</dc:creator><description>Thanks for the update. Any comments on the message by White Ninja for BES compatibility ?&lt;br&gt;&lt;br&gt;Thanks !</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424417</link><pubDate>Thu, 06 Apr 2006 00:43:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424417</guid><dc:creator>aseigler</dc:creator><description>I heard of one other instance of BES issues, and it was resolved with 912918. &amp;nbsp;This fix definitely falls into the category in the &amp;quot;Cause&amp;quot; section of 912918.&lt;br&gt;&lt;br&gt;It doesn't explicitly say so in 912918, but I believe that in order for the changes it recommends to take affect immediately, you must restart the store. &amp;nbsp;Otherwise, you must wait for the cache to flush, similar to what is discussed in 179065 and various other articles.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424939</link><pubDate>Tue, 11 Apr 2006 18:46:03 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424939</guid><dc:creator>jdonaldson</dc:creator><description>Installed the SP2 version with no problem for my Blackberry users. &amp;nbsp;I had previously gone through the steps in 912918 and am running BES 4.0.4.&lt;br&gt;&lt;br&gt;-jdonaldson</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#425074</link><pubDate>Wed, 12 Apr 2006 22:35:41 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425074</guid><dc:creator>BGT</dc:creator><description>Where can you get the Post SP2 fix? &amp;nbsp;I have tried to download it from premier support but it states that it is not currently available.</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#425076</link><pubDate>Wed, 12 Apr 2006 23:02:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425076</guid><dc:creator>aseigler</dc:creator><description>BGT: &amp;nbsp;You have to contact support and request KB916783. &amp;nbsp;It is not available for general download.&lt;br&gt;&lt;br&gt;-aseigler</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#425280</link><pubDate>Fri, 14 Apr 2006 22:15:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425280</guid><dc:creator>OliverM</dc:creator><description>Hi there,&lt;br&gt;&lt;br&gt;Hi you guys at M$ - just so you know this patch breaks Blackberry Enterprise Server...&lt;br&gt;&lt;br&gt;I'm guessing you need to finetune it some more or Blackberry have some work to do.&lt;br&gt;&lt;br&gt;Oliver&lt;br&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#425282</link><pubDate>Fri, 14 Apr 2006 22:36:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425282</guid><dc:creator>Exchange</dc:creator><description>OliverM,&lt;br&gt;&lt;br&gt;Please see this: &lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424417"&gt;http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#424417&lt;/a&gt;</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#426600</link><pubDate>Thu, 27 Apr 2006 21:55:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:426600</guid><dc:creator>vwebb</dc:creator><description>attempts to contact PSS for 916783 have failed spectacularly. is there a secret password i can use to get the hotfix? thanks!</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#426617</link><pubDate>Fri, 28 Apr 2006 00:31:55 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:426617</guid><dc:creator>Exchange</dc:creator><description>vwebb,&lt;br&gt;&lt;br&gt;What happened? There is no secret password needed for you to get this patch :). When you call in, just be clear that all you need was a hotfix. I am not sure what happened but maybe try again?</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#426723</link><pubDate>Fri, 28 Apr 2006 21:19:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:426723</guid><dc:creator>vwebb</dc:creator><description>called into PSS support noted i needed a hotfix for exchange 03, gave the article number. the liasons(?) were adamant on a few different occasions the aritcle couldn't be found and without an article there is no hotfix. even tried sighting this blog but no one would bite.</description></item><item><title>re: Fix available to alleviate event ID 9548</title><link>http://blogs.technet.com/exchange/archive/2006/03/22/422799.aspx#427182</link><pubDate>Wed, 03 May 2006 21:58:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:427182</guid><dc:creator>Oldeman</dc:creator><description>When I installed the hotfix (E2003 SP1, Bes 3.6), Blackberry users could no longer send. &amp;nbsp;KB912918 doesn't help because the BES Administrator already had Send As permission. I removed BES Admin and added using the KB article, but there was no change.</description></item></channel></rss>