| Details | |
| Product: | Exchange |
| Event ID: | 9057 |
| Source: | CDOEXM |
| Version: | 6.5.6940.0 |
| Component: | CDO for Exchange Management |
| Message: | NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service.New clients will be refused until a Global Catalog is available.After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients. |
| Explanation | |
|
This event indicates that the Name Service Provider Interface (NSPI) Proxy cannot contact any global catalogs that support the NSPI Service. New clients will be refused until a global catalog is available. A domain controller that was recently promoted to a global catalog may not have been restarted. A global catalog must be restarted in order for the NSPI interface to be available. |
|
| User Action | |
|
Check the general health of the global catalog servers. If you have recently promoted a domain controller to global catalog, remember that it must be rebooted in order to support MAPI clients. |
|
Tag: Exchange 6.5.6940.0
ADC cannot replicate to Exchange 5.5. because, on this server, LDAP Client Integrity is set to ‘2’ (always sign.) Exchange 5.5 does not support LDAP signing. To allow this serverto connect to 5.5., set the registry key to 0 (never sign) or 1 (sign if possible)
| Details | |
| Product: | Exchange |
| Event ID: | 8341 |
| Source: | MSADC |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory Connector |
| Message: | ADC cannot replicate to Exchange 5.5. because, on this server, LDAP Client Integrity is set to ‘2’ (always sign.) Exchange 5.5 does not support LDAP signing. To allow this serverto connect to 5.5., set the registry key <registry key>to 0 (never sign) or 1 (sign if possible)<value> |
| Explanation | |
|
The Active Directory Connector (ADC) cannot replicate to Exchange 5.5. because, on this server, Lightweight Directory Access Protocol (LDAP) Client Integrity is set to 2 (Always sign). Exchange 5.5 does not support LDAP signing. |
|
| User Action | |
|
Exchange 5.5 does not support LDAP signing. To allow this server to connect to Exchange 5.5., set the registry key to 0 (Never sign) or to 1. |
|
Related:
Could not connect over LDAP to . This domain controller is running . Please upgrade to Windows 2000 SP3 or later.
| Details | |
| Product: | Exchange |
| Event ID: | 8338 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory DXA Connector |
| Message: | Could not connect over LDAP to <server name>. This domain controller is running <value> <value>. Please upgrade to Windows 2000 SP3 or later.<connection agreement name> |
| Explanation | |
|
Could not connect over Lightweight Directory Access Protocol (LDAP) using the version of Windows that the designated domain controller is running. If you receive this event, this could indicate that the connection agreement is unable to function. |
|
| User Action | |
|
Upgrade to Windows 2000 SP3 or later. |
|
Related:
The service can’t work properly because the Policy ” 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.
| Details | |
| Product: | Exchange |
| Event ID: | 8325 |
| Source: | MSExchangeAL |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Recipient Update Service |
| Message: | The service can’t work properly because the Policy ‘<name>‘ 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.<service name> |
| Explanation | |
|
The service cannot work properly because the Policy specified in the event has an invalid Filter Rule. While this error exists, new users, contacts and groups will not receive mail information. |
|
| User Action | |
|
Use the Exchange System Management tool to correct the problem. Launch the ESM and open Recipients, then Recipient Update Service. Right-click on each RUS listed and choose “update now.” The Recipient Update Service could take some time to update all mailbox entries. The only way to monitor its functioning is with Task Manager. |
|
Related:
The service could not update the entry ” because inheritable permissions may not have propagated completely down to this object yet. The inheritance time may vary depending on the number of Active Directory objects within the domainand also the load of your domain controllers. To correct this problem, verifythat the Exchange permissions have been propagated to this object and then forcea rebuild for the Recipient Update Service on this domain.
| Details | |
| Product: | Exchange |
| Event ID: | 8317 |
| Source: | MSExchangeAL |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Recipient Update Service |
| Message: | The service could not update the entry ‘<object name>‘ because inheritable permissions may not have propagated completely down to this object yet. The inheritance time may vary depending on the number of Active Directory objects within the domainand also the load of your domain controllers. To correct this problem, verifythat the Exchange permissions have been propagated to this object and then forcea rebuild for the Recipient Update Service on this domain.<distinguished name> |
| Explanation | |
|
This event indicates that the Recipient Update Service (RUS) could not update an object because of a lack of permissions. This issue may occur when the Recipient Update Service does not have permissions to the particular object (noted in the event), either because permission inheritance is blocked, or because the Exchange Enterprise Group is missing permissions at the domain level. |
|
| User Action | |
|
Run SETUP/Domainprep to reset permissions. |
|
Related:
The service could not update the entry ” because inheritablepermissions are not propagated to this object. The inheritablepermissions may be disabled because the object belongs to aWindows 2000 administrative group or the inheritable permissionswere disable explicitly by an administrator.
| Details | |
| Product: | Exchange |
| Event ID: | 8315 |
| Source: | MSExchangeAL |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Recipient Update Service |
| Message: | The service could not update the entry ‘<object name>‘ because inheritablepermissions are not propagated to this object. The inheritablepermissions may be disabled because the object belongs to aWindows 2000 administrative group or the inheritable permissionswere disable explicitly by an administrator.<name> |
| Explanation | |
|
All users or groups (security principals) that belong to any of the three built-in administrators groups (domain administrators, schema administrators, or enterprise administrators) have their “inheritence security” turned off automatically. Enabling inheritence permissions allows all objects under a container to inherit the permissions of its parent container. In this case, Recipient Update Service does not have permission to update those objects. This option might have been turned off intentionally to prevent these objects from inheriting permissions. |
|
| User Action | |
|
For the user to be updated by Recipient Update Service, you must turn on the inheritence. Use the Security tab of the user’s Properties to make the change. |
|
Related:
ADC will not replicate entry ” to the Exchange 5.5 directory because only MAPIpublic store objects are replicated to the Exchange 5.5 directory.
| Details | |
| Product: | Exchange |
| Event ID: | 8311 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory DXA Connector |
| Message: | ADC will not replicate entry ‘<object name>‘ to the Exchange 5.5 directory because only MAPIpublic store objects are replicated to the Exchange 5.5 directory. <connection agreement name> |
| Explanation | |
|
Unlike Exchange 5.5 in which only MAPI Public Folders could exist, in Exchange 2000 we can also create NON-MAPI Public Folders (also called Application Public Folders). This event indicates that, during replication, the Active Directory Connector (ADC) encountered a NON-MAPI Public Folder store which it will not replicate to the Exchange 5.5 directory because the Exchange 5.5 directory has no concept of a NON-MAPI Public Folder Store. |
|
| User Action | |
|
No user action is required. |
|
Related:
ADC will not replicate entry ” because the following required attribute(s)are missing from the source entry: .
| Details | |
| Product: | Exchange |
| Event ID: | 8305 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory DXA Connector |
| Message: | ADC will not replicate entry ‘<object name>‘ because the following required attribute(s)are missing from the source entry: <attribute name>.<connection agreement name> |
| Explanation | |
|
This event indicates that when the Active Directory Connector (ADC) tried to replicate the named source object to the target directory, it could not find one of the required attributes on the source object. Without this important attribute, it would be meaningless for the ADC to replicate this object to Active Directory. |
|
| User Action | |
|
Determine why the required attributes are missing from the source object and rectify the condition. |
|
Related:
ADC will not replicate entry ” because protocol settings for this protocol type are not replicated from the Exchange 5.5 directory to the Active directory.
| Details | |
| Product: | Exchange |
| Event ID: | 8304 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory DXA Connector |
| Message: | ADC will not replicate entry ‘<object name>‘ because protocol settings for this protocol type are not replicated from the Exchange 5.5 directory to the Active directory. <connection agreement name> |
| Explanation | |
|
Active Directory Connector (ADC) only replicates three protocols types: Internet Message Access Protocol version 4 (IMAP4), Postoffice Protocol version 3 (POP3), and Network News Transfer Protocol (NNTP). For all other server-level protocol type object, for example, Lightweight Directory Access Protocol (LDAP), this message appears. |
|
| User Action | |
|
No user action is required. |
|
Related:
ADC will not replicate entry ” to ” because the target object has a higherfile version than the source object.
| Details | |
| Product: | Exchange |
| Event ID: | 8302 |
| Source: | MSExchangeADDXA |
| Version: | 6.5.6940.0 |
| Component: | Microsoft Exchange Active Directory DXA Connector |
| Message: | ADC will not replicate entry ‘<object name>‘ to ‘<object name>‘ because the target object has a higherfile version than the source object. <connection agreement name> |
| Explanation | |
|
In Exchange 5.5, the Addr-Type objects that describe the proxy-address generation dynamic-link libraries (DLLs) reside at the site level, while in Exchange 2000 these objects reside at the organization level. When Active Directory Connector (ADC) replicates these objects, if an object of the same type in the target Active Directory and if it has a file version higher than the source object, ADC will not replicate the source object. |
|
| User Action | |
|
No user action is required. |
|