Remote certificate and listening errors when SharePoint is using SSL

  • 16 February 2021
  • 0 replies
  • 102 views

Userlevel 2
Badge +9
 

Remote certificate and listening errors when SharePoint is using SSL

KB001297

PRODUCT
K2 blackpearl 0807 to 4.6.10
BASED ON
K2 blackpearl 0807
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Summary

When calling K2 web services from SharePoint and SSL is configured for both SharePoint and K2, you may receive 'remote certificate' errors when SharePoint renders the list.

One or more of the following errors may occur:

  • The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> The remote certificate is invalid according to the validation procedure.
  • Server was unable to process request. ---> The shim execution failed unexpectedly - There was no endpoint listening at https://{ <https://{/> SharePointServer}/SecureStoreService.svc/https that could accept the message. This is often caused by an incorrect address or SOAP action.
  • There was no endpoint listening at https://{ <https://{/> SharePointServer}/SecureStoreService.svc/https that could accept the message. This is often caused by an incorrect address or SOAP action.
Cause

This issue is caused by the certificate chain becoming invalid when periodic checks are made to validate the SSL certificates. This is a known issue when using SSL in SharePoint. For more information and a workaround, see the Microsoft KB Site slowness due to SharePoint STS Certificate CRL checking (http://support.microsoft.com/kb/2625048).

 

 

Additional Information

Use the following resources if you need more information about this cause of these errors.

 

 


0 replies

Be the first to reply!

Reply