Error while using Workflows within Sharepoint Site
Hi,
I tried using the sample workflows from the ECM release (ECM sample started kit). Now this is what happens:
I can install the workflows and the forms correctly. Once I go into my Sharepoint site, I can connect it to the workflow that I want. But once say I add a new document, open it in thr word client, from there say I click on "Start Workflow" this seems to fail for EVERY WORKFLOW - even those built in default (Approve etc).
The initialization and association forms come up and I fill these (workflow has not started yet), once I click on "submit" (or any other button which is supposed to start a workflow) on the document library, I can see "Failed to Start" under the name of the Workflow.
On further investigation: When I run reports on these workflows, the xml worksheet says this: "Approval failed to run. Exception has been thrown by the target of an invocation."
Also of note, somehow my debugger never really attaches to the w3wp process,hence I am unable to try to debug and resolve this issue on my own.
Really looking forward to any sort of reply on this,
I am unable to run any sort of workflows (custom or otherwise) as a result,
Thanks
Mayur
[1370 byte] By [
Mayuresh] at [2007-12-21]
I think I have your answer for this one: "Also of note, somehow my debugger never really attaches to the w3wp process,hence I am unable to try to debug and resolve this issue on my own."
In the case where you are running Vista, and using Visual Studio 2005, and you want to debug processed that you do not own, you'll need to run Visual Studio 2005 as Administrator to enable debugging. Simply joining Debugger Users, or being an Administrator on the box, doesn't do it (at least in my experience) Could your problem be related? Permissions to attach to the process you want to debug? Have you tried to manually attach to the process? Are you attempting remote debugging? Does the Sharepoint server allow it?
Hi Ian,
Sorry for the late reply!
Well, I earlier had VSTO (June CTP) configured on the same machine as the WinWF beta 2.2 These are incompatible versions. In the new configuration, I installed in roughly this order:- Win Server 2003, promoted to DC, SQL 2005, WinFX, WinWF (runtime and extension 2.2), MOSS and Visual Studio (TS) on one virtual AND MS Office 2007, VSTO, Again VS 2005 (TS) on another virtual. Thus I had to install Visual Studio on both the virtuals, but they serve different purposes (one is for WF Workflows creation another for VSTO Projects). This separation seems to have fixed the issue.
Let me know if this fixes your problem or if you have any other issue on this...I have played around the installations quite a bit by now and might have some insight;-)
Best luck with your installs (I think you need it for the beta stuff)!
Mayur Khare
