General discussion


Microsoft Exchange Server 2000 Problem

By R. A. Caluste ·
Just recently, our users in the intranet have been complaining about the behavior of the Microsoft Outlook when, from time to time, it displays "Requesting data from Microsoft Exchange Server". It will timeout and eventually freeze.

At first, I thought it was purely a DNS issue when several clients cannot resolve the server hostname. That has been fixed already but the problem remains.

I checked out several knowledge bases and came across issues with disabled accounts (that's been fixed by giving rights to self), black hole router (complaints are coming from within the intranet, same network segment as the exchange server).

Access to OWA at this stage (since nobody can open MS Outlook) is also a failure.

Also at this point Dismounting the private mailbox store (hoping to run isinteg.exe) will stop at 66% and freeze.

When trying to restart the Microsoft Exchange Information Store service, status will remain to "stopping" and will never reach the "stopped" status.

Running the Performance Monitor before the problem yields the following observations (during the time the mail service fails):

Microsoft Exchange RPC request = 2 (across time!)
Microsoft Exchange RPC operations/sec = 0

Network bytes received/sent, %Processor Time, Paging is normal.

Looking at the Event Log, I usually see 7011 events.. DNS and BINLSVC both times out waiting for a transaction response. Netlogon returns a warning: Dynamic registration of DNS records fail because no DNS servers are available.

Running a Netdiag /v /test:dns will yield a PASSED report for the dns server. Further verification at the DNS snap-in will yield an online and active DNS server.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by paul.davis In reply to Microsoft Exchange Server ...

Congradulations. Given that you've tried all the above, you've probably got a hardware problem.

Check the temp of the CPU chips first. Try a check of the voltages on the MB as well, check the power supplies for heat and voltage.

Log into the switch the machine is connected to - make sure the network connection matches what the machine is seeing. A synch mismatch can corrupt a database faster than you can say squat. Be sure one isn't set to 100 half, and the other to 100 full. Check for errors, both on the server NIC and for errors on the switch. Sometimes a card can simply go bad.

Finally, you need to monitor the network for any kind of network interference you might have. If you have a huge graphics dept, they may simply be taking up all the network bandwidth at certain times of the day. Outlook may simply be losing its connection by timing out, or the constant talk between server and client may be interrupted by this.

Intermittent troubles of this sort are very hard to diagnose. But recurrent database corruption on Exchange, with no sign of software failure is a clear pointer to a hardware or network problem.

Other possibilities include overheating anywhere on the MB support chips, bad UPS allowing voltage spikes into the system, a hard drive that isn't spun up all the time, even too much dust on the MB contacts or a loose board inside the system.

Make sure the fans are all running.

Collapse -

by R. A. Caluste In reply to

Thank you for your suggestion.

Collapse -

by techtonik In reply to Microsoft Exchange Server ...

As per Q311517, this event can show up when the Inetinfo.exe process may stop responding due to a conflict with Exchange 2000. A stack overflow in the Mailmsg.dll file might be the reason that the Inetinfo.exe process stops responding and that you may receive event ID messages that point to problems with disks or controllers.

Q179265 points to a potential conflict between Exchange and ARCserve, the solution being to stop manually ARCServe before shutting down Exchange.

Q238665 indicates that this may occur when changes made to the application, directory, virtual directory, or site are interrupted while they are being written to the metabase. This can, in certain condition, corrupt the metabase.

Maybe these articles can help?

Collapse -

by R. A. Caluste In reply to

Thank you for your suggestion.

Collapse -

by jack republic In reply to Microsoft Exchange Server ...

Do you have A Symantec antivirus for exchange installed on your system?
If you do stop the service and see if it is the source of the problem.

Collapse -

by R. A. Caluste In reply to

Poster rated this answer.

Collapse -

by robbinsr In reply to Microsoft Exchange Server ...

Is this topic still open? I have a few questions and suggestions.

Collapse -

by R. A. Caluste In reply to

Poster rated this answer.

Collapse -

by R. A. Caluste In reply to Microsoft Exchange Server ...

This question was closed by the author

Related Discussions

Related Forums