Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
LDAP returned the error [<error code>] <error description>; when importing the transaction dn: CN=Recipient Update Service (<organization name>),CN=Recipient Update Services,CN=Address Lists Container,CN=<organization name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local
changetype: <operation type>
msExchServer1LastUpdateTime:20010328035022.0Z msExchServer1HighestUSN:9102 msExchServer1HighestUSNVector:<server name>:9102 -.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the MSExchangeAL service?
What is LDAP?
13 - Constraint Violation - no additional info.
14 - Attribute Or Value Exists - Fixed with E2K SP1, the cause of this is that the reply-to address and target address were designed to be the same, which the Recipient Update Service enforced. See ME275511
20 - No Such Object - To resolve this issue, move the Exchange groups to the default User container. See ME290419
32 - Insufficient Rights - This issue can occur if the Recipient Update Service encounters a hidden distribution list. See ME287137
33 - Busy - no additional info.
35 - Unwilling To Perform when importing the transaction - See ME313658.
50 - The network request is not supported. - no additional info.
Recipient Update Service may overwrite the value of the homeMDB attribute for new Exchange Server 2003 users. See ME903291 to resolve this problem.
From a newsgroup post: "Whenever I added a new user, his mailbox was not automatically created the way it was created before SP2 was applied. Therefore, obviously the Default Recipient Policy is not working as it should. When I choose "Apply this policy now" nothing happened. No error messages were generated or anything, no error messages appeared in the Event Viewer, etc. However, nothing happened, no email addresses were updated. If I tried to Rebuild or Update the Recipient Update Services stuff, the service MSExchangeAL generated this error in the Application log.
ME254030 gave me an idea about checking the security settings for the domain container in ADSIEdit. Checking the Domain Container -> Security settings -> Advanced properties -> Exchange Enterprise Servers account, I noticed it was set up to only "Apply to this object only". I changed that to "This object and all child objects" and the error messages have stopped, mailboxes are being created rapidly and the stamping is back to normal. Problem solved. I guess I should look at the security settings a little harder next time. I wonder why this changed with SP2".
As per Microsoft: This event indicates that the Lightweight Directory Access Protocol (LDAP) call resulted in an error as described by the error code/error message. The error message can vary. For example, it could say "Insufficient rights" or "No such Object" or "Attribute or value exists". See MSEX2K3DB for more details on this event.
- Error: 20 - To resolve this issue, move the following groups to the default User container:
1. The Exchange Enterprise Servers group.
2. The Exchange Domain Servers group.
3. The Exchange Services group. See ME822927 for more details.
- Error code: 32 - See ME254030.
- Error code: 32 = Insufficient rights - From a newsgroup post: "After a lot of headaches and conversations with MS on this, I finally got it resolved so I figured I would post for anyone else that may have the same problem in the future. It turns out the exchange domain servers group did not have full control over the recipient update service even though in exchange system manager I could change it to full control (when I did change it, it would snap back to special access after a few hours). Exchange system manager and the actual schema were not in sync. Per ME259221, I had to add a registry entry to the RUS schema via ADSI Edit waited about an hour until it populated (and it only populated on one DC BTW) then within ADSI Edit granted the exchange domain servers full control of RUS and the errors disappeared".
- Error code: 35 - See ME839912 for a hotfix applicable to Microsoft Windows Server 2003.
From a newsgroup post: "I have created a case with Microsoft support and got an answer that we cannot apply a manually created Recipient Policy in a Mixed Mode environment. It is by design".
- Error code: b, error description: "Administration Limit Exceeded" - These issues are related to malformed recipient policies in Exchange. Look for Recipient policies that do not conform to the standards (see article below). This causes the Exchange System Maintenance Process to generate proxy addresses for the indicated malformed policy by appending a sequential number/alpha to the address until this error is generated.
In this instance, it was over 150+ proxy email addresses for each user in the AD. Therefore, you will need to use the LDIFDE tool to remove the offending proxy addresses (or waste hours to remove them one by one).
Refer to articles ME285136 and ME318774 for additional information on this issue.
- Error code: 34 - In a multiple domain environment this problem appeared because the Exchange Domain Servers group from a remote domain was not included in the local Exchange Enterprise Servers group for our domain. Once the remote group was included the errors stopped. Refer to Microsoft TechNet Article 313167.
- Error code: 32 = Insufficient rights - I got this error after upgrading an Exchange 2000 server to Exchange 2003. I realized that there were mail-enabled objects from another domain hosted on this server, and I forgot to run domain prep in that domain. Running Exchange 2003 domain prep in that remote domain fixed the problem.
Error code: 35 - Unwilling To Perform when importing the transaction - See ME813877.
Error 10 - No Such Attribute when importing the transaction, see ME306360.
Max A. Kostioukovitch
Error code 34 - Unavailable when importing transaction. When it occurs along with the Event 1126 from NTDS General in Directory log, the problem is related to network connectivity to Global Catalogs. See ME313167.
Error code 32 - When you mailbox-enable Microsoft Windows 2000 domain accounts in Exchange 2000 Server, the Recipient Update Service (RUS) may not stamp some user accounts with the e-mail address. This issue may occur if the RUS is not assigned the correct permissions to access the mailbox. This may be true if the Allow inheritable permissions from parent to propagate to this object check box on the Security tab in the user's Properties dialog box is not selected.
|Private comment: Subscribers only. See example of private comment|
|Links: ME254030, ME259221, ME275511, ME285136, ME287137, ME290419, ME306360, ME313658, ME313167, ME318774, ME813877, ME822927, ME839912, ME903291, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated