@san Can you give a little more detail about your workflow, possibly include a sample workspace that reproduces the issue & what version of FME you are using? It looks like you might be using a UUID to create the folder name so I suspect you are trying to do a writer fanout.

Thanks for the reply. I'm trying to convert dxf to geo json through cmd.I,m using guid to create the folder name.And trying to get a json output.But im getting error as :

Cannot create dataset: 'C:\\conversions\\17d5313d-7982-45fb-98c3-a04a0e4a9b92\\tuscs.json' of type Directory, expected a dataset of type Regular file

But when i removed the GUID from the path as below:

C:\\conversions\\tuscs.json

Translation was successful.

What could be the solution for this.

Im using fme : FME 2018.1.0.3 (20180926 - Build 18552 - WIN64).

Sorry i cannot share the workspace due to some restrictions.

I have not been able to reproduce the issue. I've attached an example workspace that uses a dataset fanout expression with a UUID. If you can modify this workspace to reproduce the issue you're encountering then we might be on track to solving it. GeoJSONexample.fmw

Sorry to Res a dead thread, but I ran into this and the text here actually helped me sort it out so I thought I'd elaborate in case anyone else gets this problem and finds this thread with no answer.

In my case I got that error from the writer because it had an incomplete path to the JSON file itself, it was missing the name of the file in the stored writer path, so it was trying to create directory (which already exists) instead of writing to an expected JSON in the directory.

In the OP case, the path C:\\conversions\\17d5313d-7982-45fb-98c3-a04a0e4a9b92\\tuscs.json is most likely being interpreted incorrectly by FME, given that C:\\conversions\\tuscs.json works fine, my guess would be that there is an issue with the "17d5313d-7982-45fb-98c3-a04a0e4a9b92" section of the path. I can't really speculate more than that, but dashes have given me no end of trouble when being passed as text.

Hi @dconran​ ,

It looks like the link to the workspace Mark shared was broken after we migrated community platforms. We just fixed the attachment - can you give the workspace a try to see if that resolves the issue you're experiencing?

Sorry if I was unclear, I have a solution now. I had located this thread through a top hit on google, and since it had no answer here I thought I'd add one. I don't actually require any further assistance. Thanks for the prompt response all the same