Solved

mail bounce problem

Posted on 2008-10-15
5
842 Views
Last Modified: 2013-11-30
we have one exchange 2003 back-end server (standard edition with SP2) with one Exchange 2003 front-end server. We are doing a transition to Exchange 2007. today we have initiated the schema update activity and i ran the preparelegacy command which ran successfully, then after that i ran the prepareschema command which was also successfull. after that i ran preparead command which was also successfull. but on the same time when preparead command was running, i was reported that few users are unable to receive mails from anybody. while sending mails to them we were getting the error:
Your message did not reach some or all of the intended recipients.

      Subject:  FW: NHRDN Nomination Form Raja 1410 (2)

      Sent:     10/15/2008 12:05 PM

The following recipient(s) could not be reached:

      Alok Narain on 10/15/2008 12:06 PM

            The message was undeliverable because the recipient specified has changed address permanently and forwarding was not applicable

            <servername.domain.COM #5.1.6>


I don't know what is the issue, is it due to exchange 2007 preparation or some other problem. it is happening with only 5 users. i have checked the ESM and found that users mailbox were disconnected after running the cleanup agent. and while reconnecting to the actual user, we were unable to connect to the same user. we removed the exchange attributes and tried to reconnect , then ESM hangs up while reconnecting. and were getting following error:

Unable to update Mailbox SD in the DS. Mailbox Guid: c30c0b3d-3714-4108-8925-29705e8c1c30. Error Code 0x8004010f
 with event id 9554.

Can you please help us in getting the error resolved at the earliest as one of the user is MD of the organization. please revert me if you need any assistance from my side

0
Comment
Question by:fextech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 2

Assisted Solution

by:mikef147
mikef147 earned 50 total points
ID: 22722172
I ran into this exact same problem last week.  

The problem, for me, was that security settings on the particular OU that these users were in somehow got messed up.    If I moved the users to another OU, re-built the Exchange 03 recipient update service policies, waited until that finshed, that everything worked fine.

My solution was to re-create the OU that these users were in.   I'd imagine you could also compare the security on a working OU to this particular OU and change what's missing.
0
 

Author Comment

by:fextech
ID: 22723684
the users are in different OU (one is in default Users OU) so i really can't check the permission.
Any other possibility you think of and most imporatant is what can be the root cause of the issue.
0
 
LVL 2

Expert Comment

by:mikef147
ID: 22723713
Do the permissions on the individual user accounts for Exchange Enterprise Servers group, Exchange Recipient Administrators and Exchange Servers groups match a working user?
0
 

Accepted Solution

by:
fextech earned 0 total points
ID: 22728450
in the users security tab, i selected the Allow Inheritable option in the advanced tab. then i removed the exchange attribute of the user and then reconnected the users with his existing id. and it worked.

But my main question is what was the problem (root cause)?
0
 
LVL 2

Expert Comment

by:mikef147
ID: 22731857
Unfortunately I'm still learning the inner workings of Exchange 07.   My best guess would be, for whatever reason that the users weren't inhertinng permissions, they were modified at one point for something.   I would also guess that the changes between Exchange 03 and 07 relating to recipient policies and RUS somehow cause the Exchange organization as a whole to no longer 'know' where the user's mailbox was.

0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In-place Upgrading Dirsync to Azure AD Connect
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This video discusses moving either the default database or any database to a new volume.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question