Workflow and ServiceDesk Community

 View Only

  • 1.  Workflow debugging using IIS

    Posted Jan 04, 2011 07:42 AM

    Hi,

     

    I'm trying to figure out how to use IIS for debugging.
     
    I enable it in the Tool preferences and check "Sticky directory" and I have enabled Windows authentication in IIS and web.conf for the project.
     
    First of all the virtual directory for the application is not created automatically when I start debugging.
     
    Also, it seems like the debugger always attaches anonynmously as I get a 401 Unauthorized error from IIS unless I enable "anonymous access".
     
     
    Can anyone give me some pointers as the documentation is sort of lacking.
     
    Thanks,
     
    Rickard


  • 2.  RE: Workflow debugging using IIS

    Posted Jan 04, 2011 03:04 PM

    Are you trying to debug IIS or a Workflow project, I'm not quite following your post.

    And are you referring to the "Sticky Debug URLs" checkbox in the Debugging section (in the Tools Preferences)?



  • 3.  RE: Workflow debugging using IIS

    Posted Jan 07, 2011 01:55 PM

    I am having the same problem. This only seems to happen when I am using any kind of Active Directory functionality. My debug tool preference is set to IIS, web.config in the workflow is set to Windows, my Get Current User component is set to HttpContext, IIS Debug_ application pool Directory Security Authentication is set to Integrated Windows. Is there something I am missing? I currently have to re-deploy the project any time I want to test which is really frustrating. I am not really sure if the "Stickey Debug URLs" property has anything to do with this. Any assistance would be greatly appreciated.

     

    Thanks,

    Tom



  • 4.  RE: Workflow debugging using IIS

    Posted Jan 07, 2011 09:40 PM

    I got it working by:

    Follow the steps at https://www-secure.symantec.com/connect/forums/issues-auto-start-workflows

    Set the Get User Name component as WindowsPrincipal

    Had to change the anonymous access account to the domain account



  • 5.  RE: Workflow debugging using IIS

    Posted Jan 08, 2011 01:19 PM
    Just realised that Setting the anonymous account would be a "bad" choice


  • 6.  RE: Workflow debugging using IIS

    Posted Jan 11, 2011 01:53 PM

    Thank you for your input, AngelD. I agree. I definitely don't want to set the domain admin as the Anonymous Account. I was able to get my Debug working again by setting the Debugging Web Server back to Internal Web Server and the Get Current User component to WindowsPrincipal. This doesn't solve or answer the question on how to debug in IIS, and with this method I will have to switch the Get Current User component from WindowsPrincipal to HttpContext to deploy, and back to debug. But, it allows me to actually debug now so I can live with having to make that change. I would still be curious as to how you would go about actually debugging in IIS and not the Internal Web Server and still be able to debug without getting having to switch the User Name Type and/or changing the Debugging method.



  • 7.  RE: Workflow debugging using IIS

    Posted Jan 12, 2011 02:53 PM

    What I do is disable the Get Current User compnent, and in the output mapping I put in the DOMAIN\Username credentials. I just have to remember to re-enable it.  This has the added benefit of allowing me to test as any user.

    As far as I know, there is no way around this as the debugger using IIS on your local computer will not get the HTTP context.

     

    rob