I am using an out of the box feedback workflow and have selected 'start this workflow when a new item is created'.
The workflow will only start when I manually kick it off
View Complete Post
Hi, I have a custom worklfow which is associated with a list. The workflow is set to auto start when a new item is added to the list. This happens fine for every user in my organisation, but not for one particular user. When he submits
a new item to the list, nothing happens. The Workflow just will not start. There are no errors in the log and no attempt is made to start the workflow. The user is part of a SharePoint group which has contirbute (no delete) permission on the list,
just like everyone else in that group who works fine.
This user also is having problems progressing the workflow, if I start the workflow for him and assign it to him.
The workflow above, manages a CR process, creating tasks for users, taking their responses from custom task forms and populating a CR document held in a document library. The first step for a user is to fill in a task form which when submitted, sets
the task to 100% complete, then populates the CR document with the text the user entered. Once the task is at 100%, the workflow process is looking for this, closes the task and creates a new task for an approver. The problem for this same is user
is that, the task gets set to 100%, but the CR doesn't progress. Again, no errors are shown, but the tp_workflowversion value in the userdata table in the content datab
I am running WSS 3.0 with other workflows which are functioning correctly.
I created a new workflow in Visual Studio 2008 and was able to successfully run it in my dev environment.
I attached the workflow to a task list in my dev environment and was able to manually start the workflow by using the drop down workflow option and using the menus to manually start it.
I installed this workflow in our production environment and attached it to the task list (which had a SPD workflow attached to it which stopped working about a month ago).
I made sure that the option to manually start the workflow was checked.
When I tried to manually start the workflow, (hover mouse over title, drop down) there isn’t a workflow option.
The workflow also will not start automatically when a task is changed.
I attached this same workflow to a different task list in production and get the option to start it.
I have tried creating a small workflow in SPD 2007 and attaching it to the task list.
It shows that it is attached, when I look at the workflows that are attached to the task list, but I still don’t get the option to manually start it.
I have checked my security and I have fu
We've been using the BizTalk SharePoint Adapter to load various different contents into a MOSS 2007 Document Library. The library has a MicrosoftÃÂ Office SharePoint Designer 2007 workflowÃÂ (sequential workflow created in Designer) which starts automatically when a new item is added to the Document Library. Or, at least, it eventually starts automatically.
For some unknown reason--and this is what we're hoping some of you may have some ideas on--the workflow fails to start on the first try, producing the "Failed to Start (retrying)" message. When the timer job comes back the second time, the workflow starts successfully, but this causes us to loose five minutes of potential work time (not to mention making us look bad to the VPs and CTO because they see the failure message).
In checking the log, I find the following pair of error messages each time the "Failed to Start (retrying)" status occurs:
In SharePoint 2010, I'm starting workflow #2 programatically from my workflow #1. See code below:
SPList currentList = web.Lists[new Guid(ListId)];
SPListItem currentListItem = currentList.GetItemById(ListItem);
//resolve any lookup parameters
string workflowId = base.ProcessStringField(WorkflowIdentifier);
//find workflow association by name
SPWorkflowAssociation workflowAssoc = currentList.WorkflowAssociations.GetAssociationByName(workflowId, Thread.CurrentThread.CurrentCulture);
if (workflowAssoc != null)
//start the workflow
SPWorkflow workflow = site.WorkflowManager.StartWorkflow(currentListItem, workflowAssoc, workflowAssoc.AssociationData, SPWorkflowRunOptions.Synchronous);
And workflow #2 will hang with Starting status (1-10 minutes), Then the workflow #2 status would be modified to Completed.
I couldn't find how to start the workflow # 2 immediately and complete immediately without several minutes delay
I have a SPD WF and I want to start it automatically by channging a value in a dropdown inside Excel.
Instead of going to Office button --> Workflows --> Start "Budget Approval", start the workflow by setting a value inside Excel (and maybe saving the file) to "Completed".
I have created a sequential sharepoint workflow in WSP Builder in my Sharepoint Server and Deployed it.
But the workflows says Failed on start and retrying ans stops there forever says couldn't start the workflow.
I repaired .NET Framework 3.5sp1 installed
1. I tried again, in C Prompt: Lodctr "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini" it says initiation file cannot be found
2 i again tried this C prompt Lodctr /R "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini"
it says reloaded from the system restored
i am still getting the same error.
When i manually go to my C:\Windows\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation i can see a folder for SQL that's it nothing more than that..
I dont know what is happening i am trying it from 2 days and still no solution.
any ideas would be real great help for me.
My system is 64 bit , Window server 2008, MOSS SP2, Visual Studio 2008 Version 9.0.30729.
.Net Framework 3.5 sp1
and WSP builder the one from Codeplex for 64 bit machines