Category | Workflow

Very often you need to retrieve a published InfoPath form, unfortunately, in SharePoint 2010 this is quite an ordeal.  In SharePoint 2007 you could simply open the InfoPath forms library in explorer view then open the forms directory and the template.xsn file would be readily visible.  In SharePoint 2010 the template.xsn file is now much better hidden/protected by SharePoint 2010.  In order to retrieve the document follow one of the two steps below. Method 1 The easiest method is to simply access the file via URL, keep in mind, when you publish the form its name is changed to template.xsn. ...

---

Problem You are receiving the error similar to the one below when attempting to execute a SharePoint WWF workflow.  ====================================================================================== 11/19/2009 10:52:19.18     w3wp.exe (0x17FC)                          0x157C    Windows SharePoint Services      Workflow Infrastructure          88xr   ...

---

Problem I had a completely phantom error today and I never did figure out the cause was but I thought it might help to explain how it happened, and my thoughts to the cause.  The environment is MOSS Enterprise SP2 development environment with Visual Studio, VSTE 1.3, Office 2007, WSPBuilder, and SQL all onboard, obviously supporting Windows Workflow Foundation workflows.  Over the last few days I’ve been struggling with strange bugs in my InfoPath task forms that required a million installs and uninstalls of the wsp, I finally noted that my task form was stuck in an “installing”...

---

  (See also http://www.sharepointassist.com/2009/01/08/sharepoint-workflow-failed-on-start-retrying/) Problem You’re developing a Windows Workflow Foundation (WWF) workflow and no matter what you do you get the Workflow “Failed on Start (retrying)” message.  In my case I debugged over and over again only to see the TaskCreate method throw an exception (that you can’t capture) and fail.    Solution Specify a token other than the default Workflow1 or top level token.  I like to use “task1, task2, or taskAdmin” or something of those sorts to organize...

---

Problem You've developed a custom workflow using Windows Workflow foundation, Visual Studio, and a nice little product called InfoPath, however, when you test your workflow you get the error message "This form cannot be opened. It is not workflow enabled." If this above change doesn't work follow the steps in this blog article about publishing a workflow enabled InfoPath form.   Resolution This form cannot be displayed properly because your security level is not set to "Domain". Open the form and republish it with the security level = "Domain"

---