Skip to main content
  • EN

I have an AutoCAD file with many layers and some object data tables (ODT). FME crashes when I try to read it as a Map 3D file. I can't find out what the reason for the crash is, and it reads fine when using a regular AutoCAD reader. When I export out the objects that are just on the layers I need (most of the PR_* layers) I can then read the file as a Map 3D type. I can't tell what is causing FME to crash on the original file. I can't even read the file contents as a Map 3D type.

I don't want to have to export out the needed layers all the time, what if the issue is on the needed layers next time, and I am setting up a Server app for users to use and I can't expect them to create separate files all the time.

My current FME version is 2020.0.0.1 (20200316 - Build 20202 - WIN64), but I was testing an old AutoCAD file for the Server app, and it ran successfully through an older FME version back in February, but can't now.

Can someone tell me what is causing FME to crash so that I can tell users what the issue is when they run across it. Is it something in the AutoCAD file and/or FME version? I have attached a file that is producing crashes, but that ran fine a few months ago.

I'm using 2020.0.2 and it works fine for me. At least, I'm not sure what the data should look like, but it certainly doesn't crash. Interestingly I don't see any updates between your build and mine that would account for a solution.

You could upgrade your FME (if possible) and try it again, to see if there is a better outcome, but I think in this case the best thing is to file a case directly with our support team. That way they can do more rigorous testing and talk to the developers if necessary.

So visit safe.com/support and create a new support case (select "Report a Problem"). I don't think live chat is going to help, since it's likely to need developer intervention if it's truly producing a crash.

Apologies for any inconvenience that this might be causing.

I was able to see the data too:

Maybe an issue with the installation of the software?

Else, I recommend as @mark2atsafe mentioned to create a support case.

I was able to see the data too:

Maybe an issue with the installation of the software?

Else, I recommend as @mark2atsafe mentioned to create a support case.

You were able to read it as Map 3D data? I can read it as a simple AutoCAD file, but not as Map 3D which contains the object data tables.

I was able to see the data too:

Maybe an issue with the installation of the software?

Else, I recommend as @mark2atsafe mentioned to create a support case.

There are other files that I have no problem with, but this file and another are an issue.

I was able to see the data too:

Maybe an issue with the installation of the software?

Else, I recommend as @mark2atsafe mentioned to create a support case.

@dvanriel,

Using FME 2020 and Map 3D this file caused a crash for me too.

Using FME 2018 and Map 3D the data is displayed, but with a lot of warnings like this:

AutoCAD Reader: Found proxy entity of type 'AeccDbNetwork' but proxy graphics were unavailable for this entity. Skipping entity

AutoCAD Reader: Found proxy entity of type 'AeccDbFace' but proxy graphics were unavailable for this entity. Skipping entity

Maybe this helps finding the issue.

Hi @dvanriel,

Thanks for reporting this issue.

It looks like this issue is related to an issue tracked as FMEENGINE-64104 in our system. This should be resolved in Workbench builds 20231+ according to the change log.

Are you able to try the latest build and confirm if that resolves the issue?

Hi @dvanriel,

Thanks for reporting this issue.

It looks like this issue is related to an issue tracked as FMEENGINE-64104 in our system. This should be resolved in Workbench builds 20231+ according to the change log.

Are you able to try the latest build and confirm if that resolves the issue?

I can't upgrade at this time. But the proxy entity reason seems likely the cause of the issue as users are drawing in Civic 3D and such and providing the files without cleaning them up. I hope that when we do have time to upgrade the newer version will resolve the issue.

I can't upgrade at this time. But the proxy entity reason seems likely the cause of the issue as users are drawing in Civic 3D and such and providing the files without cleaning them up. I hope that when we do have time to upgrade the newer version will resolve the issue.

Hi @dvanriel,

Option 2 would be to use a past version of FME to run this workspace/publish to FME Server (assuming FME Server does not experience the same issue). Alternatively, if you know the build number of FME that you were using earlier this year, I'd be happy to track down the installer and put it on our ftp for you to download if it isn't already on the downloads page.

Hope that helps.

Reply


Community Stats

30,194
Posts
114,613
Replies
37,855
Members
Terms & ConditionsCookie settings
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.