Exchange 2k, Win2kSrv Slowdowns and errors 1

[kcostain]

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

 

[compgirlfhredi]

9095:
This event is followed by event id: 9096. MAD refers to Exchange System Attendant initializing with Windows Management Instrumentation (WMI), the Microsoft implementation for Web Based Enterprise Management (WBEM). This was introduced with W2K SP2. Fore more information about WMI see link below.
MSDN WMI Info
9153:
This happened when a domain controller was demoted and it was the primary internal DNS for the Exchange server box. Changing the primary DNS address to another DC resolved the issue.
According to the only Q Article I can find (Q328931) this is to do with message tracking also. You can get a build up in the SMTP Queue which leads to this event being reported. It also may have something to do with Exchnage running in Mixed Mode. On the above article there is a link to Mixed vs. Native which tells you which is the best mode to run in.
I am currently experiencing this error after restoring my public folders due to a faulty replication. I am going to re-install service pack 3, and then move into Native Mode.
This whole thing is to do with ADC (Active Directory Connector) and SRS (Site Replicator service). We were running Exchange 5.5 with Windows 2000 which requires ADC to sync up Exchange mailboxes and Windows 2000 Active Directory. I upgraded the site to Exchange 2000 about 2 months ago. (Running fine). For some reason after a restart last week we started getting the MSExchangeSA and FBPublish errors. The problem is that Exchange 2000 does not require ADC to talk to Windows 2000 Active Directory. ADC only needs to be there if there is an Exchange 5.5 server somewhere in you Exchange network. In Exchange 2000 Admin, Site Replication Service, we deleted the connection. I then removed ADC and restarted the server - worked fine - no errors at all. (ADC would not remove until deleting the SRS connection in Exchange 2000 Admin).

Also if there are no other Exchange 5.5 servers in your network you can switch Exchange 2000 from mixed mode to native mode (similar to Windows 2000 same).

http://www.microsoft.com/contentredirect.asp

9096:
This event is preceded by event id: 9095. MAD refers to Exchange System Attendant initializing with Windows Management Instrumentation (WMI), the Microsoft implementation for Web Based Enterprise Management (WBEM). This was introduced with W2K SP2. Fore more information about WMI see link below.
2104:
Process: MAD.EXE - As per Q322837, this event can be ignored if they occur after you apply Service Pack 2 for Exchange 2000 Server.
2103:
This is caused either because there are no GC servers available or because there is no Recipient Update Service created in the domain where you installed Exchange 2000. See Q322801, Q275294.
9154:
Right click on My Network Places and select Properties
2. From the Menu Select Advanced and then select the Advanced Settings
3. In the connections box confirm that the Internal Network Card is at the top of the binding order. Select OK
4. Right click on the External NIC and select Properties
5. Highlight Internet Protocol (TCP/IP) and click on the Properties button. Then click on the the Advanced button
6. On the Advanced TCP/IP Settings select the DNS Tab.
7. Remove the ISP's Ip address from DNS and leave it blank.
8. Click OK to save the Network settings.
9. Verify that the Internal network card is configured to only point to the SBS server's internal IP address for DNS using steps 4 - 8.
10. Go to Start/Programs/Administrative Tools/DNS
11. Right click on the server's name in the DNS MMC and select Properties
12. Click on the Forwarders tab. Verify that Enable forwarders is selected and that the DNS server address for the ISP are listed
13. Click OK to exit the dialog
14. Reboot the server.

Error: "0x80004005". See Q310896 or Q318067.