• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 635
  • Last Modified:

Issue with Windows 2003 server hanging

Hello

We have a server that has recently started to freeze/hang every few weeks and requires a cold shutdown

On investigating the logs created at the time of the issue I have found the events below in the Application Log.

I've checked exchnage using message tracker to see if any mail of an outlandish size was blocking Exchange but nothing unusual appears

Server 2003 R2 SP2
Exchange 2003 SP2

Thanks in advance for any assistance
OCD Team

Event Logs

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1031
Date:            11/02/2009
Time:            09:43:33
User:            N/A
Computer:      SPDSERVER
Description:
One of the System Attendant's task is blocked.
Function: CMonitoringTask::Work
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1031
Date:            11/02/2009
Time:            09:47:33
User:            N/A
Computer:      SPDSERVER
Description:
One of the System Attendant's task is blocked.
Function: COffLineABScanTask::Work
For more information, click http://www.microsoft.com/contentredirect.asp.




Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            11/02/2009
Time:            09:48:48
User:            N/A
Computer:      SPDSERVER
Description:
LDAP Bind was unsuccessful on directory SPDSERVER.SPD.lan for distinguished name ''. Directory returned error:[0x55] Timeout.    
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1031
Date:            11/02/2009
Time:            09:50:33
User:            N/A
Computer:      SPDSERVER
Description:
One of the System Attendant's task is blocked.
Function: CPollDomainExchangeServersGroup::Work
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            11/02/2009
Time:            09:52:48
User:            N/A
Computer:      SPDSERVER
Description:
LDAP Bind was unsuccessful on directory SPDSERVER.SPD.lan for distinguished name ''. Directory returned error:[0x55] Timeout.    
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            11/02/2009
Time:            09:55:21
User:            N/A
Computer:      SPDSERVER
Description:
Process MAD.EXE (PID=5796). All Domain Controller Servers in use are not responding:
SPDSERVER.SPD.lan
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            11/02/2009
Time:            09:59:10
User:            N/A
Computer:      SPDSERVER
Description:
LDAP Bind was unsuccessful on directory SPDSERVER.SPD.lan for distinguished name ''. Directory returned error:[0x55] Timeout.    
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            11/02/2009
Time:            10:01:10
User:            N/A
Computer:      SPDSERVER
Description:
LDAP Bind was unsuccessful on directory SPDSERVER.SPD.lan for distinguished name ''. Directory returned error:[0x55] Timeout.  DC=SPD,DC=lan
For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            11/02/2009
Time:            10:01:51
User:            N/A
Computer:      SPDSERVER
Description:
Process MAD.EXE (PID=5796). All Domain Controller Servers in use are not responding:
SPDSERVER.SPD.lan
For more information, click http://www.microsoft.com/contentredirect.asp.




Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            11/02/2009
Time:            10:03:10
User:            N/A
Computer:      SPDSERVER
Description:
LDAP Bind was unsuccessful on directory SPDSERVER.SPD.lan for distinguished name ''. Directory returned error:[0x55] Timeout.    
For more information, click http://www.microsoft.com/contentredirect.asp.




0
ocdteam
Asked:
ocdteam
  • 3
  • 2
1 Solution
 
MesthaCommented:
All of those errors mean the same thing.
Can't see the domain controller. There are some connectivity issues between the Exchange server and the domain controller. NIC, cable, switch, something like that.
Check the NIC drivers are up to date - if they are not dated 2008 then they are old.

-M
0
 
ocdteamAuthor Commented:
Hello Mestha

Thanks for the reply.

Should have said when posting question that both Exchange and DC are in the same box.
Concerened about the server freezing and wondering if it was caused by these errors are they relate to the same time period.

Could they be caused by the server freezing as opposed to errors causing the server to freeze?

Cheers OCD Team
0
 
MesthaCommented:
Its unusual to see the errors occur when everything is on the same machine. Is the machine under a heavy load? If the machine is, then similar errors could occur because Exchange (the application) cannot actually talk to the domain controller function.

-M
0
 
ocdteamAuthor Commented:
Issue looks to be resolved.

Was using Log Me In IT Reach as remote suppport tool.

Looks like the mirror driver causing server to freeze. Have un-installed LMI and issue hasn't returned.

Work mate Has had this issue happen on another server.

Thanks fr any assistance
0
 
ocdteamAuthor Commented:
m
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now