Plantronics + Polycom. Now together as Poly Logo

"Failed to discover exchange server" S4B O365 Trio 8800

ndong
Occasional Visitor

"Failed to discover exchange server" S4B O365 Trio 8800

I am able to log into S4B but when I click on the calendar it comes with an error "Failed to discover exchange server"

 

Thanks in advance

Message 1 of 5
4 REPLIES 4
SteffenBaierUK
Polycom Employee & Community Manager

Re: "Failed to discover exchange server" S4B O365 Trio 8800

Logs and currently used software version?
----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 5
ndong
Occasional Visitor

Re: "Failed to discover exchange server" S4B O365 Trio 8800

Software: 5.4.3 AE

 

 

SteffenBaierUK
Polycom Employee & Community Manager

Re: "Failed to discover exchange server" S4B O365 Trio 8800

Hello ndong,

welcome to the Polycom Community.

The logs are full off:

 

1027125437|pgui |4|00|Auto discover service sending request to URL https://adaptiveinsights.com/autodiscover/autodiscover.xml.
1027125437|pgui |4|00|CSoapTransaction error = Operation canceled (5)
1027125437|pgui |4|00|'autodisc' Service CSoapTransaction network error = Operation canceled (5)
1027125437|pgui |4|00|Auto discover service network error 5.
1027125437|pgui |4|00|Auto discover service sending request to URL https://adaptiveinsights.com/autodiscover/autodiscover.xml.

Looking up the above returns with a:

 

404 Page Not Found
Sorry, but that page was not found.

I would look this up with your IT team.

 

For any further support please contact SCANSOURCE COMMUNICATIONS as they are your reseller and they can open a support ticket with Polycom for you.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 4 of 5
JetzeMellema
Occasional Advisor

Re: "Failed to discover exchange server" S4B O365 Trio 8800

That section does not neccesarily indicate an error. Exchange Autodiscover uses a fixed order of steps to locate the Exchange Autodiscover service. The first step, https://<domain>/autodiscover/autodiscover.xml, is supposed to fail in almost every single real world scenarion. Many organizations have Autodiscover configured with the autodiscover.<domain> hostname or are even using SRV records. This means that after the failing first method, one of the next methods should complete succesfully:

 

1. https://<domain>/autodiscover/autodiscover.xml (typically fails)

2. https://autodiscover.<domain>/autodiscover/autodiscover.xml (often used)

3. http://autodiscover.<domain>/autodiscover/autodiscover.xml (http 302 redirect expected)

4. _autodiscover._tcp.<domain> (contains the fqdn of the server to connect to for Autodiscover)

 

If UCS/LPE tries option 1, which is supposed to fail, and does not proceed with one of the alternate methods you may run into a bug.

 

Edit: It appears that Exchange Autodiscover is not configured for your domain at all. Method 1 connects to a webserver that is not running Exchange, method 2 resolves to an IP but this host is not listening on port 443, method 3 fails as well becasue the host is not listening on port 80 either and the SRV record for method 4 were not created.

 

I think the logging could be improved to give better feedback.

Message 5 of 5