Skip to main content

I am working on a process to read in dwg files, parse the text and assign metadata attributes.  I have one file that I am using that had missing xrefs.  Using RealDwg Reader, it worked fine.  But, when I bound the xrefs, it gave me the following error after reading in most of the file:

 

AutoCAD Reader: An error occurred for dataset '<filepath>\FIRESPRINKLER.dwg', in function RealDWGReader::processDimBlockCommon: 'eNullObjectId'
 

I purged and also made a .dxf file, but still got the error.  I am using FME 2023.2.4

Using the regular AutoCAD dwg/dxf Reader, it worked no problem.  I suspect there is some entity in the CAD file that the RealDwg Reader did not like, but after multiple purges and audits, I can’t find anything to delete.  If I am going to publish this Workspace, I need to know if there are things to look for that would help choose the correct reader.  The file is in AutoCAD version 2018.

Questions: 

  • Is this error related to a specific function in RealDwg Reader, or is it just choking on an entity in the file in general?
  • Are there any guidelines about when to use either Reader?
  • Assuming the order of features read were in the same order, the error occurred trying to read a dynamic block. So, I exported the block from the file and inFME2023.2.4:  RealDwg gave me the same error!  The regular AutoCAD Reader had no problem.  In FME 2023.2, the block was read fine by both readers.  I have attached the block that gave the error in the RealDWG Reader.
  • Could there be a bug in FME 2023.2.4 ?

 

I then launched my older FME build, 2023.2, and I was able to read the file with both Real and AutoCAD reader, no problem, but they returned different numbers of features:

From FME 2023.2

Any insight is appreciated.  If it is needed, I can file a bug report.

 

Thanks,

-Loren

 

Hi @larue, this looks like it could be a bug, but we’ll need to take a closer look. Can you please submit a support case with your data? 

As for your second question, this article goes over the 4 AutoCAD formats and might be a good one to take a look at. 🙂 Let me know if you have any questions! 


Hi @saraatsafe ,

Although I indeed got a bunch of errors and crashes, I haven’t been able to replicate them after rebooting.

What I have noticed, regardless of the FME Form build, is that after being in the application for any long stretch of time (4 hours, let’s say), that’s when errors and other weird things start to crop up.  I do purge the cache often but it doesn’t seem to have an effect either way.  I have another machine that doesn’t have the same OS configuration which I will do some testing, when I get a chance.  For now, I can’t properly document this behavior, so will need to get back you.  

Thanks for the interest,

 

@larue 


Hi @larue, thanks for the update! I can’t say I’ve heard of that happening before but do feel free to reach out via support case if you’re able to replicate those errors. It would also be helpful to know what kinds of error messages you’re receiving and what you’re doing with your workspace when they pop up. 

Please let me know if you have any other questions! 

Sara


Reply