Sign in

Microsoft.com

Microsoft

Remove From My Forums

Incoming Status: Failure when testing the connection with Email Router

Question
0

Sign in to vote
Hello,

We've got a problem configuring Microsoft E-mail Router Configuration manager

When we take the connection test the program gives the following error

Incoming Status: Failure - The server to which the application is connected cannot impersonate the requested user due to insufficient permission.

We then checked the permission but the user we’re using to connect is a domain administrator with permission to full access the mailbox specified,
it's even set to impersonate every user.

Exchange Server is 2007

Could anyone help us diagnose this problem?
Thanks
- Edited by r3.jashworth Wednesday, September 12, 2012 4:13 PM
Wednesday, September 12, 2012 4:13 PM

Answers

1

Sign in to vote
Hi,

There could many things that are required to be checked here. You can use below link to get to the root cause of this issue and resolve it. Check out the comments in below link by a user having same issue as yours:

http://calendarservermigration.blogspot.com.au/2007/08/exchange-2007-impersonation-debugging.html

If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" Thanks, Imran Abbasi
- Marked as answer by r3.jashworth Wednesday, September 19, 2012 9:19 AM
Thursday, September 13, 2012 3:55 AM

All replies

1

Sign in to vote
Hi,

There could many things that are required to be checked here. You can use below link to get to the root cause of this issue and resolve it. Check out the comments in below link by a user having same issue as yours:

http://calendarservermigration.blogspot.com.au/2007/08/exchange-2007-impersonation-debugging.html

If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" Thanks, Imran Abbasi
- Marked as answer by r3.jashworth Wednesday, September 19, 2012 9:19 AM
Thursday, September 13, 2012 3:55 AM
0

Sign in to vote

Thank you Imran Abbasi for your reply,
It helped alot in diagnosing our problem.

However I need to specify that the command in that guide didn't fully solve the problem, when launched in PowerShell most gave an error,
we had to use the line referenced in this guide to fix the problem by giving an user full impersonating privileges:
http://msdn.microsoft.com/en-us/library/exchange/bb204095(v=exchg.80).aspx

Hope this can help others

Wednesday, September 19, 2012 9:25 AM