After you rebuilt your workflow, did you update the Workflow settings on the Document Library? I think by default if you deploy a newer version of a workflow, the Workflow settings are changed to No New Instances. To check, and rectify if this is the case: navigate to the Settings page for your Document Library, then select Workflow settings. Next choose Remove a workflow. Make sure the Allow radio button is selected and click OK. You may have already done this, but it can sometimes catch people out. David.
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Monday, 31 March 2008 1:26 PM To: [email protected] Subject: [OzMOSS] Workflow issues on MOSS Development Server Hi All, I'm having a few problems getting some SharePoint workflows going. I am using VS 2008, and started out trying to build a simple sequential workflow so I can get more familiar with coding under the WF / SharePoint model, but have run into what I think are a couple of problems, one of which I think I'm on top of, another which I'm not. The workflow is on an e-mail enabled document library, and the e-mails that come into the library have a unique subject line, but a subject line that contains colon characters. For example the original e-mail that generated the following entries had a subject line of "InboundRequest/IDX:13455242 - ID:1A10E6014CE4FF23CA257412000504B9". Interestingly the first colon seems to have been replaced with a space, but the second colon in the subject line appears to have been simply dropped. 03/27/2008 12:19:44.71 OWSTIMER.EXE (0x07AC) 0x0C80 Windows SharePoint Services General 8kh7 High There is no file with URL 'InboundRequest/IDX 13455242 - ID1A10E6014CE4FF23CA257412000504B9' in this Web. 03/27/2008 12:19:44.87 OWSTIMER.EXE (0x07AC) 0x0C80 Windows SharePoint Services Workflow Infrastructure 72fv Unexpected AutoStart Workflow: System.ArgumentException: Value does not fall within the expected range. at Microsoft.SharePoint.SPWeb.GetFile(String strUrl) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStart Workflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange, AssocType atyp) Can someone confirm that my supposition that the colons are the problem here is correct? I am now pre-processing the e-mails to ensure the colons are no longer present in the subject line, but now I'm getting entries in the log like the following: 03/31/2008 15:43:10.70 OWSTIMER.EXE (0x08EC) 0x0F68 Windows SharePoint Services Workflow Infrastructure 72fv Unexpected AutoStart Workflow: System.ArgumentException: New instances of this workflow template are currently disallowed. at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflowElev(SPList Item item, SPFile file, SPWorkflowAssociation association, SPWorkflowEvent startEvent, Boolean bAutoStart, Boolean bCreateOnly) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStart Workflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange, AssocType atyp) Any suggestions gratefully accepted. Have I mis-configured the workflow in some way? Kind Regards, Trevor ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com This is an email from Fujitsu Australia Limited, ABN 19 001 011 427. It is confidential to the ordinary user of the email address to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you. If you do not wish to receive commercial email messages from Fujitsu Australia Limited, please email [EMAIL PROTECTED] ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
