Workflow Soluiton

 View Only

  • 1.  Workflow 7.1 upgrade Web.Config errors

    Posted Feb 15, 2012 05:32 PM

    When I unpackage and deploy old projects built in workflow 7.0 on a Workflow 7.1 server it is adding maxRequestLength="2097151" to  <system.web> making it <system.web maxRequestLength="2097151">.  This  causes me to get a HTTP 500.19 error say it can't read config file.  If I remove the maxRequestLength="2097151" from the web.config they open fine in the browser. I test built a project from scratch on the new server and it didn't happen.  So I believe it has something to do with the old projects but I am not sure what.  If I redeploy the maxRequestLength  ="2097151" is readded.  Is there a setting for this that I am missing to keep this from happening?

     

    Workflow Server info

    os= Windows Server 2008 R2 Standard

    IIS=7.5

    Workflow=7.1.1460.1974

     

    HTTP Error 500.19 - Internal Server Error

    The requested page cannot be accessed because the related configuration data for the page is invalid.

    Module IIS Web Core
    Notification BeginRequest
    Handler Not yet determined
    Error Code 0x8007000d
    Config Error Unrecognized attribute 'maxRequestLength'
    Config File \\?\C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\AbortProcess\web.config


  • 2.  RE: Workflow 7.1 upgrade Web.Config errors

    Posted Feb 16, 2012 05:28 AM

    The issue is the attribute maxRequestLength is incorrectly placed into system.web node of web.config file instead of httpRuntime node.
    I've checked the behavior of the publishing service in Workflow 7.1 SP2 to verify your problem.
    You are right - this issue is reproducible.
    I've discovered how it works and it seems to be a bug.

    When the publishing service adds an Ajax support to web.config file it looks for the httpRuntime node. If it found the node, it tries to move to the useFullyQualifiedRedirectUrl attribute. If this attribute exists, it is set to true. If the attribute doesn't exist, it is added. Then the service goes back to parent node i.e. httpRuntime and tries to move to maxRequestLength attribute and respectively sets it or adds it.
    The problem is when the httpRuntime node has no the useFullyQualifiedRedirectUrl attribute at all the service even then goes back to parent node (!) and in such case it will be a system.web node and it adds maxRequestLength attribute exactly to this node!



  • 3.  RE: Workflow 7.1 upgrade Web.Config errors

    Posted Feb 16, 2012 07:00 AM

    I've put this in as a bug. We'll get it addressed immediately.



  • 4.  RE: Workflow 7.1 upgrade Web.Config errors

    Posted Feb 16, 2012 10:45 AM

    Thank you for investigating this.



  • 5.  RE: Workflow 7.1 upgrade Web.Config errors

    Posted Feb 21, 2012 01:30 PM

    Is there any way to know when this change will be addressed?



  • 6.  RE: Workflow 7.1 upgrade Web.Config errors

    Posted Feb 21, 2012 03:00 PM

    This has been fixed in the trunk of our codebase, so it should be fixed before our next official release. If there's enough of a need, we can push it down to our rollups.

    The fix was basically to reset to where you were at httpRuntime vs. using a MoveToParent