Larry
Mon Oct 18 11:00:32 CDT 2004
Thanks for the response, Henry. Per your suggestions,
I've checked the Recipient Update Service properties and
the recipient policies and they all look reasonable. I
believe they're all still at the defaults established when
SBS 2000 was brought up about 16 months ago. I've also
tried "Update Now" on the RUS. The errors and related
address book problem began about 2 months ago. As I
mentioned, the problem has gone away for a time after
restart in the last two instances, and I'm planning to
restart again later today in an attempt to clear up this
latest occurrence.
This is more of "it worked fine, nothing's changed, it no
longer works" kind of problem.
>-----Original Message-----
>Could be a problem with RUS ( Recipient Update Service )
>
>1. In Exchange System Manager, click the Recipients
container, and then
>click the Recipient Update Service container. Look for a
Recipient
>Update
>Service for the domain with users that are stamped with e-
mail addresses
>(for example, Recipient Update Service (domain_name).
>
>2. In the properties of the Recipient Update Service,
make sure that the
>domain controller and Exchange server that are entered
are valid.
>
>3. In Exchange System Manager, click the Recipients
container, and then
>click the Recipient Policies container. Make sure that
the filter rules
>on
>the recipient policies are correct.
>
>--
>Henry Craven {SBS-MVP}
> Melbourne Australia
>
>"Larry" <anonymous@discussions.microsoft.com> wrote in
message
>news:175501c4b307$ddaecd20$a601280a@phx.gbl...
>> For the past couple of months, I've been seeing App. log
>> errors as follows:
>>
>> Source: MSExchangeAL
>> Category: Address List
>> Event ID: 8331
>> The service threw an unexpected exception which was
caught
>> at y:\dsa\src\lra\abv_dg\lservagent.acpp (4664).
>>
>> While in this error state, new users added to Exchange
are
>> not seen in the Global Address List by the Outlook
clients.
>>
>> All the references (especially KB 837444 and the related
>> hotfix) I've come across for this error mention it in
the
>> context of SBS 2003 and usually multiprocessor systems.
>> What I'm running is SBS 2000 on a single processor Dell
>> PowerEdge 2600.
>>
>> The first two times this cropped up the error was
repeated
>> once a minute. In both cases, the problem went away
after
>> restarting the server - at first for 5 weeks, then for 2
>> weeks.
>>
>> The current error state is slightly different in that I
>> got 4 8331 errors in 11 minutes a day and a half ago,
>> after which they stopped - though the Address List
problem
>> remains.
>>
>> I'd appreciate any insight anyone might have on this.
>> Thanks
>
>
>.
>