SPDActivities - DP.SharePoint.Workflow - Workflow failed to run

One of my SP 2016 application is using SPDActivities of Email extended feature of DP.SharePoint.Workflow to provide custom "From" address. But customers started to complain that they are not getting reminder emails anymore. Find below my STAR analysis,

Situation:
Recently I was facing an issue - Approval workflow failed to run. Customers not getting reminder emails anymore.

Task:
- Planned to look into SharePoint services, IIS site, web.config files (WFE and App Server), Latest patch/MS update/CU, Users permission.

Analysis:
Started looking into each below items, 
- SharePoint Timer Service and Administration services were running and good
- Account which is running the workflow got required permission
- DP.SharePoint.Workflow got activated for the web application
- Checked into web.config file in WFE server and App Server for below sections

Under <SafeControls> below 3 lines need to added both in WFE and App server web.config files,
<SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow.InfoPath" TypeName="*" Safe="True" SafeAgainstScript="False" />
      <SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow.Install" TypeName="*" Safe="True" SafeAgainstScript="False" />
      <SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow" TypeName="*" Safe="True" SafeAgainstScript="False" />

Screenshot for reference:



Under <authorizedTypes> below line need to be added just 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" />

Screenshot for reference:

Resolution:
Actually both the above 2 changes were already made in web.config files of WFE and App server, but recent MS update has removed it seems in App server. So, after adding the lines back int web.config file of App server and IIS reset, Approval workflow started to run again.

Comments

Post a Comment

Popular posts from this blog

Power BI Refresh Issue: unable to convert the value '' from the source data type 'VT_BSTR' to the expected data type 'VT_I8.

Image
While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 .     Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Read more

Run Powershell script on Remote Computer/Server

Image
PowerShell Remoting allows you to run individual PowerShell commands or access full PowerShell sessions on remote Windows systems.   PowerShell is locked-down by default, so you’ll have to enable PowerShell Remoting before using it. This setup process is a bit more complex if you’re using a workgroup – for example, on a home network — instead of a domain.   Enabling PowerShell Remoting On the computer you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.   To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):  Enable-PSRemoting -Force This command starts the WinRM service, sets it to start automatically with your system, and creates a firewall rule that allows incoming connections. The -Force part of the command tells PowerShell to perform these actions without prompting you for each step     Workgroup Setup If your computers aren
Read more

wsp not getting deployed in all servers

Last week, got into an issue that wsp was not deployed in all servers and hang. Please find below more information on that: Issue: Unable to deploy wsp solution in SP2016 On-Premise server Resolution : C leared SharePoint config cache and rebooted all SharePoint servers and the SQL server, r an the command Add-SPSolution and  Install-SPSolution and the .wsp solution got deployed Troubleshooting Steps Followed: -     ​In Central Admin checked in Farm Solution Management the status was stuck on deploying​ -     Stopped the SharePoint Admin and SharePoint Timer services -     Checked and found multiple One-time jobs​, deleted those using the scripts below ​   -     Find onetimer running job from timer job definition and delete with below query Get-SPTimerJob | where{$_.schedule.description -eq "One-time"} | ForEach-Object{$_.Delete()}​ Get-SPTimerJob | where{$_.DisplayName -eq $null} | foreach-object {$_.Delete()}Get-SPTimerJob | where{$_.sc
Read more