Dave
Thu Jul 14 11:29:44 CDT 2005
Sounds like a good plan installing the patches and upping the logging.
No, I haven't had this problem - I just did a couple of searches based on
the info in your original post (MSKB, eventid.net, google).
"Andy" <andy.baguley@cwcom.net> wrote in message
news:%23xJxY3IiFHA.2916@TK2MSFTNGP14.phx.gbl...
> Have you the same issue Dave?
>
> Re patching, I think I am one behind on Exchange. There is a SP rollup
> that MSBA found recently that I need to do, other than that it is SP3.
>
> I might throw that in when I re-boot later.
>
> No changes done for at least a month prior to the first occurrence.
>
> My other "play" sbs2K is patched the same, and that is running OK.
>
> Some of the leads I have found point to problems with RUS, but I've had a
> quick look and all seems in order there. When I get it running again I'll
> turn up the logging on MSExchangeAL, and wait !!"!
>
>
>
>
> "Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in
> message news:eOinguIiFHA.3448@TK2MSFTNGP12.phx.gbl...
>> You're right, everything I found points to either Exchange 2003 or
>> something besides MSExchangeAL. I hate to say it, but when I run into
>> something that's not any better documented than that, I call PSS.
>> Especially with Exchange, where at my company (and probably yours) we
>> have a lot of important data at risk.
>>
>> You're current on Exchange service packs? Make any changes around the
>> time this started?
>>
>>
>> "Andy" <andy.baguley@cwcom.net> wrote in message
>> news:u7bSwbIiFHA.708@TK2MSFTNGP09.phx.gbl...
>>> This SBS 2K installation has been running like a train for 2yrs, no
>>> probs.
>>>
>>> Recently two 8331 problems (16th June and today) have caused Exchange
>>> issues.
>>>
>>> Users are unable to send mail, it remains in the Outlook outbox.
>>>
>>> I've tried re-starting the Exchange services, but the Exchange
>>> Information store will not re-start. It just hangs.
>>>
>>> The first time a re-boot fixed it, but it hasn't lasted long !!!
>>>
>>> Google gives plenty of info on this for Exchange 2003, but little for
>>> Exchange 2000. There are some previous posts, but no definitive
>>> solutionThe entry is:-
>>>
>>> "MSExchangeAL"
>>> "Address List"
>>> "The service threw an unexpected exception which was caught at
>>> g:\dsa\src\lra\abv_dg\lservagent.cpp(4664)"
>>>
>>> The Application log is full of them, as the entry repeats every 60secs
>>> from the initial one.
>>>
>>> This is worrying, as a re-boot is not always convenient. Also there is
>>> no logical g: drive on this machine!!!
>>>
>>> Are there any regular maintenance tasks I should be performing on
>>> Exchange, apart from patching, which I do every two months or so?
>>>
>>> Any other pointers to the problem / solution?
>>>
>>> Re-install exchange?
>>>
>>> Thanks for any assistance.
>>>
>>> Andy
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>