Re: Messages stuck in local delivery queue

Thanks

I have recreated the mailboxes in question and all is fine.

Dave


"chace zhang" <v-chacez@xxxxxxxxxxxxx> wrote in message
news:%23IKF8P6uGHA.492@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Thank you for posting back.

I do understand you encountered following warning event in application
log:

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 327
Date: 01/07/2005
Time: 16:28:16
User: N/A
Computer: SNOWEXCH
Description:
The following call: EcLocallyDeliverMsg to the store failed. Error code :
-1605 (Message-ID
<5592352B8C2CE44E8A489711DAA22C01131760@xxxxxxxxxxxxxxxxxx
own.local>). MDB : a01e0cef-e192-4c89-8e18-d4fe432210bf.
FID : 1-3C. MID : 1-CAAB6. File : .

For more information, click
http://www.microsoft.com/contentredirect.asp.

As I mentioned, error 1605 indicates a store level issue. It asserts that
the problem is a corrupt mailbox that can be resolved by ISINTEG or by
moving or recreating the mailbox. Also the -1605 indicates logical
corruption occurring in the store.

Hope this helps, have a great day!

Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
| From: "DW" <dw@xxxxxx>
| References: <ew3706nuGHA.2224@xxxxxxxxxxxxxxxxxxxx>
<M5#xNhpuGHA.4396@xxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Messages stuck in local delivery queue
| Date: Tue, 8 Aug 2006 16:55:21 +0100
| Lines: 190
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
| X-RFC2646: Format=Flowed; Original
| Message-ID: <ehaJQMwuGHA.560@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: 82-69-111-163.dsl.in-addr.zen.co.uk 82.69.111.163
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:287960
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks for that, however,
|
| The error is actually:
| EcLocallyDeliverMsg to the store failed. Error code : -1605
|
| What could cause this error?
|
| Dave
|
|
|
|
| "chace zhang" <v-chacez@xxxxxxxxxxxxx> wrote in message
| news:M5%23xNhpuGHA.4396@xxxxxxxxxxxxxxxxxxxxxxxx
| > Hi,
| >
| > Thank you for your post!
| >
| > I understand that some messages are queued in Local Delivery queue and
| > some
| > recipients do not receive messages. Please feel free to let me know if
I
| > am
| > off base.
| >
| > Based on my research, -1605 stands for "JET_errKeyDuplicate" which is
a
| > problem on the database level. At this point, I suggest you check
Database
| > first:
| >
| > 1. Please back up the Exchange 2003 Mailbox database first. If you are
| > using NTBackup utility, please try the online backup method in the
| > following KB article:
| > XADM: How to Back Up and Restore an Exchange Server Computer by Using
the
| > Windows Backup Program
| > http://support.microsoft.com/?id=258243
| >
| > You can also keep an offline copy of the database files (.edb/.stm):
| > Offline Backup and Restoration Procedures for Exchange
| > http://support.microsoft.com/?id=296788
| >
| > NOTE: If you are using any third-party backup program instead of
NTBackup
| > to perform full online backup for Exchange databases, make sure that
the
| > backup program you are using is Exchange-aware and is compatible with
your
| > current Exchange server. Ensure that you know the process of how to
| > correctly perform the full online backup. If you are not familiar with
the
| > process of using the third-party backup program to back up Exchange
| > databases, please consult with the third-party backup program provider
| > before you proceed.
| >
| > 2. Dismount the Mailbox Store "Mailbox Store (ServerName)" by
| > right-clicking it in ESM and choose Dismount Store.
| >
| > 3. Open a command prompt window and change the currently directory to
| > "<system drive>:\Program Files\Exchsrvr\Bin".
| >
| > 4. Run the following command:
| > isinteg -s <Exchange Server Name> -fix -test alltests
| >
| > 5. Press the number of the "Mailbox Store (ServerName)" and press
ENTER.
| >
| > 6. After this, mount the Mailbox Store and test if the problem ceases.
| >
| > 7. If there are more than 20 fixes, you can re-run the command in step
4
| > until you found the fixes number is near to 0.
| >
| > If the issue persists, let's use the following command to perform
offline
| > defragmentation on the database:
| > <system drive>:\Program Files\Exchsrvr\Bin>eseutil /d
| > "<path>\<store_database_file_name>.edb"
| >
| > For more information about eseutil, please refer to the following
| > Knowledge
| > Base Article:
| > XADM: Exchange 2000 Server Eseutil Command Line Switches
| > http://support.microsoft.com/?id=317014
| >
| > If the problem still exists, as you are running Standard version of
| > Exchange, you cannot create a new store. We may try the following
steps
to
| > create a new blank store:
| >
| > 1. Use Exmerge to export all the mailboxes to PST files. Please refer
to
| > the following Knowledge Base Article for more information about
Exmerge:
| >
| > XADM: Microsoft Exchange Mailbox Merge Program (Exmerge.exe)
information
| > http://support.microsoft.com/kb/174197
| > How To Recover or Restore a Single Mailbox in Exchange 2000 Server
| > http://support.microsoft.com/?id=813337
| >
| > 2. Rename the mailbox database file and mount a new store.
| > 3. Restore the mailbox from PST files and test the issue again.
| >
| > Hope this helps, please feel free to let me know if you have any other
| > concerns on this issue.
| >
| > Have a nice day!
| >
| > Best Regards,
| >
| >
| > Chace Zhang (MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have
issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you
check
| > the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although
we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
| > doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| >
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| >
| > --------------------
| > | From: "DW" <dw@xxxxxx>
| > | Subject: Messages stuck in local delivery queue
| > | Date: Tue, 8 Aug 2006 01:07:56 +0100
| > | Lines: 32
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
| > | X-RFC2646: Format=Flowed; Original
| > | Message-ID: <ew3706nuGHA.2224@xxxxxxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: 82-69-111-163.dsl.in-addr.zen.co.uk 82.69.111.163
| > | Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.sbs:287763
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hi all,
| > |
| > | I had to restore an SBS 2003 Premium machine from NT Backup after a
hard
| > | drive failed. This seemed to go fine for a few days i.e. everyone
| > receiving
| > | mail etc, but now some of the users report not getting emails.
| > | There are 87 (so far) messages in the Local Delivery queue. As I
said,
| > this
| > | is only affecting a few users.
| > | I put logging to max and got this error:
| > |
| > | Event Type: Warning
| > | Event Source: MSExchangeTransport
| > | Event Category: Exchange Store Driver
| > | Event ID: 327
| > | Date: 07/08/2006
| > | Time: 13:33:00
| > | User: N/A
| > | Computer: SERVER
| > | Description:
| > | The following call : EcLocallyDeliverMsg to the store failed. Error
code
| > | : -1605
| > |
| > | I have googled and EventID etc for this error but all the obvious
| > | possibilities seam to be not relevant. i.e. Server side rules
through
| > | outlook (there aren't any!).
| > | Is it a case of recreating those user mailboxes?
| > |
| > | Any help or suggestions greatfully received,
| > |
| > | Thanks
| > | Dave
| > |
| > |
| > |
| >
|
|
|



.

Relevant Pages

  • Re: IIS logs for Exchange/OMA Access
    ... If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. ... So when you import the pst file, this will > not copy the corrupted Exchange attributes. ... the > problematic device to access this new mailbox. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange Mailbox problem
    ... Please try my suggestion in the first reply to see if the mailbox issue ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... <<<permission or Exchange attributes. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange Mailbox problem
    ... Screen shot of the error message when you run the Change User Permission ... 41235318-Exchange Mailbox problem. ... Microsoft CSS Online Newsgroup Support ... <permission or Exchange attributes. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange Transport 3018
    ... Since the issue occurs when Companyweb sends out alert e-mail, ... Microsoft CSS Online Newsgroup Support ... <Thread-Topic: Exchange Transport 3018 ... Export all mails in Mailbox as .PST file. ...
    (microsoft.public.windows.server.sbs)
  • RE: Information Store Recovery
    ... If you used recovery storage groups in Exchange 2003, ... restore the information store again and check if the issue persists: ... Expand Servers, and then expand YourServerName and the storage group. ... Right-click Mailbox Store, and then click Properties. ...
    (microsoft.public.windows.server.sbs)