Event type: error
Event Source: MSExchangeAl
Event type: Address list synchronization
Event ID: 8331
date:
2004-8-5
Event: 18:30:06
User: N / A
Computer: Dell2600
description:
The service encounters an unexpected abnormality, which is found in F: /Titanium/dsa/src/lra/abv_dg/lservagent.cpp (1658)
Symptoms
On a computer that is running Microsoft Exchange Server 2003 and that has more than one logical processor, you may find that Active Directory updates from Exchange 2003 no longer work correctly. The Recipient Update Service does not configure all the Exchange attributes for the user accounts. As a result, these users may not appear in the Global Address List or may not be able to connect to their Exchange mailboxes. Additionally, you may find that event ID 8331 error messages that are similar to the following are repeatedly logged to the application event Log:
TYPE: Error
Source: msexchangeal
Category: Address List Synchronization
Event ID: 8331
Description:
The Service Threw An Unexpected Exception Which Was Caught At Drive: /TITANIUM/DSA/SRC/LRA/ABV_DG/LSERVAGENT.CPP (4511)
You may also receive event ID 8331 error messages that contain a description that reports than an unexpected exception occurred in the Active Directory Connector (Adc.exe) and in the Lotus Notes Dirsynch Connector component (Addxa.dll).
When You Click
Check Name While Configuring Exchange E-Mail Accounts in Microsoft Outlook, You May Receive An Error Message That Is Similar To The Following:
The name could not be resolved. The name could not be match to a name in the address.
Cause
.
Resolution
To resolve this problem, obtain the latest service pack for Exchange Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 836993 How to obtain the latest updates and service packs for Exchange Server 2003
Workaround
To Work Around this Problem, Restart The Appropriate Service. For Example, IF The Source of the Event ID Error Message That Logged to the Application Event Log Is listed as
MSExchangeal, Restart The System Attendant Service.
STATUS
This Problem Was First Corred in Exchange Server 2003 Service Pack 1.
Restart the Microsoft Exchange System Attendant Service to resolve the Microsoft Exchange System Attendant Service.
