Tech Trek – 2017 February
Runtime error occurs when initiating workflows, i.e. user reports that nothing happens, or failure occurs when attempting to transfer files (via OfficialFile.asmx Web service). Re-executing the workflow would result into the expected behavior.
This typically happens after a SharePoint upgrade or patch has been applied. As this affects only a certain component, this behavior may not be apparent after the update has been applied.
- Open SharePoint LOGS folder and check the affected log file at the time the event occurred to see if the following Unexpected error is present:
<CompilerError Line=”0″ Column=”0″
PublicKeyToken=71e9bce111e9429c is not marked as authorized in the application configuration file.” />
- Compare entry differences of the most recent web_<date/time>.BAK using a text comparison tool like WinMerge or WinDiff.
- Open web.config in the Web Front-end server at the following location and add/correct the affected component.
<authorizedType Assembly=”Microsoft.SharePoint, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.Workflow” TypeName=”SPWorkflowTaskProperties” Authorized=”True” />
- Perform an iisreset.
I’ve highlighted Version=184.108.40.206 since usually this entry reverts back to 220.127.116.11 in the SharePoint web.config file which causes the unauthorized issue.