View request headers in IIS

To view request headers of incoming requests from IIS, you can use failed request tracing in IIS to include status code 200. This would log successful requests too and you can view all request headers in the "request details" > "general request headers" section.

Comments

OWA not working after security update

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. FarmStateReplicator.exe (0x0CD8) Office Web Apps Farm State 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

SharePoint 2013 workflow : The server was unable to process the request

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 http://sharepoint.stackexchange.com/questions/89101/failed-to-retrieve-the-com-class-factory-for-component-with-clsid-sp-sprequest Solution 1: 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 co

Error while starting VM - Failed to allocate resources while connecting to a virtual network

Solution: Change Network Adapter settings for the virtual machine to "Not Connected", start the VM and change the network adapter to the default one. Error Details: [Window Title] Virtual Machine Connection [Main Instruction] The application encountered an error while attempting to change the state of 'machine_name'. [Content] 'machine_name' failed to start. Synthetic Ethernet Port (Instance ID GUID): Error 'The specified network resource or device is no longer available.'. Failed to allocate resources while connecting to a virtual network. [Expanded Information] 'machine_name' failed to start. (Virtual machine ID GUID) 'machine_name' Synthetic Ethernet Port: Failed to finish reserving resources with Error 'The specified network resource or device is no longer available.' (0x80070037). (Virtual machine ID GUID) 'machine_name' failed to allocate resources while connecting to a virtual network: The

Small Talk - Blog by Houratious Albert

Search This Blog