Hello All,
I've been having some issues with an install of Exchange Server 2000 (on Windows 2000 Server) I run. The primary probelm is a serious slowdown in Exchange and ultimatley server instability or client access problems. Here are more details...
Here are the basic details:
There are only two servers:
Server #1:
- A DC running Windows 2000 Server (AD Installed) (SP4)
- Fax Services
- RAS (Dial-Up) server
Server #2:
- Windows 2000 Server (SP)
- Running DNS (Dynamic Updates Enaabled)
- Exchange Server 2000 (6249.4 Service Pack 3)
Clients:
- Windows 2000 Pro (SP4)
- Office XP SP1
10 Clients mainly on laptops having POP3 EMail (from the ISP) downloaded to the desktop, then uploaded to the Exchange Server. Exchange Server does not download POP3 mail but forwards outgoing mail to an SMTP server. These operations are working correctly.
Symptoms leading up to the problem:
- On the client side, many of them recive messages stating "Communicating with the Exchange Server..." with a progress bar. These messages at times will stay for some time and lead to a communications failure message.
- Also on the client, the Outlook application becomes slow and may crash or lead to the user rebooting or restartign thier computer.
On the server:
While the errors occur on the client the follwoing errors show up in the Exchange server's Application event log :
1:52pm - Event ID 2104 - MSExchangeDSAccess
Process MAD.EXE (PID=1440). All Domain Controller Servers in use are not responding:
dc.domain.ca
1:53pm - Event ID 2103 - MSExchangeDSAccess
Process MAD.EXE (PID=1440). All Global Catalog Servers in use are not responding:
dc.domain.ca
1:55pm - Event ID 9154 - MSExchangeSA
SACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.
1:56pm - Event ID 9095 - MSExchangeSA
The MAD Monitoring thread is initializing.
1:57pm - Event ID 9153 - MSExchangeSA
Microsoft Exchange System Attendant reported an error '0x8007203b' when setting DS notification.
After this, I would get two event messages:
2:01pm - Event ID 9095 - MSExchangeSA
MAD Monitoring thread is initialzing
2:01pm - Event ID 9096 - MSExchangeSA
MAD Monitoring thread is initialized
There are no messages in the other event logs near this time frame. Thare are no messages in the Domain Controller's event log in this time frame.
Notes:
I have tested commonuications between the servers and clients a number of times - there does not seem to be issues with the hardware networokign of the computers.
I have looked into permissions of various keys in the registries and used the ADSI Editor to try and find issues in the Active Directly but all permissions seem to be fine. I have used netdiag on both servers to try and determine a DNS problem but the DNS passes. Netdiag on the DC shows this message after the test:
"DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '10.0.0.3' and other DCs also have some of the names registered."
10.0.0.3 is the Exchange/DNS Server.
Any ideas?
Thanks,
Kevin
I've been having some issues with an install of Exchange Server 2000 (on Windows 2000 Server) I run. The primary probelm is a serious slowdown in Exchange and ultimatley server instability or client access problems. Here are more details...
Here are the basic details:
There are only two servers:
Server #1:
- A DC running Windows 2000 Server (AD Installed) (SP4)
- Fax Services
- RAS (Dial-Up) server
Server #2:
- Windows 2000 Server (SP)
- Running DNS (Dynamic Updates Enaabled)
- Exchange Server 2000 (6249.4 Service Pack 3)
Clients:
- Windows 2000 Pro (SP4)
- Office XP SP1
10 Clients mainly on laptops having POP3 EMail (from the ISP) downloaded to the desktop, then uploaded to the Exchange Server. Exchange Server does not download POP3 mail but forwards outgoing mail to an SMTP server. These operations are working correctly.
Symptoms leading up to the problem:
- On the client side, many of them recive messages stating "Communicating with the Exchange Server..." with a progress bar. These messages at times will stay for some time and lead to a communications failure message.
- Also on the client, the Outlook application becomes slow and may crash or lead to the user rebooting or restartign thier computer.
On the server:
While the errors occur on the client the follwoing errors show up in the Exchange server's Application event log :
1:52pm - Event ID 2104 - MSExchangeDSAccess
Process MAD.EXE (PID=1440). All Domain Controller Servers in use are not responding:
dc.domain.ca
1:53pm - Event ID 2103 - MSExchangeDSAccess
Process MAD.EXE (PID=1440). All Global Catalog Servers in use are not responding:
dc.domain.ca
1:55pm - Event ID 9154 - MSExchangeSA
SACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.
1:56pm - Event ID 9095 - MSExchangeSA
The MAD Monitoring thread is initializing.
1:57pm - Event ID 9153 - MSExchangeSA
Microsoft Exchange System Attendant reported an error '0x8007203b' when setting DS notification.
After this, I would get two event messages:
2:01pm - Event ID 9095 - MSExchangeSA
MAD Monitoring thread is initialzing
2:01pm - Event ID 9096 - MSExchangeSA
MAD Monitoring thread is initialized
There are no messages in the other event logs near this time frame. Thare are no messages in the Domain Controller's event log in this time frame.
Notes:
I have tested commonuications between the servers and clients a number of times - there does not seem to be issues with the hardware networokign of the computers.
I have looked into permissions of various keys in the registries and used the ADSI Editor to try and find issues in the Active Directly but all permissions seem to be fine. I have used netdiag on both servers to try and determine a DNS problem but the DNS passes. Netdiag on the DC shows this message after the test:
"DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '10.0.0.3' and other DCs also have some of the names registered."
10.0.0.3 is the Exchange/DNS Server.
Any ideas?
Thanks,
Kevin
