SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

July 2017

What’s in that patch? Jul 2017

NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.

Ever wondered what fixes are inside of a given CU?   Please see attached PDF with full detail. I wanted a new format for easy reading.   Show management and make the business case for why downtime should be taken to apply CUs.  Also posted at http://sharepointupdates.com/

If you found this helpful, please leave a comment.   

shades_smile_thumb_thumb_thumb_thumb[2]

Download

What’s in that patch – Jul 2017.PDF

FIXED – Workflow Endpoint Not Found Exception: Unable to connect to the remote service

Recently I noticed the below error when viewing Workflow status on SharePoint Server 2013.   Root cause turned out to be a missing IIS binding for both HTTP: 12291 and HTTPS: 12290.   After adding the additional IIS binding the status page was able to render again.  Cheers!

shades_smile

Error

Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> Microsoft.Workflow.Client.WorkflowEndpointNotFoundException: Unable to connect to the remote service at http://sharepointwf:12291/SharePoint/default/c1740af1-82ad-4026-beb5-c6eddaea7d88/4d2c8da0-a0da-41c1-8387-96260df02a62/$Workflows/$Instances/4d10f51f-2e21-4ff7-aa3c-ceadde059a14. See InnerException for more details. Client ActivityId : 69ee049e-ffb2-209a-6826-71aedbaa6db7. —> 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 127.0.0.1:12291   
  at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)   
  at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)     –
— End of inner exception stack trace —   
  at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)

Screenshots

image
image
image
image

Office 365 – Hybrid Team Site Redirect AAM

Migrating team sites to Office 365?  Worried about broken links?  Check this out.

Recently I found a helpful STSADM trick that provides HTTP redirection for hybrid SharePoint farms moving team sites into the Office 365 cloud.   As we migrate sites and remove from the source farm on-premise users will see 404 Page Not Found when open old URLs.

However, we can use STSADM to provide a “<RedirectUrl>” Alternate Access Mapping (AAM) property on the source SharePoint Web Application (http://portal/*) which redirects user traffic to a destination Office 365 Tenant (ex:  https://tenant.sharepoint.com/*)

If you are gradually moving team sites into the cloud with third party tools (ShareGate, Metalogix, DocAve, etc.) this trick is invaluable to preserve a smooth user experience where old links will seamlessly redirect to Office 365 team sites in the cloud.  Cheers! 

shades_smile

Diagram

image

Commands

Enable AAM Redirect

Verify AAM Redirect

Screenshots

image

image

Video

References

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲