Exchange Stops Responding - Need help quick!

From: Stephen Sanders (fake_at_fake.com)
Date: 02/18/04 

Date: Wed, 18 Feb 2004 14:25:04 -0600

I am having some issues with Exchange 2000 SP3 and was wondering if anyone
could help me find where to look for what may be wrong.

When I start the server, everything runs just fine for about half an hour or
so. After a little bit, Exchange stops responding completely. There are no
error messages in any of the logfiles. All the services are running just
fine. There is no excessive processor, memory or disk usage. There is
network traffic going to and from the machine just fine and it responds well
to pings and such. The only thing on the computer that stops working is
Exchange.

I have turned on logging for MSExchangeIS System in the recovery, general
and connections categories, and nothing unusual shows up in the logs.

When I open Outlook 2003 is just sits at the "Updating Inbox" screen. If I
look at the send and receive meter, it stops at 50% and never moves. If I
try to log in via OWA, it stops at the "Loading" screen and never makes
progress.

The clients are connecting to the exchange server and authenticating just
fine. When I open Outlook on a client, I see a message in the event log
showing a success audit linking the user's domain ID to their mailbox
(Application Log, EventID 1007, Success Audit).

Using PERFMON, I watched the RPC Packets/Sec vs. RPC Requests and that does
not indicate any backlog in processing RPC connections.

I ran an ISINTEG check on both the public and the private database, and it
did not indicate any consistancy errors.

If I reboot the server, it will work just fine for another 30-60 minutes
before stopping.

I'm stumped as to what to try next. Anyone have any suggestions on where to
look? Are there any other logging categories I could turn on that may help
with troubleshooting?

Thanks in Advance,

Stephen Sanders

Relevant Pages

  • Re: Exchange Stops Responding - Need help quick!
    ... forth of newsgroups is a pretty slow "down server" support mechanism. ... After a little bit, Exchange stops responding completely. ... > and connections categories, and nothing unusual shows up in the logs. ... I watched the RPC Packets/Sec vs. RPC Requests and that ...
    (microsoft.public.exchange2000.general)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... SBS 2008 does include the option during installation, to install fresh or to perform a migration installation, which allows you to introduce it into an existing SBS 2003 organizations. ... Windows Small Business Server 2008 Unleashed ... Since exchange defaults to accepting ... IF, after a week, you are still seeing some connections, try *DISABLING* ...
    (microsoft.public.windows.server.sbs)
  • Re: Errors 5790 and 5719; Domain Not Found
    ... I have configured rpc over http following those docs:) ... As my DC/GC is not on the same machine as Exchange Server, ... >> Exchange Server to configure RPC over HTTP connections for Outlook... ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... Since exchange defaults to accepting ... IF, after a week, you are still seeing some connections, try *DISABLING* ... SenderID filtering on the Virtual SMTP server. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)