Sign in
 
HomeSharePoint Server 2010SharePoint Foundation 2010SharePoint OnlineLibraryForums
SharePoint Products > SharePoint Products and Technologies Forums > SharePoint - Workflow (pre-SharePoint 2010) > Infopath Workflow The form has been closed. form cannot be found

Answered Infopath Workflow The form has been closed. form cannot be found

Answers

  • Thursday, January 31, 2008 10:59 PM
     
     Answered
    Sign In to Vote
    0
    Sign In to Vote
    yes I figured out the problem,
      
        the problem is being caused by the fact that your info path form does not properly install as a viable template, if you look at central admin and look at infopath templates, you will see that your forms are not properly installed. The hosting aspx is basically complaining and saying that it is not receiving anything. I wrote a blog post about it, check it out

    http://juanlarios.blogspot.com/2008/01/workflow-infopath-forms-stuck-on.html


    it's more detailed but it involves publishing the info path form, read it , if you have questions I will reply. 


    regards,

     Juan
     
  • Tuesday, February 12, 2008 4:12 PM
     
     Answered
    Sign In to Vote
    0
    Sign In to Vote
    DrNash1111,
     
       check Central Admin, I think it's under Operation Management, and go to your InfoPath Section where it has all the templates. check to see what the status of your infoPath template. 

       If my guess is correct it should not be installed properly and waiting on a "installing" or "pending" state. Let me know if that's the problem.

       that means your infopath form was not installed properly. At least you can trouble shoot a little more targeted after you find that out,

       let me know so I can instruct you further if that is the case.

    JuanL
     

All Replies

  • Monday, May 14, 2007 1:18 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    hi bruce,


    if you get form closed message means there is a problem with your infopath form ,
    1. Problem with form urn's
    2. Problem with datasource.
    3. make sure that the infopath form is browser compatible

    make sure that both r given correctly,

    check security and trust for forms, give domain or full trust.

    check error log for more information reside in web server extensions/12/logs

    thanks
    praveen


     
  • Monday, May 14, 2007 8:12 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    Adding this to the Features XML resolved the issue.  

     

    Specifies what assemblies will receive events. 

     

    ReceiverAssembly="Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

    ReceiverClass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver"



    Bruce VB
     
  • Thursday, December 06, 2007 11:17 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    I am having the same problem and my log file says:

     

    Exception occurred during request processing. (User: AURORAWATER\tim.stewart, Form Name: , IP: , Request: http://moss-dev:8080/_layouts/CstWrkflIP.aspx?ctype=0x010101009B1A00198835864D8B534FA4FCD8C16A, Form ID: , Type: InfoPathLocalizedException, Exception Message: The specified form cannot be found.) 

     

    I have not found any good documentation on the Association_FormURN syntax:  Here is an excerpt of what I have in my workflow.xml:

     

    <MetaData>

       <Association_FormURN>urn: schemas-microsoft-com: office:infopath:workflow: Proposal-Assoc-1033:-myXSD-2007-05-08T04-21-20</Association_FormURN>

       <AssociateOnActivation>true</AssociateOnActivation>

    </MetaData>

     

    (I embeded some spaces after a few of the colons that were causing smiley faces to appear).

     

    Excerpt from my feature.xml:

     

    <ElementManifests>

       <ElementManifest Location="workflow.xml" />

       <ElementFile Location="ChangeOrderProposal_Assoc_1033.xsn"/>

    </ElementManifests>

    <Properties>

       <Property Key="GloballyAvailable" Value="true" />

       <Property Key="RegisterForms" Value="*.xsn" />

    </Properties>

     

    Here are my data source's details (from InfoPath):

     

    myFields (Group)

    Namespace: http://schemas.microsoft.com/office/infopath/2003/myXSD/2007-12-06T19:17:16

    Minimum occurrences: 1

    Maximum occurrences: 1

    Default value: [none]

     

    Does my Association_FormURN in workflow.xml need to match the namespace in my InfoPath form's data source?

     

    My Form is browser compatible.  To test this, I've deployed the form to a document library and then configured the form to show in the browser.  The form displays fine.

     

    Here is a warning message I get when running the PostBuildActions.bat file that the Workflow wizard created:

     

    The feature with ID '2c3bd17e-e5e7-4daf-b37f-693f9001b098' is still activated within this farm or stand alone installation. Deactivate this feature in the various locations where it is activated or use -force to force uninstallation of this feature.

     

    I've commented out the form validation stsadm command in the PostBuildActions.bat because it was giving me an error message that my form had not been published (even though I had published it).

     

    Thanks for your help!

     
  • Friday, December 07, 2007 5:28 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    After reading Praveen's post and some of "Pro SharePoint 2007 Development Techniques" from Apress, I found how to fix the problem.  It was the URN in my workflow.xml file.

     

    I fixed my problem by loading my association into InfoPath, selecting the File | Properties... menu option and then copying the URN and pasting it into my workflow.xml.

     

    Thanks Praveen and Apress.

     

    Tim

     
  • Friday, December 14, 2007 6:36 AM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    Sorry, from a long time i was busy, so i didn't check the forms.
    Any way you got the solution.
    nice to know.

    thanks
    -Praveen.
     
  • Friday, December 14, 2007 6:40 AM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    According to Bruce replied,
    the FEATURE.xml file should contains the receiver data [ReceiverAssembly and ReceiverClass] in it.

    if you use the xml [insert snippet], by default it will gives you the default syntax.

    thanks
    -Praveen.

     
  • Friday, December 28, 2007 9:48 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    I am having the same problem with the "The Form has bee closed" when I tried to persist and dump out the stack trace I get this.

     

    Value cannot be null.
    Parameter name: g   at System.Guid..ctor(String g)
       at Microsoft.Office.Workflow.WrkAssocPage.AssociationOnLoad(EventArgs ea)
       at Microsoft.Office.Workflow.CstWrkflIPPage.OnLoad(EventArgs ea)
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

     

    I don't really know what is happening underneath the hoold here. I'm assuming the CSTwrkfllPage or the WrkAssocPage aren't quite working right? can you throw out some suggestions? I already did the usual cheks with the Forms beign browsable. The initial error details say that the form is not browsable, but the stack trace seems to be telling me different. unless there is a corrolation here.

       also, I don't really understand the idea behind 'publishing' the form, why do I have to do that and where do I 'publish' to? when my workflow is deployed, I see that the two forms I'm using are deployed to the 12\TEMPLATE\FEATURE\Workflowname" is that ''published" version??

     

    I am stumped here, any help would be appreciated. thanks

     

    Juan

     
  • Monday, January 21, 2008 12:13 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    Do you found solution? I have the same problem when adding approval workflow to the list:

    Application error when access /_layouts/CstWrkflIP.aspx, Error=Value cannot be null. Parameter name: g 

     
  • Wednesday, January 23, 2008 1:17 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    I had the same problem. Are you sure you add the follwing lines?

     

    ReceiverAssembly="Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

    ReceiverClass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver"

     

     

    Chris

     
  • Thursday, January 31, 2008 10:59 PM
     
     Answered
    Sign In to Vote
    0
    Sign In to Vote
    yes I figured out the problem,
      
        the problem is being caused by the fact that your info path form does not properly install as a viable template, if you look at central admin and look at infopath templates, you will see that your forms are not properly installed. The hosting aspx is basically complaining and saying that it is not receiving anything. I wrote a blog post about it, check it out

    http://juanlarios.blogspot.com/2008/01/workflow-infopath-forms-stuck-on.html


    it's more detailed but it involves publishing the info path form, read it , if you have questions I will reply. 


    regards,

     Juan
     
  • Saturday, February 09, 2008 12:17 AM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    I am having this problem even though I have everything set up properly according to these posts. My Feature.xml has the right receiver classes (since the Snippet had it right).  My form is domain security, browser enabled, my urn is from the published version and correct. All my form has is 3 textareas.

     

    I've followed David Mann's example from Apress Workflow in the Office 2007 System book.  It has everything you guys have been talking about and yet I still get "The form has been closed". It is just 1 form, an association form, the next button is there but when i click it is when I Get the all white screen with it.

     

    At first I got a legitmate InfoPath error box (the first two times I tried to associate the workflow) saying the form could not be open, under details it said "The specified form cannot be found".

     

    After deleting the published, deactivating the feature and rebuilding still nothing changes, however now I just get the white screen, no InfoPath box. I'm really stumped as to what is wrong here.

     
  • Tuesday, February 12, 2008 4:12 PM
     
     Answered
    Sign In to Vote
    0
    Sign In to Vote
    DrNash1111,
     
       check Central Admin, I think it's under Operation Management, and go to your InfoPath Section where it has all the templates. check to see what the status of your infoPath template. 

       If my guess is correct it should not be installed properly and waiting on a "installing" or "pending" state. Let me know if that's the problem.

       that means your infopath form was not installed properly. At least you can trouble shoot a little more targeted after you find that out,

       let me know so I can instruct you further if that is the case.

    JuanL
     
  • Thursday, April 10, 2008 4:13 AM
     
     
    Sign In to Vote
    0
    Sign In to Vote
     JuanL wrote:
    DrNash1111,
     
       check Central Admin, I think it's under Operation Management, and go to your InfoPath Section where it has all the templates. check to see what the status of your infoPath template. 

       If my guess is correct it should not be installed properly and waiting on a "installing" or "pending" state. Let me know if that's the problem.

       that means your infopath form was not installed properly. At least you can trouble shoot a little more targeted after you find that out,

       let me know so I can instruct you further if that is the case.

    JuanL

     

     

    Same problem as Dr. Nash.... I've checked Central Admin page and all of the forms say ready - none stuck in "Installing".

     

    Any other suggestions?

     
  • Wednesday, April 16, 2008 2:53 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

     

    what is the error message that is given through SharePoint? have you changed your web config to dump out Stack trace? that might give you a better understanding of what is happening. Can you post the stack trace dump out that SharePoint provides?

     

    when the form is "closed" there should be an error message in the back. I think that if you change the web config it will dump out the error message.

     

     

    Juan

     
  • Thursday, July 03, 2008 12:58 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote

    hi,

     

    Even i was getting this error. its solved.

     

    Pls check the formUrn of ur form in the workflow.xml and your forms in the

    Central Administration > Application Management > Manage Form Templates

    Go to view properties of your form and check for Form ID: 

     

    These two values are same or not, if not copy this value and place it in workflow.xml.

     

    It should work. 

     

     
  • Monday, July 07, 2008 11:02 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    I am having same issue.  Where is this workflow.xml file you refer to?

     

     
  • Sunday, January 31, 2010 3:48 PM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    If that is an InfoPath Form .

    make sure you don't have a data connection that depend on the View named (ALlItems.aspx )  normally called "All Documents" or " All Items".
    The problem will occur if the view has be changed , removed or customized in a way that the workflow can't pull the required fields.

    You can test this be using the InfoPath Design tools , under data connections, make sure you go through each one of them successfully.

    Good Luck



    -George Gergues
    -SharePoint Architect.



     
  • Wednesday, February 17, 2010 8:32 AM
     
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks shoba..

    This point helped me:These two values are same or not, if not copy this value and place it in workflow.xml (the urn are not same)
     
  • Wednesday, March 03, 2010 10:31 PM
     
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote

    I was encountering the same error message even though the form URN was identical in the InfoPath template and the workflow.xml file. I finally discovered that when the template was published the ID would revert back to the original ID. To fix this, I reset the ID in the InfoPath template and copied it into the workflow.xml file. The moral of the story is do not choose your own template ID!

    • Proposed As Answer by Zubin G Wednesday, March 03, 2010 10:31 PM
    •