After troubleshooting an issue with SharePoint Designer, I wanted to document the fix for others. Installing the “DP.CustomActions” WSP from CodePlex worked well on SharePoint 2010 and 2013. However, with 2016 an issue occurs which requires additional [web.config] modification. Details below. Cheers!
WSP is fully deployed and installed
Custom Action workflow steps are visible in SharePoint Designer
Click action then suggestion menu disappears. No action sentence is visible on designer.
Locate </targetFx> in [web.config] file
Add below XML code both before AND after </targetFx>
Recently I was building a new SharePoint 2016 farm and came across the below error with older PowerShell SharePoint 2013 install scripts. Expected error as Microsoft moved the functionality to Office Online Server. Cheers!
The term ‘New-SPExcelServiceApplication’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Microsoft removed the Excel Service Application from SharePoint Server.
Office Online Server has the functionality going forward.
Recently I came across the error below when upgrading a SharePoint 2016 farm. Expected product behavior and simply a case of training SharePoint Administrators to use PSCONFIG.EXE command line instead. Cheers!
stsadm -o upgrade -inplace b2b –force
Command line error. Invalid parameter.
stsadm –o upgrade command has been replaced by psconfig.exe -cmd upgrade
Recently I wanted to create a SharePoint 2016 lab environment. With Excel Services moving out of the SharePoint 2016 product, we now need to plan for an instance of OOS. Below are the steps I followed and screenshots of the process.
Install Windows Server 2012 R2 (en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso)
NOTE – Windows Server 2016 seems to be missing Ink and Handwriting Support.