Forum

Forumlar
Microsoft
Exchange Server
MSExchangeAL Error
 
Bildirimler
Hepsini Temizle

MSExchangeAL Error

 
Exchange Server
Son Cevaplar gön: Savas Demir 16 yıl önce
5 Yazılar
4 Üyeler
0 Reactions
633 Görüntüleme
RSS
 Yusuf Cagan
(@YusufCagan)
Gönderiler: 96
Estimable Member
Konu başlatıcı
 

Exchange Server 2003 Enterprise Edition

MSExchangeAL  Event ID:8231 böyle bir hata alıyorum

 
Gönderildi : 08/07/2008 23:23

 Savas Demir
(@savasdemir)
Gönderiler: 1870
Illustrious Member
 

1. Click Start, click Programs, click Microsoft Exchange, and then click System Manager.
2. Expand the Organization object, and then expand the Recipients container.
3. Click Recipient Update Service.
4. In the right pane, right-click New, and then click Recipient Update Service.
5. Click the domain that does not have an instance of the Recipient Update service and that has users that must be updated by Exchange.
6. Click Next.
7. Choose the server that you want to run the Recipient Update Service and process all the necessary users with the Exchange attributes.
8. Click Next.
9. Click Finish.
10. To manually initiate an update of the recipients in that domain, right-click the Recipient Update Service, and then click Update Now to force an update.

 
Gönderildi : 09/07/2008 01:56

 Eser SOLMAZ
(@esersolmaz)
Gönderiler: 3204
Illustrious Member Yönetici
 

Exchange Recipient Update Service does not stamp proxy addresses in Exchange 2000 Server and in Exchange Server 2003


View products that this article applies to.

function loadTOCNode(){}















Article ID : 286356
Last Review : October 25, 2007
Revision : 4.4

This article was previously published under Q286356

This article is a consolidation of the following previously available articles: 286356, 283134


var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'";
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;


SYMPTOMS


loadTOCNode(1, 'symptoms');

The Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 Recipient Update Service does not create proxy addresses (e-mail addresses) for newly mail-enabled users or public folders when the computer that is running Exchange is in an Exchange mixed-mode environment. An Exchange mixed-mode environment includes Exchange Server 5.5 and Exchange 2000 Server or Exchange Server 2003. Additionally, the following events may be logged in the Event Viewer Application log when you start the Microsoft Exchange System Attendant service.

Back to the top


Event 1


loadTOCNode(2, 'symptoms');

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2035
Description:
The e-mail address description object in the Microsoft Exchange directory for the 'TYPE' address type on 'i386' machines is missing.


Back to the top


Event 2


loadTOCNode(2, 'symptoms');

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2037
Description:
The file version of 'Address\TYPE\I386\3RDPARTY.dll' installed on the local server is not current. Unable to locate a correct version on any server in the site.


Back to the top


Event 3


loadTOCNode(2, 'symptoms');

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2027
Description:
Unable to generate the e-mail address. Unable to load address module 'C:\Exchsrvr\Address\TYPE\I386\3RDPARTY.dll' for address type 'TYPE'. Error 0xc007007e.


Back to the top


Event 4


loadTOCNode(2, 'symptoms');

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Controller
Event ID: 8231
Description:
Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=Name,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=Name,DC=com':'MAD.EXE', error=8000ffff. Taking provider offline.


Back to the top


CAUSE


loadTOCNode(1, 'cause');

The issue can occur because of an invalid or missing third-party e-mail address generator. When the Microsoft Exchange System Attendant service starts, it tries to load an address generation .dll file for each address type that the Recipient Update Service requires to generate the third-party proxy address. If the System Attendant cannot load the .dll file for any address type, the Recipient Update Service does not process the accounts. Additionally, the events that are mentioned in the "Symptoms" section are logged in the Event Viewer Application log.

The generator may be present on any recipient policy. If you do not find the address generator in a recipient policy, check remote sites/administrative groups for the invalid or missing e-mail address generator. If such an invalid e-mail address is added to the gatewayProxy attribute of a Recipient Update Service, the Recipient Update Service no longer updates objects.

Back to the top


RESOLUTION


loadTOCNode(1, 'resolution');

To resolve this issue, either manually copy the missing .dll file from an existing Exchange Server 5.5 computer, or disable that particular address type so that the Recipient Update Service no longer tries to load the .dll file.

Note Every server that is running Exchange that has a Recipient Update Service must have the correct address generation .dll files.

Back to the top


Option 1: Copy the third-party address generation .dll files


loadTOCNode(2, 'resolution');























1. Note the name of the required .dll files that are mentioned in the MSExchangeSA event ID 2027 or 2037.
2. On an existing Exchange Server 5.5 computer, locate the .dll file that is specified in step 1.
3. Create the folder structure that is listed in the MSExchangeSA event ID 2027 or 2037.
4. Copy the .dll file into the location that is specified in the MSExchangeSA event ID 2027 on the Exchange computer that is running the Recipient Update Service.
5. Restart the Microsoft Exchange System Attendant service on the Exchange computer.
6. Monitor the Event Viewer Application log to make sure that the error messages are no longer logged.
7. Right-click a Recipient Update Service in the right pane, and then click Update Now to trigger the Recipient Update Service to update objects. Do this step for each Recipient Update Service that is listed in the right pane.

Back to the top


Option 2: Remove the invalid or unwanted address type from all recipient policies


loadTOCNode(2, 'resolution');














1. Find the policy that has the improper or unwanted e-mail address generator. To do this, follow these steps:













a. In Exchange System Manager, expand Recipients.
b. Click Recipient Policies, and then examine each recipient policy that is listed in the right pane for the e-mail type that is experiencing this issue.

Note The e-mail type that is experiencing the issue is listed in the event ID 2035, 2027, and 2037 error messages that are mentioned in the "Symptoms" section, where TYPE is the e-mail type that is experiencing the issue.
c. If you cannot find the address type that is experiencing this issue in a recipient policy, check site addressing and e-mail address generators at remote sites/administrative groups.
d. When you identify the address type that is experiencing this issue, click to clear the check box for the problem address type from the recipient policy, and then click OK to close the policy properties.
2. Use ADSI Edit or the LDP utility to examine each Recipient Update Service for the address type that is experiencing this issue. To do this, follow these steps.

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

























a. Start ADSI Edit.
b. Expand the Configuration container.
c. Expand Services, click Microsoft Exchange, click Organization Name, and then click Address Lists Container.
d. Click Recipient Update Services.
e. In the right pane, right-click a Recipient Update Service, and then click Properties.
f. In the Select a property to view box, click gatewayProxy.
g. In the Values box, click the address type that is experiencing this issue, and then click Remove.
h. Click OK, and then quit ADSI Edit.
3. In Exchange System Manager, click Recipient Update Services under Recipients.
4. Right-click a Recipient Update Service in the right pane, and then click Update Now to trigger the Recipient Update Service to update objects. Do this for each Recipient Update Service in the right pane.

Back to the top


MORE INFORMATION


loadTOCNode(1, 'moreinformation');

The MSExchangeSA event ID 2035 may be logged when the AddrType attribute does not replicate from the Exchange Server 5.5 directory to the Active Directory directory service.

For additional information about how to troubleshoot replication of the AddrType attribute, click the following article number to view the article in the Microsoft Knowledge Base:
326962 ( http://support.microsoft.com/kb/326962/) Event ID 2035 message occurs when system attendant tries to initialize the Recipient Update Service

 
Gönderildi : 09/07/2008 01:57

 Alper OZDEMIR
(@alperozdemir)
Gönderiler: 703
Prominent Member
 

Biraz bilgi verirseniz mesela ne gibi bir yapınız var exchange dc adc veya member bir server üzerindemi çalışıyor yada yapıda herhangi bir değişiklik yaptınızmı bu hatayı almaya başlamadan önce ?

 
Gönderildi : 09/07/2008 01:57

 Savas Demir
(@savasdemir)
Gönderiler: 1870
Illustrious Member
 

http://support.microsoft.com/kb/275294
linki unutmuşum
selamlar

 
Gönderildi : 09/07/2008 02:01

Forum Jump:
  Önceki Konu
Sonraki Konu  
Paylaş: