Skip to main content
Question

Error occurer in function AutoCAD2004writer:WriteInsertAttribute, exception thrown: 'invalid input'


Forum|alt.badge.img

Hi,

 

I´m trying to convert data from a ArcGIS filegeodb to AutoCAD DWG. In the proces I´m getting the following error which says absolutly nothing to me. Does anybody have an idea on where the problem could be?

AutoCAD Writer: An error occurred for dataset 'C:\\Temp\\RF2017\\RFgrundkort2017.dwg', in function AutoCAD2004Writer::writeInsertAttribute. Exception thrown: 'Invalid input' (Invalid input)

Thanks

 

Christian

6 replies

fgiron
Supporter
Forum|alt.badge.img+20
  • Supporter
  • December 20, 2017

Hi Christian,

I've been reported the same error. Have you found any solution since then?

Thanks,

 

Francisco

dmerrick
Contributor
Forum|alt.badge.img+1
  • Contributor
  • November 20, 2018

I was having the same error when converting from a point layer, using the DWGStyler with a template to convert to a block before FeatureWriting it out.

 

In the DWGStyler I had in the Block Name: "Ex Sanitary Manhole" when it should have been "Ex Sanitary Manhole " with a space at the end before writing it to "V-SSWR-STRC".

 

 

 


andreaatsafe
Safer
Forum|alt.badge.img+12
dmerrick wrote:

I was having the same error when converting from a point layer, using the DWGStyler with a template to convert to a block before FeatureWriting it out.

 

In the DWGStyler I had in the Block Name: "Ex Sanitary Manhole" when it should have been "Ex Sanitary Manhole " with a space at the end before writing it to "V-SSWR-STRC".

 

 

 

Hi @dmerrick - glad to hear you were able to resolve the error you received.

 

Do you know if the template DWG file had the Block Name with a space at the end? Or did you have to add the space even though the block name (in the template file) did not have a space at the end?

 

Just want to be sure this isn't a bug with the DWGStyler :)

 

- Andrea

dmerrick
Contributor
Forum|alt.badge.img+1
  • Contributor
  • November 21, 2018
andreaatsafe wrote:

Hi @dmerrick - glad to hear you were able to resolve the error you received.

 

Do you know if the template DWG file had the Block Name with a space at the end? Or did you have to add the space even though the block name (in the template file) did not have a space at the end?

 

Just want to be sure this isn't a bug with the DWGStyler :)

 

- Andrea

@AndreaAtSafe, I was mistaken about my error and having a space at the end of the block name. Further examination showed I was missing a couple "shx." files. I manually copied them into the same folder that the template resides in but still have the same template block issue of it not being recognized.

 


andreaatsafe
Safer
Forum|alt.badge.img+12
dmerrick wrote:

@AndreaAtSafe, I was mistaken about my error and having a space at the end of the block name. Further examination showed I was missing a couple "shx." files. I manually copied them into the same folder that the template resides in but still have the same template block issue of it not being recognized.

 

@dmerrick

 

It sounds like you are still encountering a problem.

 

I think it might be best to post this as a new question on the Q+A board: https://knowledge.safe.com/questions/index.html

 

In your new post, sharing a few more details will help the FME community help you, if you could provide additional details including:
  • A clear statement of the problem you are trying to resolve
  • The version of FME you are using, including build number and edition
  • A small sample of your data, or screenshots of the data in the FME Data Inspector
  • A description of your expected output, with screenshots if possible
  • Your FME workspace
  • Your FME translation log file
  • Any other information that may be useful to share

Forum|alt.badge.img
  • August 13, 2019

Same error but for me the issue was not all template files being in AutoCad version 2013


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings