Workflow Soluiton

 View Only
  • 1.  Issue with Source File Component

    Posted Apr 18, 2016 10:17 AM

    Hi,

    I'm using the "Source" and "Copy Files" components to move some files around on an existing web server. I've tested it in debug and everything works fine. However, when i publish the project, i'm getting an error. It's saying that it can't find the file path. Am I missing something? What's the difference between running it in debug mode and running the published version?



  • 2.  RE: Issue with Source File Component

    Posted Apr 18, 2016 10:27 AM
    Debug = your user permissions Published = application pool identity permissions Ensure the application pool service account has proper directory permissions.


  • 3.  RE: Issue with Source File Component

    Posted Apr 18, 2016 10:28 AM

    Ah, ok let me check. Thank you



  • 4.  RE: Issue with Source File Component

    Posted Apr 18, 2016 10:57 AM

    what would the application service account be called? I'm trying to grant it access now



  • 5.  RE: Issue with Source File Component
    Best Answer

    Posted Apr 18, 2016 11:02 AM

    go into your IIS manager on the Workflow server, and expand your server at the top-left

    click on Applications Pools

    on the right, you should see all your applications pools, and the Identity they're using

    you may see some like ApplicationPoolIdentity; these should be configured as actual service accounts instead of the built-in defaults like this.  for example, "ProcessManagerPool" is likely your default that's being used by Workflow, or perhaps the "DefaultAppPool".  right-click on the proper application pool and select Advanced Settings.  "Identity" can be found in the third section. click in the right field and click the ellipsis (...), and choose Custom account, and "Set..."  this will allow you to set a specific service account to which you've given the proper rights to access the directories you're attempting to manage via Workflow.



  • 6.  RE: Issue with Source File Component

    Posted Apr 18, 2016 11:34 AM

    awesome, thank you