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

Exchange 2003 problems with GC

Hi
I have Exch 2k3 in a win2k3 domain that has 3 dcs, 2 of them are GCs.
the thing is that exchange starts and works smoothly, the after a while i start getting these below errors on it,
the things used to get fixed when i reboot the server for a cpl of days.. but now i keep getting these errors..


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            9/17/2004
Time:            11:22:09 AM
User:            N/A
Computer:      <name>
Description:
LDAP Bind was unsuccessful on directory <>.com for distinguished name ''. Directory returned error:[0x51] Server Down.  DC=<...>,DC=<...>,DC=com

For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2103
Date:            9/17/2004
Time:            11:28:14 AM
User:            N/A
Computer:      <name>
Description:
Process MAD.EXE (PID=856). All Global Catalog Servers in use are not responding:
<server1>.com
<server2>.com
 

For more information, click http://www.microsoft.com/contentredirect.asp.




Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            9/17/2004
Time:            10:45:04 AM
User:            N/A
Computer:      <name>
Description:
Process MAD.EXE (PID=476). All Domain Controller Servers in use are not responding:
<1>
<2>
<3>

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeIS Public Store
Event Category:      General
Event ID:      7200
Date:            9/17/2004
Time:            10:33:00 AM
User:            N/A
Computer:      <name>
Description:
Background thread FDoUpdateCatalog halted on database "First Storage Group\Public Folder Store (ServerName)" due to error code 0x80004005.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            9/14/2004
Time:            5:26:25 AM
User:            N/A
Computer:      <name>
Description:
Process MAD.EXE (PID=1112). Topology Discovery failed, error 0xffffffff.

For more information, click http://www.microsoft.com/contentredirect.asp.


and other errors!

Any help is much appreciated.

Thanks
Michel
0
Michel Sakr
Asked:
Michel Sakr
  • 2
  • 2
1 Solution
 
Michel SakrAuthor Commented:
Also after a while I can't access Exchange system manager from the server itself, I get a popup error with "the server is not operational" (DNS records on DNS servers are correct)
... 500 points added
0
 
v_alberCommented:
Hi,
  First try to run: dcdiag /v, netdiag /v on the exchange server (tools are on windows server support tools).
  Search for the errors or failures and let me know what are those.

Thanks.
0
 
v_alberCommented:
Hi again,
  If you have any type of third party monitoring software for UPS for example try to remove it, restart the server and see
  if this behavior happens again.
  If it's not it, go to Exchange System Manager, server properties, Directory Access tab, and try to change Global Catalog  and force replication for DC's.
0
 
Michel SakrAuthor Commented:
dcdiag and netdiag were performed with random errors..
after troubleshooting the issues and seeing the random amount and type of errors, I resolved the issue by updating the Network adapter drivers(!!)
The server is an IBM server xseries 235, It seems this is a common issue on the xseries!

I have now another problem that I will post related to Exchange POP3 and Outlook..

Thanks for the replies
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

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