Skip to main content
Question

FME 2019.0.1 Data Inspector won't handle 3D geometries?

takashi
Influencer

After upgrading FME Desktop 64-bit on Windows 10 to the latest version 2019.0.1 build 19253, FME Data Inspector became not to handle any 3D geometries.

If a workspace contains an Inspector and you send 3D features to it, Data Inspecector once opens but then closes automatically without displaying the translation result. If the Visual Preview was active, Workbench would close silently after the translation finished.

Reinstalled FME 2019.0.1 twice, but the symptom still appears.

Have you observed such a symptom?

15 replies

takashi
Influencer
  • takashiInfluencer
  • Author
  • May 14, 2019

Isn't there anyone who encountered the same symptom?

cyrusa
Contributor
Forum|alt.badge.img+3
  • cyrusaContributor
  • Contributor
  • May 14, 2019

Hi Takashi,

I encountered the same problem (two weeks ago) a couple of times with 3D points and lines. In 'graphics view' and 'Data inspector'. Today I tried to reproduce the same but it showed my data (I didn't update)

FME(R) 2019.0.0.0 (20190308 - Build 19224 - WIN64)

takashi
Influencer
  • takashiInfluencer
  • Author
  • May 14, 2019
cyrusa wrote:

Hi Takashi,

I encountered the same problem (two weeks ago) a couple of times with 3D points and lines. In 'graphics view' and 'Data inspector'. Today I tried to reproduce the same but it showed my data (I didn't update)

FME(R) 2019.0.0.0 (20190308 - Build 19224 - WIN64)

Thanks for your response. I would like to know whether the symptom appears for only a few users in a specific environment or is a general issue which many users could encounter.

My environment:

  • FME 2019.0.1 build 19253 64bit
  • Windows 10 Pro

The issue won't appear with 32bit version FME 2019.0.1.

david_r
Celebrity
  • david_rCelebrity
  • May 14, 2019
takashi wrote:

Isn't there anyone who encountered the same symptom?

I don't have many 3D datasets handy, but if you have a small sample dataset I'd be glad to test here on my end.

takashi
Influencer
  • takashiInfluencer
  • Author
  • May 14, 2019
takashi wrote:

Isn't there anyone who encountered the same symptom?

Thanks @david_r, it's quite easy to reproduce the issue in my machine. Try this workspace.

b19253-data-inspector-3d-issue.fmw

david_r
Celebrity
  • david_rCelebrity
  • May 14, 2019

I just tested with FME 2019.0.1.0 (20190506 - Build 19253 - WIN64) on Windows 10 build 17134, both with the Inspector and the Visual Preview. I had no issues.

takashi
Influencer
  • takashiInfluencer
  • Author
  • May 15, 2019
david_r wrote:

I just tested with FME 2019.0.1.0 (20190506 - Build 19253 - WIN64) on Windows 10 build 17134, both with the Inspector and the Visual Preview. I had no issues.

Thanks for your testing. In my environment the symptom still appears unfortunately...

nielsgerrits
VIP
Forum|alt.badge.img+54
takashi wrote:

Thanks @david_r, it's quite easy to reproduce the issue in my machine. Try this workspace.

b19253-data-inspector-3d-issue.fmw

Tested with no issues.

FME(R) 2019.0.1.0 (20190506 - Build 19253 - WIN64) in Windows 7

jovitaatsafe
Safer
Forum|alt.badge.img+11

Hi @takashi,

I was working on a Data Inspector crash case recently to do with viewing 3D data, and their case resolved when they removed their old graphics card. The faulting dll was one that belonged to their graphics card.

Would you be able to share a screenshot of your Windows Event Viewer on the crash event? And if anyone else is experiencing this issue, if you could please share your crash event as well. If you don't want to share the screenshot publicly, please feel free to email it to and just add my name to the email subject. I'll be sure to post back here when a resolution is found if this goes into a new case.

takashi
Influencer
  • takashiInfluencer
  • Author
  • May 16, 2019
jovitaatsafe wrote:

Hi @takashi,

I was working on a Data Inspector crash case recently to do with viewing 3D data, and their case resolved when they removed their old graphics card. The faulting dll was one that belonged to their graphics card. 

Would you be able to share a screenshot of your Windows Event Viewer on the crash event? And if anyone else is experiencing this issue, if you could please share your crash event as well. If you don't want to share the screenshot publicly, please feel free to email it to  and just add my name to the email subject. I'll be sure to post back here when a resolution is found if this goes into a new case. 

Hi @jovitaatsafe, thanks for your response. The first two are events on FME Data Inspector crash.

0684Q00000ArMfbQAF.png

?????:         Application
???:           Application Error
??:            2019/05/16 9:36:09
???? ID:       1000
????????:      (100)
???:           ???
?????:         ?????
????:          N/A
???????:       PSS-IIJIMA-01
??:
??????????????????: fmedatainspector.exe??????: 2019.7.36.19253???? ????: 0x5cd0fa07
???????????????: ig9icd64.dll??????: 23.20.16.4849???? ????: 0x59f375c0
?????: 0xc0000005
???????: 0x000000000060fc1d
????????????? ID: 0x25ac
??????????????????????: 0x01d50b7f543110b3
????????????????? ??: C:\Program Files\FME 2019.0\fmedatainspector.exe
?????????????? ??: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll
???? ID: af97ee18-a1b5-45bd-b0cc-dbbc4d8326e7
????????????????????: 
??????????????????????????? ID: 
???? XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-05-16T00:36:09.202209200Z" />
    <EventRecordID>66525</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PSS-IIJIMA-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fmedatainspector.exe</Data>
    <Data>2019.7.36.19253</Data>
    <Data>5cd0fa07</Data>
    <Data>ig9icd64.dll</Data>
    <Data>23.20.16.4849</Data>
    <Data>59f375c0</Data>
    <Data>c0000005</Data>
    <Data>000000000060fc1d</Data>
    <Data>25ac</Data>
    <Data>01d50b7f543110b3</Data>
    <Data>C:\Program Files\FME 2019.0\fmedatainspector.exe</Data>
    <Data>C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll</Data>
    <Data>af97ee18-a1b5-45bd-b0cc-dbbc4d8326e7</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
takashi
Influencer
  • takashiInfluencer
  • Author
  • May 16, 2019
jovitaatsafe wrote:

Hi @takashi,

I was working on a Data Inspector crash case recently to do with viewing 3D data, and their case resolved when they removed their old graphics card. The faulting dll was one that belonged to their graphics card.

Would you be able to share a screenshot of your Windows Event Viewer on the crash event? And if anyone else is experiencing this issue, if you could please share your crash event as well. If you don't want to share the screenshot publicly, please feel free to email it to and just add my name to the email subject. I'll be sure to post back here when a resolution is found if this goes into a new case.

Hi @jovitaatsafe, according to @andreaatsafe's suggestion, I updated the graphics driver to the latest version, then the problem has been resolved!

This Intel site was helpful: Downloads for Graphics Drivers

Thanks for your support.

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

Hi @jovitaatsafe, according to @andreaatsafe's suggestion, I updated the graphics driver to the latest version, then the problem has been resolved!

This Intel site was helpful: Downloads for Graphics Drivers

Thanks for your support.

@takashi So happy to hear that this resolved the issue!

Thanks for letting us know :)

- Andrea

jovitaatsafe
Safer
Forum|alt.badge.img+11
takashi wrote:

Hi @jovitaatsafe, according to @andreaatsafe's suggestion, I updated the graphics driver to the latest version, then the problem has been resolved!

This Intel site was helpful: Downloads for Graphics Drivers

Thanks for your support.

Glad to hear it! Thanks for sharing the resource @takashi!

I
  • igadget
  • July 4, 2019

Hi,

I'm experiencing this with FME 2019.1.0.0 (20190627 - Build 19601 - WIN64)

Opening Inspector from Workbench > Tools > FME Data Inspector... works fine but if I try with a simple Creator (no geometry) and an Inspector it crashes...

Here's the windows event report:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
        <Provider Name="Application Error" /> 
        <EventID Qualifiers="0">1000</EventID> 
        <Level>2</Level> 
        <Task>100</Task> 
        <Keywords>0x80000000000000</Keywords> 
        <TimeCreated SystemTime="2019-07-04T11:20:48.527323100Z" /> 
        <EventRecordID>30008</EventRecordID> 
        <Channel>Application</Channel> 
        <Computer>Computer</Computer> 
        <Security /> 
    </System>
    <EventData>
        <Data>fmedatainspector.exe</Data> 
        <Data>2019.7.37.19601</Data> 
        <Data>5d166e79</Data> 
        <Data>Qt5Gui_fme.dll</Data> 
        <Data>5.12.3.0</Data> 
        <Data>5cffd2fc</Data> 
        <Data>c00000fd</Data> 
        <Data>000000000010a0ac</Data> 
        <Data>29d0</Data> 
        <Data>01d5325a7d332433</Data> 
        <Data>C:\Program Files\FME\FME20191\fmedatainspector.exe</Data> 
        <Data>C:\Program Files\FME\FME20191\Qt5Gui_fme.dll</Data> 
        <Data>57f4083e-ac23-4143-b1f7-79c01cca4368</Data> 
        <Data /> 
        <Data /> 
    </EventData>
</Event>

I have 2018.1 in the same computer and everything works fine with it.

jovitaatsafe
Safer
Forum|alt.badge.img+11
igadget wrote:

Hi,

I'm experiencing this with FME 2019.1.0.0 (20190627 - Build 19601 - WIN64)

Opening Inspector from Workbench > Tools > FME Data Inspector... works fine but if I try with a simple Creator (no geometry) and an Inspector it crashes...

Here's the windows event report:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
        <Provider Name="Application Error" /> 
        <EventID Qualifiers="0">1000</EventID> 
        <Level>2</Level> 
        <Task>100</Task> 
        <Keywords>0x80000000000000</Keywords> 
        <TimeCreated SystemTime="2019-07-04T11:20:48.527323100Z" /> 
        <EventRecordID>30008</EventRecordID> 
        <Channel>Application</Channel> 
        <Computer>Computer</Computer> 
        <Security /> 
    </System>
    <EventData>
        <Data>fmedatainspector.exe</Data> 
        <Data>2019.7.37.19601</Data> 
        <Data>5d166e79</Data> 
        <Data>Qt5Gui_fme.dll</Data> 
        <Data>5.12.3.0</Data> 
        <Data>5cffd2fc</Data> 
        <Data>c00000fd</Data> 
        <Data>000000000010a0ac</Data> 
        <Data>29d0</Data> 
        <Data>01d5325a7d332433</Data> 
        <Data>C:\Program Files\FME\FME20191\fmedatainspector.exe</Data> 
        <Data>C:\Program Files\FME\FME20191\Qt5Gui_fme.dll</Data> 
        <Data>57f4083e-ac23-4143-b1f7-79c01cca4368</Data> 
        <Data /> 
        <Data /> 
    </EventData>
</Event>

I have 2018.1 in the same computer and everything works fine with it.

Hi @inspecteurgadge,

Sorry to hear that you've run into this. Would you be able to ensure that your graphics card is up to date? You can check if it needs to be updated in the Windows Device Manager and selecting Display Adapters. There's also a resource for Intel graphics driver downloads that takashi shared above. 

 

 

The second thing I would need to investigate further on the issue is a system information report. Would you be able to run the system_information.bat file from this troubleshooting article and send me the FME Report? You can send it to  or go through this web form to report a case (or let me know if you already have a case), and just include my name somewhere in the subject line. Thanks!

Reply


Helpful Members This Week

Community Stats

31,287
Posts
118,664
Replies
38,875
Members

Latest FME

Terms & ConditionsCookie settings

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
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.