Cannot contact SharePoint on-premises server

(0) Share

Report

Posted on by Community Member

I'm trying to configure server-based integration between CRM Online and SharePoint 2013 on-premises and this is the error that shows up on the validation step:

Cannot contact site at the specified URL sharepoint.domain.com/.../crm

Is this because we're using a non-standard port (4443)? I can confirm that the SharePoint site is accessible from the internet through a reverse proxy (Microsoft Remote Access) and users can successfully log on via AD FS. We're using a 3rd party certificate.

I've gone through the steps mentioned here to grant Dynamics 365 access to SharePoint On-prem: https://technet.microsoft.com/en-us/library/dn894709.aspx

Anyone know what else I could be missing?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report
Copy link

Link copied!

We had that issue in the past. Per Microsoft, SharePoint must use SSL.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

We are using SSL with a 3rd party certificate. The URL in the error message mentions "https ://sharepoint.domain.com:4443/sites/crm" but the https:// got hidden in the post.

Was this reply helpful? Yes No
Tony Amaral 190 on at

Like (0)

Report
Copy link

Link copied!

I'd stay away from integrating Dynamics with SharePoint. I was never able to get the server side integration working since 2016 and Microsoft was never much help. The way documents are managed in SharePoint in my opinion is a mess and I don't see much interest from Microsoft in making this integration a simple and straight forward feature. I'd keep my documents in Dynamics only, it has a pretty decent doc management.

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report
Copy link

Link copied!

It is possible that the issue is the port number, as the configuration is not expecting that value.

You should see if you can get this to work with port 443.

Was this reply helpful? Yes No