Re: SBS2003 STD Exchange 2003 SP1 errata?

From: Les Connor [SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 06/30/04


Date: Wed, 30 Jun 2004 15:59:37 -0500

At this point I'd recommend installing SP1. It will fix your errors. After
installation:

a) disable the store.exe alert (if you wait for the alert, it has
instructions on how to disable).
b) use DOMAIN\username to login to OWA. (the login page gives you this
instruction).
c) If your OMA device doesn't allow DOMAIN/username (many do) then you have
to wait a few days for a fix to be released (should be very soon).

The reason you don't want to use the workarounds is that some things won't
work, such as spellcheck and links embedded in emails.

Note that if you do the workarounds, they have to be manually undone prior
to installing the hotfix.

-- 
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Mark Medici" <mark@dbma.EXAMPLE.com> wrote in message
news:udcuigsXEHA.2824@TK2MSFTNGP10.phx.gbl...
> Excuse me if this has already been addressed.  I can only view the past 2
> weeks worth of newsgroup traffic, and could not find definitive
information
> regarding Exchange 2003 SP1 on SBS2003.  I also searched MS Knowledgebase
> for issues (only the STORE.EXE memory alert problem is returned).
>
> I have a customer running SBS on a Compaq server that uses a single
> Pentium-4 with HTT (Hyperthreading Technology).  They are experiencing
> frequent MSExchangeAL Event ID 8331 errors, (unexpected exception in
> lservagent.cpp), and are having occasional setup problems in Outlook (The
> name could not be resolved. The name could not be matched to a name in the
> address list). According to MSKB article 837444, these issues are related
> and are fixed in Exchange 2003 SP1.
>
> So I need to decide which is worse: the current problems or the new
problems
> that SP1 introduces.  I'm not confident I understand the issues with
> Exchange 2003 SP1 on SBS 2003.  All I've found so far are:
>
>     1.    Spurrious STORE.EXE memory utilization errors
>     2.    OWA users must logon with domain\username instead of just
> username.
>     3.    OMA users also must logon with domain\username
>
> I also found one message that indicates Remote Web Workplace is somehow
> affected.
>
> Is this the full extents of the problems observed installing Ex2k3-SP1 on
> SBS2k3?  These seem to be issues that can easily be worked-around.  Or are
> there other, more troublesome issues introduced?
>
> Thanks
>
>


Relevant Pages

  • Re: Windows XP SP1 BUG?
    ... theso insert the cd & do a upgrade will fix this? ... what about un installing ... sp1 will that work i will try it tells me a few programs may not run if i do ... up on the recovery console and went through the "upgrade install". ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Problems when pinging
    ... What I would suggest is you report it as a bug, in the new bug feedback forum: ... First of, the KB article you referred to, is included in .NET 2.0 SP1. ... So installing 3.5 will not change anything for a 2.0 SP1 application at all. ... but this fix didn't work. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Cryptographic service will not run
    ... Select "Normal Startup", click "apply" and reboot. ... Try installing the Updates again. ... I have ran Norton's FixBlast AND | McAfee's Stinger fix and have tried to apply the patch | from Microsoft. ... | XP REQUIRES SP1 to be installed, this PC does NOT have | SP1. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Problems when pinging
    ... First of, the KB article you referred to, is included in .NET 2.0 SP1. ... So installing 3.5 will not change anything for a 2.0 SP1 application at all. ... but this fix didn't work. ... "The upgrade patch cannot be installed by the windows installer service ...
    (microsoft.public.dotnet.languages.vb)
  • New mail - Desktop Alert Settings - Longer than 30 seconds?
    ... Win XP, Office Outlook 2003 SP1 ... But I want this alert to stay at my screen until I have open the mail, ... Is there any way to fix this setting? ...
    (microsoft.public.outlook.general)

Quantcast