| Details | |
| Product: | Exchange |
| Event ID: | 8339 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.0000.0 |
| Message: | Could not establish a signed Kerberos LDAP connection to %1. Please ensure the domain controller %1 is running Windows 2000 SP3 or later.%4 |
| Explanation | |
| Could not establish a signed Kerberos LDAP connection.
Receiving this event indicates that the Connection Agreement may be stuck. |
|
| User Action | |
| Please ensure the domain controller is running Windows 2000 SP3 or later. | |
Tag: Exchange 6.5.0000.0
Could not connect over LDAP to %1. This domain controller is running %2%3. Please upgrade to Windows 2000 SP3 or later.%4
| Details | |
| Product: | Exchange |
| Event ID: | 8338 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.0000.0 |
| Message: | Could not connect over LDAP to %1. This domain controller is running %2%3. Please upgrade to Windows 2000 SP3 or later.%4 |
| Explanation | |
| Could not connect over LDAP using the version of Windows that the designated domain controller is running.
Receiving this event indicates that the Connection Agreement may be stuck. |
|
| User Action | |
| Please upgrade to Windows 2000 SP3 or later. | |
Related:
The service can’t work properly because the Policy ‘%1’ has an invalid Filter Rule (purportedSearch). Use the Exchange System Management tool to correct this problem. While this error exist new users, contacts and groups won’t receive mail information necessary to them to work properly.%2
| Details | |
| Product: | Exchange |
| Event ID: | 8325 |
| Source: | MSExchangeAL |
| Version: | 6.5.0000.0 |
| Message: | The service can’t work properly because the Policy ‘%1’ has an invalid Filter Rule (purportedSearch). Use the Exchange System Management tool to correct this problem. While this error exist new users, contacts and groups won’t receive mail information necessary to them to work properly.%2 |
| Explanation | |
| The service can”t work properly because the Policy specified in the event has an invalid Filter Rule.
While this error exists, new users, contacts and groups won”t receive mail information. |
|
| User Action | |
| Use the Exchange System Management tool to correct this problem.
Launch the ESM and open Recipients, then Recipient Update Service. Right-click on each RUS listed and choose “update now.” RUS may take some time to update all mailbox entries. The only way to monitor its functioning is with Task Manager. |
|
Related:
ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Universal Distribution group and it is not allowed to have Domain Local groups as members.connection agreement name
| Details | |
| Product: | Exchange |
| Event ID: | 8246 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.0000.0 |
| Message: | ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Universal Distribution group and it is not allowed to have Domain Local groups as members.connection agreement name |
| Explanation | |
| This event occurs because the group is a Universal Distribution group and it is not allowed to have Domain Local groups as members. | |
| User Action | |
| Change the group type from a Universal Security group to a Global Security group. For more information on security groups, see the Windows online documentation. | |
Related:
ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Global Distribution group and it is not allowed to have Domain Local groups or Universal groups as members.connection agreement name
| Details | |
| Product: | Exchange |
| Event ID: | 8245 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.0000.0 |
| Message: | ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Global Distribution group and it is not allowed to have Domain Local groups or Universal groups as members.connection agreement name |
| Explanation | |
| This event occurs because the group is a Global Distribution group and it is not allowed to have Domain Local groups or Universal groups as members. | |
| User Action | |
| Change the group type from a Global Security group to a Universal Security group. For more information on security groups, see the Windows online documentation. | |
Related:
ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Global Security group and it is not allowed to have others groups as members.connection agreement name
| Details | |
| Product: | Exchange |
| Event ID: | 8244 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.0000.0 |
| Message: | ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Global Security group and it is not allowed to have others groups as members.connection agreement name |
| Explanation | |
| This event occurs because the group is a Global Security group and it is not allowed to have others groups as members. | |
| User Action | |
| Change the group type from a global security group to a universal security group. For more information on security groups, see the Windows online documentation. | |
Related:
ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Domain Local Security group and it is not allowed to have others Domain Local groups as members.connection agreement name
| Details | |
| Product: | Exchange |
| Event ID: | 8243 |
| Source: | MSADC |
| Version: | 6.5.0000.0 |
| Message: | ADC was unable to add the member ‘object name’ to the group ‘object name’. This is because the group is a Domain Local Security group and it is not allowed to have others Domain Local groups as members.connection agreement name |
| Explanation | |
| This event occurs because the group is a Domain Local Security group and it is not allowed to have other Domain Local groups as members. | |
| User Action | |
| Change the group type from a Domain Local Security group to domain global or universal. For more information on security groups, see the Windows online documentation. | |
Related:
Error reported by policy group provider ‘name’:’name’, error=error code.error message
| Details | |
| Product: | Exchange |
| Event ID: | 8234 |
| Source: | MSExchangeAL |
| Version: | 6.5.0000.0 |
| Message: | Error reported by policy group provider ‘name’:’name’, error=error code.error message |
| Explanation | |
| This is a generic error about a problem with the Recipient Policies being applied.
Check the application log for other related events. |
|
| User Action | |
| Check the related events and proceed based on what is indicated by those events. If this does not resolve the issues, please call Microsoft Product Support Services. | |
Related:
Invalid policy group provider version for ‘object name’:’DLL name’. Taking provider offline.name
| Details | |
| Product: | Exchange |
| Event ID: | 8232 |
| Source: | MSExchangeAL |
| Version: | 6.5.0000.0 |
| Message: | Invalid policy group provider version for ‘object name’:’DLL name’. Taking provider offline.name |
| Explanation | |
| This is just an informational event that indicates that the System Attendant process initiated the application of recipient policies. | |
| User Action | |
| No user action is needed. | |
Related:
Calendaring agent failed to initialize with error server name.
| Details | |
| Product: | Exchange |
| Event ID: | 8197 |
| Source: | EXCDO |
| Version: | 6.5.0000.0 |
| Message: | Calendaring agent failed to initialize with error server name. |
| Explanation | |
| This failure can occur because of logon failures to mailbox and public folder stores. | |
| User Action | |
| Follow the instructions in the message. | |