Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 824
  • Last Modified:

Ex2003 SP2 Local Delivery Queue Stuck

Hello.
I recently had a hard drive failiure on a server running Exchange. The raid config got corrupt so all the data was lost. Luckily we had a 35GB NTBackup of Exchange. I restored this to a new /disasterrecovery Exchange server with the same name. It did the 15GB EDB but when it got part way into the STM it failed. After creating a blank STM we got the store mounted and email was flowing for a bit. A few days later it stopped working. Noticed that the database size was never increased from 18GB to 75GB (could be why the STM failed to restore....).

After increasing the DB size and restarting the information store email is still stuck in the local delivery queue. I created 2 new test users and can send mail back and forth with them. I can send internal and external email inbound/outbound with them. Works fine. Old users are not send/recieving any email. It gets stuck in the Local Delivery Queue. I have tried to do force connection and Unfreeze but nothing works. I have about 150 emails, 8MB.

What could get these old emails to work? Any new email old users send also get stuck in the queue. The first few emails sent 2 days ago are being deleted with NDRs, so it appears a corrupt email is not the cause.

Thanks!
0
undy30
Asked:
undy30
  • 5
  • 4
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
When the restore was unsucessful you ran the repair with the create STM switch, did you run the Offline defrag and the Isinteg to remove the logical corruption before mounting it in production.
Can you increase diagnostic on Transport and see if you get any 327 event ids.
In case you get just Offline defrag and isinteg the database.
0
 
undy30Author Commented:
I did do an offline defrag and isinteg before mounting the database. I increased loggin on the Transport, I'll see what comes up.

When I reboot the server the queue does go back to 0 and mail appears to deliver fine. But then instantly the queue freezes again.
0
 
undy30Author Commented:
Yes, we have a lot of 327 events.

The following call : EcLocallyDeliverMsg to the store failed. Error code : -2147221240 (Message-ID  <e420d6e20905110853t45835293v4cf79a370e497c2@mail.gmail.com>). MDB : 373c33b4-1d96-4c09-8279-39f17bf4454f. FID : . MID : . File : D:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_93c1c8f401c9d2500000002e.EML.

The Queue folder has the emails in it. I can open them just fine in outlook express on the server.


We're getting the exact error in KB924206. We applied the patch and no luck.

Thanks for your help!
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
undy30Author Commented:
I disconnected a users mailbox in AD and reconnected it in ESM with no luck. Outbound email appears to work fine. It's just any mail being sent to the store (i guess the 327 errors show that).

0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Is the Exchange a standard to enterprise?
If its Enterprise create a new store and move mailbox or else if standard and Exchange 2003 create a RSG and merge mailboxes from RSG to prduction, as there is still corruption in your store.
Also would like to know how much time did Offline defrag take and when you ran Isinteg where there any errors warnings or fixes?
0
 
undy30Author Commented:
I have Standard edition. I'm currently EXmerging all my mailboxes to PST, to create a new mail store. The Offline defrag was quicker than I thought, about 8 hours for both the defrag and the isinteg. I did have to run isinteg twice as I got errors the first time, second time was clean.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
OHk once the PST is taken out dismount the stores and move the current DB and logs to a different location and then mount with a blank.
Do not delete the DB or logs until everything is fine for some weeks.
0
 
undy30Author Commented:
Ok the issue appears to be fixed. Created the new store and imported the PSTs and that finally got it working.

One small issue. Someone had a massive PST file and I did a date range of 1 year back but that was still over 2GB. I thought cancelling the Exmerge operation would make the PST at least somewhat readable but it isn't. I've done a ScanPST on it and that failed. Outlook can't open it, as with EXmerge. Do you know of anything besides a paid 3rd party program to get that readable? If not I"ll just do a RSG with a backup.

Thanks so much!
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
You can use the Exmerge and split the time to 3-6 months rather then 1year what your were working with.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now