Two quick thoughts:
Does this happen with all users at the same time? If not, try shutting down
Outlook and deleting the user's OST file. Restart Outlook and let it create
a new OST, and see if that solves the problem. Obviously if all the users
are seeing the symptom at the same time, it wouldn't be this.
Also, in ESM, in the properties of the Default SMTP Virtual Server ->
General -> Advanced -> Edit, is the Sender ID Filter enabled? I had this
symptom after enabling Sender ID when Exchange services would restart - for
example, IMF updates, services restart, incoming mail stops flowing. At
that point, I'd get the service hang at "stopping" as you describe and have
to reboot the server. It might explain the seemingly random nature of this
if you have Exchange restarting from something like WSUS. This KB is what
fixed it for me, even though the symptom didn't really match the KB.
Messages from some organizations may remain in the queue folder when you
enable the Sender ID filter feature in Exchange 2003 http://support.microsoft.com/default...en-us%3B927478
"Billy Gareth" <BillyGareth@newsgroup> wrote in message
> Scenario: Usually every 4-5 days, sometimes more, sometimes less users
> say that Outlook is saying that it is connected but no emails are coming
> through. If they restart Outlook then it doesn't connect properly to
> If I try and restart Exchange server, it takes ages then fails with a 1053
> error. The state then gets stuck in the "stopping" state and the only way
> resolve in a complete server restart.
> May not happen for weeks then happens weekly again for a few weeks.
> Failure generally seems to happen overnight at some time as compliants
> already come through first thing in the morning.
> Has done this since install 2 years ago but not consistent. So think that
> is all good for months then starts again.
> These errors show in event viewer
> LDAP Bind was unsuccessful on directory server.servername.local for
> distinguished name ''. Directory returned error:[0x51] Server Down. 8026
> The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
> component could not be found in the configuration information. The
> could not be initialized. Make sure that the operating system was
> properly. 8250
> Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> Have run toubleshooting assistant many times and fixed issues that were
> found or found no issues.
> Am out of ideas...
> SBS 2003 standard
> Exchange SP3
> 17 mailboxes
> Prviate DB = 13.4GB
> Public DB = 28MB
> DB limit patch applied