Add following html in a content editor of workflow task display form. This will redirect user to editable approval form.
<script src="/PWA/SiteAssets/RedirectToEditForm.js"></script>
the javascript file RedirectToEditForm.js should have the following code:
var origUrl = window.location.toString();
var editUrl = origUrl.replace("DispForm","EditForm");
window.location = editUrl;
Note: Do not add Script tags in the file, just add code in file.
You are trying to synchronise user profile service and nothing gets imported. There could be several reason(s). I had following issues.
It is always a good idea to take help from the Active Directory folk, if you come across issues while syncing USP.
Following shows ports that are required for communication between servers (App, WFE & DB) for SharePoint.
| Protocol | Port | Usage | Comment | Server | Source IP(s) | Destination IP(s) |
| TCP | 80 | HTTP | Client to SharePoint web server traffic (SharePoint – Office Web Apps commun..) | SharePoint/ Project Server (Web Front End) |
Client Machines |
WFE App |
| TCP | 90 | HTTP | Client to SharePoint web server traffic (SharePoint – Office Web Apps commun..) | SharePoint/ Project Server (Web Front End) |
Client Machines |
WFE App |
| TCP | 443 | HTTPS/SSL | Encrypted client to SharePoint web server traffic (Encrypted SharePoint – Office Web Apps commun..) | SharePoint/ Project Server (Web Front End) |
Client machines |
WFE App |
| TCP | 25 | SMTP for e-mail integration | Cannot be configured | SMTP Server | App | (SMTP) |
| TCP | 1433, 445 | SQL Server using named pipes (445), SQL Server default commun.. port (1433). | Client to Database server | Database Server | App | DB |
I followed the below step in order to delete Workflow Manager.
Note: If you’re recovering your workflow environment, your existing workflow won’t be deleted as they reside in content db. Once you setup Workflow Manager, check if you can see “SharePoint 2013 Workflow” and “Project Server 2013 Workflow” options in SharePoint Designer (I had to connect Workflow Application Service with the Web Application). Only then your existing workflow will show up under workflows in SPD.
Courtesy:
http://social.technet.microsoft.com/wiki/contents/articles/27689.sharepoint-2013-how-to-fully-uninstall-workflow-manager-1-0.aspx
http://e-sharepoint.blogspot.ae/2014/04/problems-with-workflow-manager-10-and.html
If deploying WSP using Visual Studio, you’ll end up with the following error.
Error occurred in deployment step ‘Activate Features’: Feature with Id ‘8a442317-1158-4994-b265-26499b2def57’ is not installed in this farm, and cannot be added to this scope.
Solution:
Just manually created package and deploy
Starting up a list workflow, was throwing following error.
Error:
RequestorId: 675358e8-c91d-0f3a-ebaa-d663a9a1202d. Details: System.ApplicationException: HTTP 401 {“error”:{“code”:”-2147024891, System.UnauthorizedAccessException”,”message”:{“lang”:”en-US”,”value”:”Access denied. You do not have permission to perform this action or access this resource.”}}} {“Transfer-Encoding”:[“chunked”],”X-SharePointHealthScore”:[“0″],”SPRequestGuid”:[“6359f5a3-808a-4144-ace2-0fdff207809f”],”request-id”:[“6359f5a3-808a-4144-ace2-0fdff207809f”],”X-FRAME-OPTIONS”:[“SAMEORIGIN”],”MicrosoftSharePointTeamServices”:[“15.0.0.4569″],”X-Content-Type-Options”:[“nosniff”],”X-MS-InvokeApp”:[“1; RequireReadOnly”],”Cache-Control”:[“max-age=0, private”],”Date”:[“Sun, 30 Nov 2014 08:08:36 GMT”],”Server”:[“Microsoft-IIS\/8.0″],”WWW-Authenticate”:[“NTLM”],”X-AspNet-Version”:[“4.0.30319″],”X-Powered-By”:[“ASP.NET”]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Resolution 1:
PS C:\Users\exceed.epm> Get-SPTimerJob “RefreshMetadataFeed” | Start-SPTimerJob
Resolution 2 (In my case it worked):
Activate site feature “Workflows can use app permissions”
Site actions > Site Settings > Site features > Workflows can use app permission
[Updates 10-08-2016]
Resolution 3:
This time above two resolution didn’t work. Had to install CU3 of Workflow Manager and Client.
