Exchange Connector

Hi,

Im setting the Exchange connector and Iam facing this kind of error:

Anyone seen this?

Event 1

EwsResponseHttpHeaders: <Trace Tag="EwsResponseHttpHeaders" Tid="14" Time="2014-04-17 21:13:36Z">
401 Unauthorized
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Thu, 17 Apr 2014 21:13:36 GMT
Content-Length: 0

</Trace>

Event 2

Exchange Connector: Failed to poll the inbox at https://webmail.mydomain/EWS/Exchange.asmx for new mail, details: The request failed. The remote server returned an error: (401) Unauthorized.

Thanks

April 18th, 2014 12:40am

Exchange Connector: Failed to poll the inbox at https://webmail.mydomain/EWS/Exchange.asmx for new mail, details: The request failed. The remote server returned an error: (401) Unauthorized.

check your account settings and permissions, primarily Impersonation settings if you are using impersonation. one of those is usually the cause of this problem. 

  • Proposed as answer by Thomas Bianco Tuesday, April 22, 2014 2:52 PM
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2014 5:24pm

Agree with above, most likely cause is impersonation.
April 22nd, 2014 8:36am

Hi Thomas,

Thanks for your attention, but Im not using impersonation, my account has a mailbox, also I tryed to configure using impersonation and Im getting the same error, for me looks like something with Exchange server I will try to forward the error to the Exchange team to see if they can give me a light....

Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2014 6:09pm

try connecting directly to the web service as a test. Also enable additional logging to help see what the issue is. The additional logging helps a lot
April 22nd, 2014 7:02pm

Hi Guys,

Just to let you know we found the problem, was the exchange forms, we need to disable the forms on OWA, then worked fine.
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2014 7:22am

OWA shouldn't have anything to do with Exchange Web Services. perhaps there was a separate permissions issue?
April 29th, 2014 4:28pm

Just use the RUN AS account in this form   Domain\Account  or   account@domain.com

this worked with me fine

Free Windows Admin Tool Kit Click here and download it now
February 18th, 2015 1:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics