Hi folks,
Another question I’m struggling with I’m afraid.
I’d like to use a network location as my output destination for my workflow, but I’m getting the following error from Workflow when I try to use a mapped drive as the Job Output Folder :
W3001 : Error while executing plugin: HTTP/1.1 500 Internal Server Error LoggedApplicationException: There was an error running the output creation process caused by IOException: Unable to create directory Z:\Planet Press Statements\2018\06\15 (SRV000042)
Create Output: W1603 : Plugin failed - 10:55:09 (elapsed time: 00:00:02:139)
The Z: drive is correctly mapped, and is read / write accessible both to myself and to the planet press service account, so my assumption is that it’s not liking the mapped drive for some reason.
If I try using a full UNC path however, the Next and Finish buttons on the Print Options page of the Output Creation process remain greyed out, and there is the little warning symbol denoting invalid path.
Firstly, should the Designer support full UNC paths for output (e.g. \servername\share\destinationfolder), and if so is there a particular way this needs to be entered? Secondly, is there anything else that the error message above could mean, that I should be looking into?
Many thanks in advance,
Rich
Hi Rich,
Please could you share the screenshot of the Connect screen where you are trying to enter the full UNC path.
Designer supports full UNC paths for output. Please refer to the below link for detailed information about using network drives:
http://help.objectiflune.com/en/planetpress-workflow-user-guide/2018.1/#Workflow/OtherFeatures/NetworkConsiderations.html
Kind Regards,
Meena
Hi Meena,
Thanks for getting back to me. Screenshot hopefully attached below.
All the best,
Rich
Hi Rich,
Thank you for the screenshot. Please could you share the screenshot with the full UNC path you are trying that errors.
Kind Regards,
Meena
Hi Meena,
I’m not sure how or why, but this seems to have resolved itself now - I was putting the UNC path back in to the configuration to provide you with a screenshot, and it seems to happily accept it now, and generate the output where expected. Quite possibly I had a typo in there that I wasn’t picking up on, and simply by re-typing it I’ve solved my own problem!
Many thanks for your response though!
All the best,
Rich
Hi Rich,
That’s great! I’m glad its all sorted. Thank you for the update.
Kind Regards,
Meena
Not sure if I have missed something, but what was the fix?
Hi,
The issue was resolved by itself when Rich tried to input the full UNC path again to get a screenshot.
Kind Regards,
Meena
Hi iBaldie,
Meena is correct - I think I must have made a typo when trying to type in the UNC path, when I tried again later to get a screenshot, it worked just fine.
All the best,
Rich
Hi Rich
Ah ok great thanks, I am having simular issues, unfortunatly mine have not fixed themselves… I have given up with network output with custom variable file names and instead written my own scripts for moving files and renaming them, shame realy as Workflow has the potential but lacks modernisation…
In recent releases of Windows (where recent means Windows Vista, I think), mapped drives were moved from being global (i.e. for every user and program running on the system) to being per-session. Workflow, being a service, runs in session 0, while the logged in user and all of its interactive programs run in session 1 (or 2, or 3…). So drive mappings done by the logged-in user will not be visible by services.
This was done to improve the overall system security and prevent drive letter conflicts between drive mappings done on multiple sessions. There is, I believe, a way to revert to the old behavior but I wouldn’t recommend that.
The “real” fix is to use a script or a batch file in a Workflow startup process to map network shares to drive letters when Workflow starts up. This way, the mappings will become available to Workflow (and other Connect services). Ideally using the same letters as the logged-in user. 