Step by step video on how to fix the SharePoint Workflow issue caused by .NET patch
This post is a continuation of this previous post. It is also an extension of KB4465015. The video assumes you read the previous post and/or KB. The page to the scripts mentioned in the video can be found here: https://gist.github.com/joerodgers/2302b394796c865818839d843bae2dad
After installing .NET security patches to address CVE-2018-8421, SharePoint workflows stop working (KB 4457916/4457035 and others)
*** FINAL UPDATE VI *** SharePoint CUs are out The Nov 2018 SharePoint CUs The SharePoint with fixes are available. Some environments using third-party solution may still need to follow the steps on this post: Description of the security update for SharePoint Enterprise Server 2016: November 13, 2018 (KB4461501) Description of the security update for
SharePoint 2013/2016 Usage Reports fail to show the correct number of clicks from anonymous access
Symptom When using a Search Center with anonymous access, click statistics do not compute correctly for anonymous access but registers other user’s accesses properly. ULS logs will show entries like this: w3wp.exe SharePoint Foundation CSOM ajwqj Medium Request does not have SPBasePermissions.UseRemoteAPIs permission. Need to check it when each API is accessed Repro Steps Set
Leveraging the new Time Travel Trace API in Debugging tools to find when one or more SharePoint event happened
In my previous post, I showed a proof-of-concept script to list all occasions a process opened a file. JavaScript is easy to program and works for most cases, however in some occasions you need to access resources not available from JavaScript and only a full-fledged debugging extension will do. In this post I will show
After updating SharePoint 2013 to November 2017 CU or later you may not be able to open documents with Office
*** UPDATED TO INCLUDE Stefan Gossner and Adam Soreson’s INPUT *** Symptom After updating SharePoint 2013 to November 2017 CU from a previous version you will not be able to open Office documents (Word, Excel, PowerPoint) but other types of documents like .txt and .pdf files can be opened. There is no indication of the
SharePoint 2013 and 2016 does not respect the user zone when sending alerts but the Cross Firewall Access Zone (an unusual scenario)
Symptoms Consider you have a one Web Application with at least two zones. The extranet zone (http://sp2016 in this example) and an intranet zone (http:sp2016:100 in this example). The cross firewall zone is the intranet zone (http:sp2016:100 in this example). Notice that this is an unusual scenario as extranet is the natural candidate to
Tool to generate DebugDiag rule for SharePoint based on event id (Tag) and optionally a partial message
When I updated my post on how to create DebugDiag rule based on event id (Tag), I received some feedback that modifying the scripts is quite error prone and more often than not the resulting script would not work as expected. To that end, I decided to create a visual tool that will create the
SharePoint 2013/2016 RSS Viewer not working with external sites when through a proxy
Recently I worked on a case for a Fortune 500 company that was having problems to render the RSS Viewer Web Part in their SharePoint 2013 farm. They still have a SharePoint 2010 farm in the same network environment and this farm was not having problems rendering the RSS Viewer. The constraint was this:
The [unofficial] guide for SharePoint 2013 (and 2010) working with TLS 1.2 only
There are several resources out there claiming SharePoint 2013 and 2010 are not compatible with TLS 1.2 but no official stance from Microsoft either way until now. This post is still not the official response, but it is the first step in this direction. Official documentation to follow. The official supportability is explained in the
Misbehaving custom SharePoint components leading to claims authentication exceptions (tag bz7l)
I have mentioned the steps to troubleshoot Claims to Windows NT Service (c2WTS) problems in a previous post (click here). There is also a post to see if the problem is with Active Directory (AD) or c2WTS (click here). After doinf the normal troubleshooting outlined in the previous posts you still have an issue