Home > Event Id > Event Id 8331 Exchange 2003

Event Id 8331 Exchange 2003

Posted by: MARCO BIANCHI at Apr 11, 2004 4:14:05 AM I've called the MS support line and recieved the emailed link and installed the package with no issues in SBS 2k3. the update to the Exchange 2003 SBS SP2 resolved the issuejce122672 Monday, April 11, 2011 5:20 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity Event: 12016 MSExchangeTransport 3 74 176d SBS 2011 Event ID 36888 SChannel Let me know if this works. -- Melissa Travers, MCSE Microsoft Exchange Support Please do not send email directly to this alias. Source

x 18 Thomas Christensen Path: "f:\titanium\dsa\src\lra\abv_dg\lservagent.cpp" - In my case, the event was reported 1-2 times per minute and the address lists were not updated. Exchange event 8331 13. How did you get the error? 3. All documentation I've seen about that service pack only mentions Windows 2003 Server or 2000 Server. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.7638.0&EvtID=8331&EvtSrc=MSExchangeAL

My e-mail is [email protected] Posted by: Costas at May 26, 2004 7:41:52 AM You'll have to call PSS to get patches like this. Close Box Join Tek-Tips Today! Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact [email protected] Please remember to click “Mark as Answer” on

taloola69 (MIS) 21 May 04 08:18 Yes i had this exact same problem with a xeon and SBS 2003......i called MS and asked for the hotfix which solved the problem straight Registration on or use of this site constitutes acceptance of our Privacy Policy. Windows Small Business Server 2003 with SP1 fully supports Exchange Server 2003 SP2. From the Support Center, you can also search the Microsoft Product Support Knowledge Base and contact Microsoft Product Support Services. • Exchange Server TechCenterConnect to Exchange Server-related technical articles and other

We first used a Forest prep/Domain prep to elemenate the error message. Apparently this is an Exchange 2003 error that was supposed to be fixed in SP1. Posted by: Michael B Smith at Mar 26, 2004 11:15:06 AM Has anyone actually ran this with success? https://social.technet.microsoft.com/Forums/exchange/en-US/bf0561ec-5fd3-4cd8-85d1-b0fdfe5f3f88/source-ms-exchangeal-event-id8331?forum=exchangesvrgenerallegacy On the servers giving the 8331, we have seen the issues like when adding a user or group, you find they are not added in the Global Address list".

Posted by: Neil Hobson at May 26, 2004 1:00:48 PM archives by month December 2009 November 2009 October 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 The call is free of charge. afternoon. Already a member?

x 17 Jason Clarke There is a hotfix available for this problem, and is available from Microsoft Product Support Services. http://www.eventid.net/display-eventid-8331-source-MSExchangeAL-eventno-3416-phase-1.htm Yes SP1 for exchange can be applied :) 2. Cheers, Marty that Top Exchange 2003 Event ID 8331 by Melissa Tr » Thu, 20 Nov 2003 04:55:36 i Marty, Spruce and Zane If the problem recurs in For more information, click http://www.yqcomputer.com/ Event Type: Error Event Source: MSExchangeAL Event Category: Address List Synchronization Event ID: 8331 Date: 11/11/2003 Time: 8:49:17 PM User: N/A Computer: Description: The service threw

Yes SP2 is inclusive of SP1 - and you dont need a special version for SBS - just backup first as usuall :) Go to Solution 4 2 Participants Pete Long(4 this contact form Take Survey Question has a verified solution. Yes. The version of your Exchange Server. 2.

See example of private comment Links: ME821908, ME831464, ME837444, ME843539, E-Bitz - SBS MVP the Official Blog, WINSUG SBS 2003 Info, Service Pack 1 for Exchange 2003, MSEX2K3DB Search: Google - The reason the domainprep fixes the problem is because it creates these groups again, in the Users container. Take yourself to another level. have a peek here Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature.

Concepts to understand: What is the role of the MSExchangeAL service? Address List Error Event ID: 8331 7. A.

Red Flag This Post Please let us know here why this post is inappropriate.

How did you get the error? 3. If anyone has ran this is there anything I need to look out for? Register now while it's still free! The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items… CodeTwo Exchange Outlook Email Software Advertise Here 592 members asked questions and

x 23 Doug Masters The upcoming MS KnowledgeBase article is ME837444. Ask Questions for Free! Privacy Policy Support Terms of Use Login with LinkedIN Or Log In Locally Email Password Remember Me Forgot Password?Register ENGINEERING.com Eng-Tips Forums Tek-Tips Forums Search Posts Find A Forum Thread Check This Out This can be beneficial to other community members reading the thread.

Event ID: 8331 Source: MSExchangeAL Source: MSExchangeAL Type: Error Description:The service threw an unexpected exception which was caught at () English: Request a translation of the event description x 22 EventID.Net As per Microsoft: "This event is logged when the Recipient Update Service cannot stamp Exchange attributes on Active Directory objects. Their is no article currently (3/26/2004) available for the hotfix. x 22 EventID.Net Path: y:\dsa\src\lra\abv_dg\lservagent.cpp - Reported on W2K3 running Exchange 2003 - no additional info Path: f:\titanium\dsa\src\lra\abv_dg\lservagent.cpp - Reported on Small Business Server 2003.

Covered by US Patent. Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Does SP2 work on Microsoft Windows Small Business Server 2003? Several users stated that installing the Exchange 2003 Service Pack 1 solved this problem for them.

Just restart the MSE System Attendant service.