Re: One user having messages stuck in Local Delivery
- From: Keven <Keven@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 16 Jan 2008 13:05:01 -0800
Update on this is that it is indeed getting worse. I was able to fix one of
the users by removing their mailbox, deleting it, and then recreating a
mailbox, but within 12 hours yet another user is now having the same
problems. I can't keep doing this for all users as many of them (including
now two of them with the problem) are remote users who would take FOREVER to
resync and aren't quick enough on their computers to deal with the task of
resetting up outlook over the phone with me.
I just took the mailbox store offline, backed it up directly, and then ran
through the following on it:
Eseutil /P
Eseutil /D
Isinteg -fix -test alltests
Lots of problems found and corrected during that process it seems, but when
I took it back online I am still having two downed users.
Application Log has been dead quiet save when I had the mailbox store
detached in order to run the above attempted repairs.. at the end of my rope
with this and am already starting a new install of SBS on a new machine in
case I can't get this working.. but that will be a nightmare as well for both
me and the external users to get everything from box 1 to box 2.. I'd love to
keep this box running until middle of Feb when the staff will all be in the
same city and I can transfer to a new install of sbs inhouse with them all.
PSS.. how does one contact?
"Dave Nickason [SBS MVP]" wrote:
Has this sorted itself out? When you view the local delivery queue, is.
there any useful information at the bottom of the screen under "additional
queue information?"
If this situation is worsening, I do an online and offline backup of your
databases. You can do an offline by simply shutting down the Exchange
services and copying the mdbdata folder elsewhere for safe keeping. After
your restart the services, do an online backup using your normal procedure
such as SBS Backup.
Is there anything relevant in the application log? Exchange usually logs
like crazy if something's wrong.
If you don't have useful information in the queue information or the logs,
I'd consider calling PSS for this rather than troubleshooting without a
clear path. That's especially true if it's worsening.
"Keven" <Keven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B1A4AF74-FAB9-479A-B0B2-FEA4391EDC13@xxxxxxxxxxxxxxxx
I had an entire array fail and had to restore SBS2003 Premium server from
backup. Restore went as well as could be hoped for and company back up
and
running. By the end of the first day however it's been noted that one
specific member of the organization hasn't received any emails even ones
sent
from within the network. Additionally all email sent to multiple people
which included him didn't get delivered to anyone. When I go into the
Exchange System Manager and look at the Queues there are multiple messages
stuck in the queue, all of which have his email address in them.
I have attempted to restart the exchange system and it never corrected and
then restarted the server, and it never corrected. What's the next step
to
correct this?
- Follow-Ups:
- Re: One user having messages stuck in Local Delivery
- From: Dave Nickason [SBS MVP]
- Re: One user having messages stuck in Local Delivery
- References:
- Re: One user having messages stuck in Local Delivery
- From: Dave Nickason [SBS MVP]
- Re: One user having messages stuck in Local Delivery
- Prev by Date: Re: Basic Server System Questions
- Next by Date: Re: External email recipient
- Previous by thread: Re: One user having messages stuck in Local Delivery
- Next by thread: Re: One user having messages stuck in Local Delivery
- Index(es):
Relevant Pages
|
