Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- From: "Dave Goldman [MSFT]" <dgoldman@xxxxxxxxxxxxxxxx>
- Date: Tue, 17 Oct 2006 14:36:16 -0400
You need to turn up diagnostic logging on the domain controller. The
Lsass.exe process is responsible for communications as far a kerberos, LDAP
calls, etc go. There are only 10 available threads in the lsass process for
NSPI calls (MAPI clients and system attendant use this) for communicating
with the domain controller. 95% of the times lsass is busing doing something
else (looking up security acls, performing authentication, etc) and you will
run in to this. If you think this is going to happen again:
1. Get a netmon trace from your exchange server so you can see what gc the
calls are going to.
2. Get a full performance monitor log of the server with all instances and
counters and you can look at which thread is causing the problem.
3. Get one from the domain controller as well.
If you don't find anything with the diagnostic logging on the domain
controller then open a PSS ticket with that data.
Dgoldman
"John Fullbright [MVP]" <fjohn@donotspamnetappdotcom> wrote in message
news:eXyjR3f8GHA.4084@xxxxxxxxxxxxxxxxxxxxxxx
After W2K3 SP1, did you apply kb898060? If not, you want to do that.
"Amit" <amit.dattani@xxxxxxxxx> wrote in message
news:1161085754.838969.174470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have checked the DCs and there is nothing stated in the event logs on
these servers on the date that my exchange server went down. All is
reported as being fine on my DCs. I have two DCs and one is the GC.
The exchange server is pointing to the DC which is also the GC.
Thanks
Amit
Dave Goldman [MSFT] wrote:
You need to check the logs on your domain controllers as something is
wrong
there. When you rebooted the box and started the services back up they
would
issue another call to the domain controllers and what ever threads were
blocked at the time freed up allowing you back in again.
Dgoldman
"Amit" <amit.dattani@xxxxxxxxx> wrote in message
news:1161083980.373202.7260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All,
Any help on this is very much appreciated!!
Right, here goes! I have two exchange servers which are both running
on
Win 2k3 SP1. Exchange is 2003 SP1. One of my exchange servers comes to
a halt and the only way to get it back up and running is by hard
resetting the server! When this has been rebooted the server works
fine
and reports no errors in the logs after the reboot. However, I am
getting the following event logs showing errors prior to reboot:
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1031
Date: 16/10/2006
Time: 1:35:46 AM
User: N/A
Computer: Exchange
Description: One of the System Attendant's task is blocked.
Function: CMonitoringTask::Work
After this is logged I get the following event logs:
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 16/10/2006
Time: 1:35:46 AM
User: N/A
Computer: Exchange
Description: Process MAD.EXE (PID=2344). All Domain Controller
Servers
in use are not responding:
{Lists all my DCs}
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2114
Date: 16/10/2006
Time: 1:35:46 AM
User: N/A
Computer: Exchange
Description: Process MAD.EXE (PID=2344). Topology Discovery failed,
error 0xffffffff.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9154
Date: 16/10/2006
Time: 1:35:46 AM
User: N/A
Computer: Exchange
Description: DSACCESS returned an error '0x80004005' on DS
notification. Microsoft Exchange System Attendant will re-set DS
notification later.
These event logs are repeated until my exchange box was rebooted and
once it had been rebooted all works fine. Server has been up and
running and showing no errors since but this is very concerning and I
have checked all Microsoft KBs and google groups.
Have checked the DNS settings, made sure that the server can see all
my
DCs. Have also checked all the security and permission settings which
have been posted on here.
My other exchange server works fine and has not rebooted any issues or
problems like this and both were set up at the same time. The only
difference is that the other exchange server is my external SMTP
server
and this server points all external mail to it.
Any help on this is appreciated. I dont know why it is happening on
one
server and not the other! If you need more info let me know.
Thanks in advance
Amit
.
- Follow-Ups:
- References:
- One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- From: Amit
- Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- From: Dave Goldman [MSFT]
- Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- From: Amit
- Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- From: John Fullbright [MVP]
- One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- Prev by Date: Re: NOT Sending Email
- Next by Date: Re: Incoming Email Problems (550 5.7.1. relaying denied)
- Previous by thread: Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- Next by thread: Re: One of the System Attendant's task is blocked. Function: CMonitoringTask::Work
- Index(es):
Relevant Pages
|
