One specific user cant send mail to another specific user in same Exchange 2007 enviroment.

Hi,

  Background:
  Exchange 2007 with SP3 & roll-up 3
  Server 2008 SBS

  I have a user on Exchange 2007 that just cant receive a mail from another internal user (Both on the same Exchange)

  When user1 sends user2 a mail in the same SMTP name space, and on the same Exchange server, the mail returns to user1 with the following error:

  "There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator."

  user2@mydomain.com
  #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionJetErrorReadVerifyFailure:16.18969:7D080000, 17.27161:000000006202000000000000EA00000000000000, 255.23226:00000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.27962:0A000000, 255.27962:94000000, 255.17082:06FCFFFF, 0.27745:15000000, 4.21921:06FCFFFF, 255.27962:FA000000, 255.1494:2F400000, 255.1238:00000000, 0.36537:0F010480, 4.5587:0F010480, 0.65193:0F010480, 0.31004:0F010480, 0.39497:0F010480, 4.55881:0F010480, 0.27676:0F010480, 0.23580:BDF9FFFF, 0.16668:0F010480, 0.27420:0F010480, 0.39497:0F010480, 4.55881:0F010480, 0.27676:0F010480, 0.23580:0F010480, 0.36537:0F010480, 4.5587:0F010480, 0.65193:0F010480, 6.21970:0F01048003002F0E0F010480, 6.21970:0F0104800300230E0F010480, 4.13236:06FCFFFF, 4.4097:06FCFFFF, 4.5093:06FCFFFF, 4.5318:06FCFFFF, 4.10104:06FCFFFF, 0.21097:0F010480, 4.8756:BFF9FFFF, 4.4353:BFF9FFFF, 4.5257:BFF9FFFF, 4.4606:06FCFFFF, 255.1750:00000000, 0.26849:00000000, 255.21817:06FCFFFF". ##

  Received: from myserver.mydomain.local ([fe80::6060:f540:d469:85ec]) by
   myserver.mydomain.local ([MAC ADDRESS]) with mapi; Wed, 4 Mar
   2015 13:21:02 +0900
  Content-Type: application/ms-tnef; name="winmail.dat"
  Content-Transfer-Encoding: binary
  From: user1 <user1@mydomain.com>
  To: user2 <user2@mydomain.com>
  Date: Wed, 4 Mar 2015 16:21:01 +0900
  Subject: test mail
  Thread-Topic: test mail
  Thread-Index: AQHQVoZtknIxngxmzEmDYrT2fDaQgA==
  Message-ID: <77060361B689EA4BAAE82363613C41BD0233FFFBB107@myserver.mydomain.local>
  Accept-Language: en-US, en-USA
  Content-Language: en-USA
  X-MS-Has-Attach:
  X-MS-TNEF-Correlator: <77060361B689EA4BAAE82363613C41BD0233FFFBB107@MYSERVER.mydmain.local>
  MIME-Version: 1.0

Everyone else can send mail to user2 and user2 receives them well, can user2's Exchange mailbox really still be corrupt as some of the web pages suggest?

  Please, if anyone can assist it would greatly be appreciated.
LVL 3
wimpie_asgAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Any other user can send to user2 other than user1? If this is correct this is most likely a auto complete caching issue. Have user1 open a new email, start typing the name of user2, when you see user2 populate "delete it".

Also have user1 find user2 via the GAL (global address list) then try sending the email again.

Will.
0
Guy LidbetterCommented:
I've seen this issue a couple of times, it is generally rectified by moving the mailbox to another database.
In the process the mailbox is basically rebuilt and any odd issues disappear...

Usually though, i have to admit, it affects everyone sending to the mailbox not one other person..., but database issues can be quirky...

Do you have a number of databases this can be done on? and if so... are the mailboxes on the same store?
0
wimpie_asgAuthor Commented:
Hi,

Thx for the reply.

At first I also thought it was an autocomplete caching issue, I use to resolve these issues quite quick by starting to type the mail, wait for autocomplete, then use the arrow keys up and down to highlight the mail address in the list, and simply pressing delete, but this did not work and I was quite livered.

Yes, anyone else can send mails to user2 in the same Exchange organization / SMTP name space, (Even from outside the company) I have tested this thoroughly. Only user1 cant send to user2, I get the same error message over and over again, and the mails returns within about 5 seconds or so. I logged in to user1's OWA, and sent a mail to user2, the same thing, I even went in to user1's contacts and deleted the contact, same thing.
0
Acronis Data Cloud 7.8 Enhances Cyber Protection

A closer look at five essential enhancements that benefit end-users and help MSPs take their cloud data protection business further.

Will SzymkowskiSenior Solution ArchitectCommented:
If you have tested this from OWA and it is still producing this error message then I would do the following next.
- Try moving the user2 mailbox to another database
- Check on user2 mailbox that there is no blocking enabled for user1 (see screenshot)
reject.JPG- Create a new mailbox and see if NewUser can send to User2.

I would start by check the restrictions on the mailbox first.

Will.
0
wimpie_asgAuthor Commented:
Hi Guy,

Thank you for the reply,

I don't have any other Exchange databases, no, I have seen a similar web page suggesting to create a second Exchange database, move this user in to it, and run ESEutil against it, and then to move it back to the old Exchange database. I must tell you, this is probably the worst person this could have happened to in the company, this person is the owner of the company, and a major @$$. I really do not like to use ESEutil as I don't trust it too much, but I am sure there are many people that would argue...

Did you managed to fix your problem just by moving it to another Exchange database, and then back again?
0
Satyendra SharmaMicrosoft UC Technical ArchitectCommented:
If you have other mailbox databases i would recommend moving affected users mailbox to another database which should remove corruption if there is any and there is no harm in doing that.
0
wimpie_asgAuthor Commented:
Hi Will,

I quickly logged on the Exchange server to have a look at message delivery restrictions, "All Senders" and "No Senders" is selected, this all is still on the stock standard settings.

I never had to do this before, can I just create another database in Exchange to move this user to it, and then back again to the old dataset? Is there any catches in doing this, anything I need to be aware of / is there a better way in doing this, meaning, without creating a second Exchange database?
0
Guy LidbetterCommented:
Hi Wimpie,

Yes, just moving the mailbox was sufficient. No need to run ESEUtil unless you suspect the actual database itself is corrupt, but then you'd have a whole host of other problems.

I would create another database store temporarily, move the mailbox, then move it back and delete the temporary database. That should do it... it won't cause any issues on your estate by doing this and is pretty straight forward.

The law in the universe is... if something bad is going to happen in exchange.... it will happen to a VIP...
0
Will SzymkowskiSenior Solution ArchitectCommented:
Exchange to move this user to it, and then back again to the old dataset?
Yes you can do this.

The only thing you need to be aware of is when creating a new database it is recommenced that you have separate disks for Logs and the databases. This is not a requirement but if you are planning on keeping this database I would set it up properly.

Also you need to make sure that if you keep this database that you have backup software that will be backing this database up. If your logs fill up the disk your database will dismount.

Will.
0
wimpie_asgAuthor Commented:
Hi Will,

Thank you for your reply.

I decided on creating a second Exchange database to move the corrupted mailbox across. But if you know me, I had to test it first with a less important user, so...I created a second Exchange database, moved this one less important soul across to the new database, waited for about 5 minutes, and it failed, why? Well, it said that Exchange had reached the maximum amount of errors allowed in the move, great, so I did not specify the amount of corrupted items allowed in the move, so I did the less important soul again, this time specifying 100 items that can be left on corruption, and it moved successfully, during the move I sent mail to it to make sure mail wont bounce back while the mailbox is transferring, and that when the transferring if the mailbox is done, that the actual test message would appear in the mailbox, all was OK. The last thing I wanted to do was to transfer a mailbox from one Exchange database to another and the messages either bounces back to the sender, or gets lost in cyberspace, but Microsoft had thought of this before, obviously.

So, by doing this test on this less fortunate soul first, I realized there are other mailboxes that are corrupted too. I decided I would move all the mailboxes to the new Exchange database, so far so good. I am about 3/4 of the way of a 280gb store. When all the mailboxes are moved, I will leave the old database for 1 month or so before decommissioning it just to make sure all is working well. Also, I have created the new Exchange database on a different hard-drive away, just in case the original hard-drive array the Exchange database was on could have been faulty in a way the diagnostic software did not pick up. So, new Exchange database, new hard-drive away, what could go wrong? :-)
0
wimpie_asgAuthor Commented:
Hi,

I have successfully created a new Exchange database and moved all users to the new Exchange database, all seems to be working well. I have dismounted the old Exchange database, and mail is working, sent/received properly.

I see in the event viewer that Exchange is now looking for the old Exchange database, there are event id's in the event viewer for example:

Event ID:  4001
A transient failure has occurred. The problem may resolve itself in awhile

There are event ID's that appear only when I dismount the old database, when I mount it again, the event ID's disappear.

What is the correct way to "Tell" Exchange that this database is no longer in production. All Mailboxes had been moved to the new Exchange database, I can see this in "RC> Database location" in the EMC. The location of all the mailboxes had changed to the new Exchange database location.

After starting a new Exchange database, is there anything else I need to move/change I have seen the send/receive limits I had to me amended again as the new Exchange database had the default limits again, are there more things like this?

Otherwise - The original issue is gone, moving the mailboxes to a new Exchange database had indeed resolve the issue.
0
Guy LidbetterCommented:
I doubt there is anything else you need to update, but I would suggest running
get-mailboxdatabase -status | select *

Open in new window

and comparing the values just to be safe.

Use the
Remove-MailboxDataBase

Open in new window

command to properly clean out the database. As far as exchange is aware, if the database is still there, even in a dismounted state is will still health check it, that's probably where the errors are coming from.

Are you running any copies (CCR, SCR, LCR???)

Otherwise you should be all good....

Regards

Guy
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Satyendra SharmaMicrosoft UC Technical ArchitectCommented:
Hello,

I would recommend to create another question if you have any other issues at this point since the original issue was resolved please mark this solved :)
0
wimpie_asgAuthor Commented:
Moving mailboxes to a new Exchange database resolved the issue I initially had in the beginning of this threat. Thank you for all the input, all is working well.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.