Here, I received another SharePoint 2013 workflow error.
This time the workflow was not able to send emails and the following error was being shown
Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP Unauthorized to http://sitename/_vti_bin/client.svc/web/lists/getbyid(guid'guid') Correlation Id: id Instance Id: id
Fortunately I came across this post which gave me the answer
In InetMgr, go to advanced settings for Security Token Service Application Pool and change "Load User Profile" to true. Recycle application pool.
Reason 2 and Solution 2 : There could be another reason for this error. The workflow authentication can fail if the user executing the workflow (this will be the user initiating the workflow) is given permission through active directory group and the container for t…
I recently came across this error while attempting to configure an external content type in SharePoint 2013.
The error message showed Access denied by Business Data Connectivity.
On verifying the ULS logs the found errors as given in the table beneath the post
This happens because you have not set access on the BCS object that you created. Go into Central Administration and select your External Content Type or other object and select Set Permissions from the dropdown. Your authentication is working or you would not be able to save the object you created to the metadata store. You now need to tell the metadata store who has access to the objects you created in BCS.
It worked like a charm.
Updating in my blog post so that someone searchin…
Office web apps for SharePoint 2013 not working after security updates / server patching.
After installation of the following security patches, OWA stopped working there by causing issues with SharePoint 2013.
Details of ULS logs are provided below.
Office Web Apps
Error when trying to connect to Farm State Manager service: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http:///farmstatemanager/FarmStateManager.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean con…