Exchange EWS error about displaymonkey HOT 11 CLOSED

Hi, we have just released an update 1.4.0. Please upgrade and see if it will take care of your issue.

from displaymonkey.

Hi

I hev recently upgraded to new version but now it says "Couldn't resolve". As I said before I can login and get the xml file over web with the same username and password. where can I look to the logs to analyze the issue?

regards,

from displaymonkey.

Hi, it's hard to tell what the real issue is, because it may come from EWS setup. There is an application setting in DMM where you can specify full path for the log file which will receive transcript of EWS handshake when you attempt to connect. It might help shed some light.

Also, albeit optional, when you register EWS account record in DMM see if you enter a "EWS Url (optional)" value. This is useful when EWS auto discovery is not fully setup in your organization. For example, an entry for Outlook 365 would look something like: "https://outlook.office365.com/EWS/Exchange.asmx". If you do not specify a value both DMM and DMP applications will attempt to autoresolve EWS service endpoint address on every call to it based on specified account email address.

from displaymonkey.

Hi, please advise if the previous suggested remedy has worked for you. Thanks you.

from displaymonkey.

Have you tried following our suggestion to activate the trace file and see what is in there?

from displaymonkey.

Hi,

I wrote the whole entry of the Ews server and I can go in that address over web and see the xml file. How can I activate the trace file and see the those logs?

regards,

from displaymonkey.

Please read up in this thread for our suggestion on how to activate the trace file.

from displaymonkey.

Hi

below is the trace result

"

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="15" MinorVersion="0" MajorBuildNumber="1263" MinorBuildNumber="5" Version="V2_23" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<m:ResolveNamesResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:ResolveNamesResponseMessage ResponseClass="Error">
<m:MessageText>No results were found.</m:MessageText>
<m:ResponseCode>ErrorNameResolutionNoResults</m:ResponseCode>
<m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
</m:ResolveNamesResponseMessage>
</m:ResponseMessages>
</m:ResolveNamesResponse>
</s:Body>
</s:Envelope>
"

regards,

from displaymonkey.

Well, sounds like your handshake with EWS succeeds indeed. It's probably the mailbox address which you specify that EWS cannot resolve.

We cannot help you here unfortunately. From this point you might want to either take this up with the Exchange team in your organization or try self-support by using your favorite web search engine on "ErrorNameResolutionNoResults".

from displaymonkey.

Consider this scenario - you are trying to resolve a mailbox for a valid Outlook contact which has no mailbox/calendar resources associated with in the Exchange repository.

from displaymonkey.

Closing this post. According to logs above this is not a DM issue.

from displaymonkey.