Did you hardcode any FME Server related parameters?
In addition to this, I've discovered it is adding the 4 characters "\\"\\ prior to the path in the FME_SERVER_REQUESTS_PARAMETERS
Did you hardcode any FME Server related parameters?
No, I haven't. Neither in the workspace before publishing nor do any appear once downloaded from FME Server
In Desktop, is the workspace saved in the same folder as the XML file you are reading? FME might be changing the path because of that.
The other possibility I found is that the first \\ character in the UNC path is being treated as an escape character. Try adding an extra \\ at the beginning and see if that works (which is what I think the "\\"\\ might be trying to do).
Any space characters in the UNC path? If so maybe enclose it in quotes.
I suspect this is a problem we've sorted out for readers and writers, but this transformer might have missed out.
In Desktop, is the workspace saved in the same folder as the XML file you are reading? FME might be changing the path because of that.
The other possibility I found is that the first \\ character in the UNC path is being treated as an escape character. Try adding an extra \\ at the beginning and see if that works (which is what I think the "\\"\\ might be trying to do).
Any space characters in the UNC path? If so maybe enclose it in quotes.
I suspect this is a problem we've sorted out for readers and writers, but this transformer might have missed out.
Hi Mark
No the workspace is saved in a different folder. I have also added the additional \\ and it made no difference.
The UNC paths does have spaces in but has already got quotes round it.
Hi Mark
No the workspace is saved in a different folder. I have also added the additional \\ and it made no difference.
The UNC paths does have spaces in but has already got quotes round it.
Then I think we'll need one of our FME Server experts to weigh in. I'll ask them to take a look.
In addition to this, I've discovered it is adding the 4 characters "\\"\\ prior to the path in the FME_SERVER_REQUESTS_PARAMETERS
Hi @david_whiteside - I've been trying to reproduce this without much luck. Can I ask the build of FME Server and FME Desktop you're using.
Can I also ask how the publish parameter is being populated? i.e., Are you just running the job from the Run Workspace page on FME Server or are you using an FMEServerJobSubmitter or something like that?
Are you able to share a copy of the job's log file with us?
@MattAtSafe
Hi Matt
I have raised a case with your support. Case ID is C133890. This has the workspace, original file and log file attached.
It has been run as both a jobsumbitter from Desktop and as a job from the UI in FME Server