Recovery after Dirty Crash 1

[joelrob]

Had to take extreme measures to recover from a dirty crash, none of the databse repairs would work. Exchange server 2003 running on win 2003. I deleted the information store that wouldn't mount (moved the db files to a backup location). Then re-created the information store and restored the mailboxes from a backup. Now my internal users are having issues sending mail to each other, it's hit and miss. Sometimes it goes through, sometimes it hangs in the queue until it times out with an NDR. It seems to be when they select the users from the Global Contact list, that it does not go through. When the full e-mail name is typed out, UserFirstName.UserLastName@domain.com, it goes through fine, but takes a long time.

Any help would be greatly appreciated.

 

[Fatboy0341]

I'm taking a wild stab - but are your users running Outlook 2003 in Cached Mode?



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[joelrob]

Yes, they are, but it's been almost a week now, shouldn't they synch up with the server? If not, how can I force them to?

 

[Fatboy0341]

That was going to be my next question - how long has it been since the crash and restore.

The default for updating the cached GAL is 24 hours - you probably didn't change that stting otherwise you would have remembered it.


What is the exact verbage of the NDR when one of the emails doesn't go through? USer does not exist? Connection refused?

I will be on the road in about 15 minutes, so I probably won't be able to reply to your next message - I'll chack again tomorrow AM. I didn't want you to think I blew you off or anything.

JB




"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[joelrob]

Actually I just recently inherited the joy of administering this Exchange server, have no idea what's been set up or re-configured from the defaults.

As to the NDR, I'll post a copy of it in the AM, will have to get one of the users to forward to me.

Thx for the responses.

 

[Fatboy0341]

Sounds good...post one when you have time and we'll see if we can get this sorted out.



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[joelrob]

Here are a couple of the NDR messages bouncing back to users:

The following recipient(s) could not be reached:

/O=COMPANY NAME/OU=DOMAIN/CN=RECIPIENTS/CN=UserName on 8/21/2006 8:37 PM
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.
<ExchServer.DOMAIN.com #4.4.6>

Your message did not reach some or all of the intended recipients.

Subject: Updated: Candidates and Applications
Sent: 08/21/2006 3:22 PM

AND...

The following recipient(s) could not be reached:

USER NAME on 08/21/2006 3:22 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
MSEXCH:MSExchangeIS:/DC=com/DC=domain:EXCHSERVER

 

[Fatboy0341]

The 4.4.6 error generally is telling you there is a loop of some sort in your configuration.

Since this doesn't happen to everyone it could be a rule or alternate recipient issue.

Check your DNS records maybe? Are you running internal MX?

Now - the second error message - do the same mailboxes get both errors sporadically, or do some mailboxes only get one or the other?







"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[joelrob]

I think this is all coming down to the GAL not being updated on the user's desktops. After my restore method, all the desktops were coming up with an error message saying that Exchange was in repair mode, did the user want to connect, work offline or cancel. So to fix this, I exmerge'd each users mailbox out, deleted their mailbox by removing Exchange features from their account, purging the mailbox from Exchange, then re-adding their Exchange features. After that, they no longer get the prompt on startup, but the other issues started occuring. To verify this, on my personal workstation, I removed Exchange Cached Mode, and the address lists came up fine, and e-mail went through ok.

I wasn't able to fix the startup prompt on all users at once, have over 150 workstations here, having to do several a day over the course of the last week, so I think will continue to have these problems until 24 - 48 hours after the last user's completed.

The second error only happens when a user that's been "repaired" tries to send to a user that hasn't. The first error happens sporadically through the environment, some people get them, others don't, different senders/recipients, no common thread that I can find. However, all e-mail was being cc'd to an archive mailbox that was in another information store and still damaged after the crash. I've redirected it to a different mailbox in the restore information store and I think those errors are dying down now.

Thanks for all your help in this, it's really appreciated.

 

[Fatboy0341]

I hear you...having to touch each and every workstation will be a drag but it sounds like you are on the right track.

Good job getting it sorted out and drop a final post on this thread when the last one's done.

I'm actually glad I picked up on this thread...I learned something from it...hopefully I won;t need to apply it but if I do - I'll be ready.

JB



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[Fatboy0341]

And happy to help at all if I managed to. That's what this place is for...



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."