“Unable to render the data. If the problem persists, contact your web server administrator.” error in SharePoint 2016 BCS

Created an external list SharePoint 2016 using business data connectivity services, configured secure store target application and created external list in SharePoint.
The external list displayed this error message with a correlation ID.

“Unable to render the data. If the problem persists, contact your web server administrator.”

unable-to-render-the-data-if-the-problem-persists-contact-your-web-server-administrator

ULS Log viewer found this message in the logs:

Error while executing web part: Microsoft.BusinessData.Infrastructure.BdcException: The shim execution failed unexpectedly – Unable to obtain the application proxy for the context.. —> Microsoft.Office.SecureStoreService.Server.SecureStoreServiceException: Unable to obtain the application proxy for the context.

Solution:

The web application is not associated with the secure store service application.

  • Go to SharePoint Central Administration site
  • Application management >> Click on Configure service application associations under Service Applications.
  • select the web application in which your site exist, Check the “Application proxy group” column >> Make sure the BDC and secure store service applications check boxes checked.

service-application-association-sharepoint-2016

SharePoint sites not opening locally IIS Error

I am having this strange problem . All of a sudden all of the new sites created in the SharePoint are not opening locally. And even iis is failing to pick up the ip binding with a site. All my existing sites when browsed from IIS manager are giving certificate error and ultimately showing connection problem error. Only thing that was done was the patching this week. I have no idea why all this is happening. Has any one faced similar problems before.

Solution :

  • try stopping the Foundation Web service on the affected farm member and re-starting it.

  • If you were adding SSL certs to the IIS sites, it may be a case of attempting to use the same IP with different SSL certificates across IIS web sites.  IIS 7.5 and below do not support SNI, so you have to have a unique IP:SSL Cert combination, or get a Wildcard or SAN certificate instead.