Skip to main content
Question

AutoCAD Writer: Failed to open file in method.

  • June 14, 2017
  • 11 replies
  • 144 views
verdoodtdries
Supporter
Forum|alt.badge.img+23

Hello FME Community,

I have a workspace running smoothly on FME Desktop, but as soon as I launch the workspace on FME Server, I'm confronted with an error message like this:

The workspace reads some data from different sources, performs some hocus pocus and finally writes to autocad format. I've replaced the Autocad writer with a simple .txt writer, to ensure the problem is not situated at the writer.

The FME Server account has writing permissions to the folder location I'm trying to populate with some data.

Since I'm creating a new Autocad-file, I'm quite confused with this error message. The file is generated by my workspace, so it can't be opened in another program.

What can be causing this error ?

Has anyone experienced this error before ?

Kind regards,

Dries

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

11 replies

lars_de_vries
Forum|alt.badge.img+10

Hi Dries,

Can it be that workspace is trying to call a template .dwg-file that is not correctly referred to? Maybe the path is not set as a Parameter?

Kind regards,

Lars de Vries

verdoodtdries
Supporter
Forum|alt.badge.img+23
  • verdoodtdriesSupporter
  • Author
  • Supporter
  • June 14, 2017

Hi Dries,

Can it be that workspace is trying to call a template .dwg-file that is not correctly referred to? Maybe the path is not set as a Parameter?

Kind regards,

Lars de Vries

HI lars_de_vries,

 

Thank you for the suggestion. I'm using a template .dwg file but it is correctly refered to and also set as a parameter. This is not causing the error. Kind regards. Dries

 

lars_de_vries
Forum|alt.badge.img+10
HI lars_de_vries,

 

Thank you for the suggestion. I'm using a template .dwg file but it is correctly refered to and also set as a parameter. This is not causing the error. Kind regards. Dries

 

 

Hi Dries, can you relate the .dwg file to a certain parameter and see from that point forward what goes wrong?
mark2atsafe
Safer
Forum|alt.badge.img+59

My best guess is that this is an encoding problem. Is the FME Server machine a different locale or encoding than the Desktop machine? That might be one cause of the problem.

FME Evangelist to the Rich and Famous!!
verdoodtdries
Supporter
Forum|alt.badge.img+23
  • verdoodtdriesSupporter
  • Author
  • Supporter
  • June 15, 2017

My best guess is that this is an encoding problem. Is the FME Server machine a different locale or encoding than the Desktop machine? That might be one cause of the problem.

Mark2AtSafe,

 

Thank you for the suggestion, but both machines use the same locale and encoding.

 

verdoodtdries
Supporter
Forum|alt.badge.img+23
  • verdoodtdriesSupporter
  • Author
  • Supporter
  • June 15, 2017
This problem was not related to the writer format, nor the permissions. I've solved it finally by building the workspace again from scratch by copying the whole workspace in a new one. This ran smoothly.

 

 

 

mark2atsafe
Safer
Forum|alt.badge.img+59
This problem was not related to the writer format, nor the permissions. I've solved it finally by building the workspace again from scratch by copying the whole workspace in a new one. This ran smoothly.

 

 

 

Sad that you would have to do that, but at least it is working now. Perhaps if this happens again you can contact our support team and ask for assistance? http://support.safe.com - then we'll have a formal record of the issue and can get the developers to investigate. Thanks.

 

 

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+59
Mark2AtSafe,

 

Thank you for the suggestion, but both machines use the same locale and encoding.

 

OK. All the cases I could find on our internal systems gave that error in response to an encoding problem, which is why I mention it. But I guess there are many other reasons for it too!

 

 

FME Evangelist to the Rich and Famous!!
F
  • florent
  • May 21, 2019
Sad that you would have to do that, but at least it is working now. Perhaps if this happens again you can contact our support team and ask for assistance? http://support.safe.com - then we'll have a formal record of the issue and can get the developers to investigate. Thanks.

 

 

Hi Mark,

I have exactly the same problem and i don't find any solution. I try to copy all my workspace in a new one but that doesn't work.

How can I solve this problem ?

Do you need my workspace ?

Bests Regards

Florent
mark2atsafe
Safer
Forum|alt.badge.img+59

Hi Mark,

I have exactly the same problem and i don't find any solution. I try to copy all my workspace in a new one but that doesn't work.

How can I solve this problem ?

Do you need my workspace ?

Bests Regards

Florent

Hi Florent,

Can you post this as a new question please? Then it will be easier for everyone to find and help you. Please include as much information as you can, for example the version of FME that you are using.

Thanks

Mark

FME Evangelist to the Rich and Famous!!
F
  • florent
  • May 22, 2019

Hi Mark,

I have exactly the same problem and i don't find any solution. I try to copy all my workspace in a new one but that doesn't work.

How can I solve this problem ?

Do you need my workspace ?

Bests Regards

Florent

We found the problem.

We have a machine with FME Server and a user "FME server". During this week-end the writing rights on the network with the user "FME server" were cancelled.

The problem was resolve with restoring writing rights on the network of the user "FME server"

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.