Microsoft cloud engineer - SharePoint, Office 365, Azure, DotNet, Angular, JavaScript.
Microsoft cloud engineer - SharePoint, Office 365, Azure, DotNet, Angular, JavaScript.

SharePoint 2016

FIXED – SPDActivities Custom Action (SharePoint 2016 )

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!  

shades_smile

Issue

  1. WSP is fully deployed and installed
  2. Custom Action workflow steps are visible in SharePoint Designer
  3. Click action then suggestion menu disappears.   No action sentence is visible on designer.

image

Resolution

  1. Locate </targetFx> in [web.config] file
  2. Add below XML code both before AND after </targetFx>

<authorizedType Assembly=”DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83″ Namespace=”DP.Sharepoint.Workflow” TypeName=”*” Authorized=”True” />

  1. IISRESET
  2. Clear SharePoint Designer client cache https://stackoverflow.com/questions/43113666/how-to-clear-cache-in-sharepoint-designer-site
  3. Test
image

Root Cause

  • Appears that SharePoint 2016 leverages more Dot Net Framework versions (3.0, 3.5, 4.0, 4.5) and has a larger [web.config] to support backward compatibility with multiple Dot Net versions.

‘New-SPExcelServiceApplication’ is not recognized as the name of a cmdlet

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! 

shades_smile

Error Message

  • 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.

Root Cause

FIXED – stsadm upgrade command has been replaced by psconfig.exe

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! 

shades_smile

Error Screenshot

image

New Command

References

How to install Office Online Server for SharePoint 2016 (OOS)

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.

Cheers! 

shades_smile

Steps

  1. Install Windows Server 2012 R2 (en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso)
    1. NOTE – Windows Server 2016 seems to be missing Ink and Handwriting Support.
  2. Run PowerShell to install IIS

  1. Install Windows Identity Foundation
  2. Install Ink and Hand Writing Services
  3. Get latest Windows Updates
  4. Generate Self Signed Certificate
    1. Start > Run > INETMGR > Server > Server Certificates > Generate self signed certificate with “OOS” Friendly Name
    2. Start > Run > INETMGR > Server > Server Certificates > Export “OOS” to PFX file
      with password

    3. Start > Run > CERTLM.MSC > add Local Machine certificates > import PFX to “Personal” folder
    4. Start > Run > CERTLM.MSC > add Local Machine certificates > import PFX to “Trusted Root Certificate Authorities” folder
  5. Install Office Online Server (en_office_online_server_may_2016_x64_dvd_8484396.iso)
  6. Create new OOS farm

Screenshots

image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image

Error

  • Resolves the PowerShell error “New-OfficeWebAppsFarm : It does not appear that this machine is part of an Office Online Server farm.”

References

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲