Solved

Exchange System Attendant stops when starting, AD LDAP error in Event Log.

Posted on 2008-06-19
3
1,917 Views
Last Modified: 2011-10-03
Hi,

I have a server where Exchange System Attendant does not start. If I start it, it will stop automatically after a few seconds. A look in the event logs shows the following errors:

System Log:
Source: Service Control Manager (Event ID 7031)
The Microsoft Exchange System Attendant service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

Application Log:
Source: Microsoft Exchange Serv (Event ID 1000)
The description for Event ID ( 1000 ) in Source ( Microsoft Exchange Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: mad.exe, 6.5.7638.1, 430e737d, ntdll.dll, 5.2.3790.3959, 45d70ad8, 0, 000417af.

Directory Service Log:
Source: NTDS LDAP (Event ID: 1535)
Internal event: The LDAP server returned an error.
 
Additional Data
Error value:
0000208D: NameErr: DSID-031001A8, problem 2001 (NO_OBJECT), data 0, best match of:
      ''

Source: NTDS LDAP (Event ID: 1535)
Internal event: The LDAP server returned an error.
 
Additional Data
Error value:
00002024: LdapErr: DSID-0C090769, comment: Error processing notification request, data 0, vece

Source: NTDS LDAP
Category: LDAP Interface
Event ID: 1535
Internal event: The LDAP server returned an error.
 
Additional Data
Error value:
0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
      'CN=Address-Templates,CN=Addressing,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxxx,DC=xxxxxx,DC=com,DC=au'

If I try to start it many times, the system attendant will eventually start and stay running. However when it is started, LSASS.EXE will be running at high CPU usage, about 50%-60%.

I will also see the following warning in Event Logs:

Source: NTDS REplication (Event ID:2094)
Performance warning: replication was delayed while applying changes to the following object. If this message occurs frequently, it indicates that the replication is occurring slowly and that the server may have difficulty keeping up with changes.
Object DN: CN=internal 18924472,CN=Microsoft Exchange System Objects,DC=xxxxxxxx,DC=xxxxxxx,DC=com,DC=au
 
Object GUID: d7001eec-effa-4490-adb2-78eef4ba04e8
 
Partition DN: DC=xxxxxx,DC=xxxxxxx,DC=com,DC=au
 
Server: 422d9ad7-d2ab-44d1-aff6-41c599ff9cd9._msdcs.xxxxxx.xxxxxx.com.au
 
Elapsed Time (secs): 18


I believe that the LDAP issue is causing the system attendant to not start and also when it does start, CPU usage is high because LSASS is waiting until it timeouts and is backing up other requests.

Does anyone have any ideas to fix the (NO_OBJECT) issue? I have been pulling my hair out over this issue for a few days now.

Server is running Exchange 2003 SP2 and Windows Server 2003 SP2. I have reapplied SP2 to Exchange, this was before I suspected it of being a AD/LDAP problem. Exchange server is also a DC, There is another DC locally and another DC at a remote site.
0
Comment
Question by:theblip
  • 2
3 Comments
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 21825113
0
 
LVL 59

Accepted Solution

by:
Darius Ghassem earned 500 total points
ID: 21825130
Actually use this instead of of the microsoft website.
From a command prompt try running netdiag /fix this could
repopulate the dns records for your dc

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located in the download section on my website at
http://www.pbbergs.com/windows/downloads.htm#DCDIAG

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.
0

Join & Write a Comment

Synchronize a new Active Directory domain with an existing Office 365 tenant
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video discusses moving either the default database or any database to a new volume.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now