| Event Id | 8130 |
| Source | MSExchangeAL |
| Description | <object name> added to <object name>. <connection agreement name> |
| Event Information | According to Microsoft: To do this, follow these steps: 1. Start the Exchange System Manager tool. 2. If administrative groups are enabled, expand Administrative Groups, and then expand your administrative group. If administrative groups are not enabled, go to step 3. 3. Expand Servers, right-click the Exchange server that you want to configure diagnostic logging on, and then click Properties. 4. Click the Diagnostics Logging tab, and then click MSExchangeAL in the Services list. 5. In the Categories list, click LDAP Operations, click Maximum, click Address List Synchronization, and then click Maximum. If you are running Exchange 2003, go to step 6. If you are not running Exchange 2003, go to step 7. 6. Click MSExchangeSA in the Services list, click Proxy Generation in the Categories list, and then click Maximum. 7. Click OK. After you have selected a domain RUS to troubleshoot, and after you have increased diagnostics logging on the Exchange server that handles the domain RUS that you want to troubleshoot, you must select an object to use to test the RUS. For example, test the RUS by using a user account that the RUS has not stamped. You can then view the actions that the RUS performs on this object. This behavior may also occur if these objects have not replicated to the domain controller that the Exchange server has selected as the configuration (Config) domain controller. Exchange reads the address lists and the recipient policies from the configuration domain controller and not from the domain controller that the RUS points to. To determine which domain controller is used as the configuration domain controller, follow these steps: 1. Start the Exchange System Manager tool. 2. If administrative groups are enabled, expand Administrative Groups, and then expand your administrative group. 3. Expand Servers, right-click the Exchange server that you want to view the properties of, and then click Properties. 4. Click the Direc |
| Reference Links | How to troubleshoot the Recipient Update Service by using the Application log in Exchange 2000 Server or in Exchange Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.