SharePoint Destination

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

Today I got into a situation to restore the previous version of one of the SharePoint Designer 2010 workflows, created in SharePoint Designer 2013. 1.      In the left pane of SharePoint Designer, click the little pin icon next to  All Files . 2.      Now look for the folder Workflows on the right pane and look for your workflow. 3.      My situation was to restore a previous version of the workflow “Reminder Test. Select and expand it.  4.      Each of these files has a set of versions. Right click on the XOML file and choose  Version History . Select the version you would like to restore. (For my there is some problem in loading version history and so couldn’t provide the screenshot) 5.      Click  Restore . 6.      Right click on the next file, the XOML.rules. Go find that exact same date/time of the f...

Hello, I was dealing with this issue and getting errors like -  " Workflow Service: The HTTP request has timed out after 20000 milliseconds " and "Save cannot be performed and server cannot be reached". Resolution: Make sure the following services are restarted -               Service Bus Gateway               Service Bus Message Broker

Note 1:  By default this feature is enabled in “Developer Site”. So if your site has been created with the “Developer Site” template then do not use this article since this is for non-developer sites. Note 2:  Enabling this feature is not recommended for production sites. Sideloading apps is insecure. The main reason for blocking sideloading by default on non-developer sites is the risk that faulty apps pose to their host web/host site collection. Apps have the potential to destroy data and make sites or, given enough permissions, can even make site collections unusable. Therefore, apps should only be sideloaded in dev/test environments and never in production. ( Referenece:   Apps for Office and SharePoint blog ) Pre-requisites Install Windows PowerShell from Windows Management Framework (I installed the Windows Management  Framework 3.0 ). Then install “SharePoint Online Management Shell”  Link . Procedure Execute a PowerShell script in any desktop n...

In this article, we look at how to solve the ECB menu refresh in the federated authenticated site.   Note 1   This issue is only for federated authentication and not for Windows Authentication mode.   Note 2   In our scenario, LogonTokenCacheExpirationWindow is 9 minutes and ServiceTokenCacheExpirationWindow is 10 minutes. So, the popup holds good for 1 minute.   In federated authenticated site, ECB menu of an item (List or Library) refresh depends on the lifetime difference between LogonTokenCacheExpirationWindow and ServiceTokenCacheExpirationWindow. By default, it is 10 minutes for both and hence when the ECB menu is clicked the second time after the page loaded, the popup won’t appear. The issue here is the popup must make an AJAX call which expires because the cache is already expired. Select an item under any app in SharePoint and click on the second level ECB Menu (For example click “…” of any document and then again click “…...

To get SharePoint Search service app pool details like name, id use the below script, Get-SPServiceApplication | Select Name, @{Name="SPAppPoolName"; Expression={$_.ApplicationPool.Name}},  @{Name="IISAppPoolName"; Expression={$_.ApplicationPool.Id}}, @{Name="ProcessAccountName"; Expression={$_.ApplicationPool.ProcessAccountName}}

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} | fo...