The same here…

Uninstall VMWare Tools v12.5.0.24276846 and install an older version.

We installed VMware-tools-12.4.0-23259341-x86_64.exe (https://packages.vmware.com/tools/esx/latest/windows/x64/) and it works again.

In our environment, the server is configured to automatically install the latest version of VMWare Tools. We had to disable this option for the affected servers in our vSphere client so that the version we selected (12.4.0-23259341) would not be updated again.

Best regards,

Gerhard

Same issue here FME 2023.1 b23619

Event Log:

Faulting application name: fmeworkbench.exe, version: 2023.7.47.23619, time stamp: 0x64e967bc
Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726
Exception code: 0xc0000005
Fault offset: 0x0000000000e3696d
Faulting process id: 0x3808
Faulting application start time: 0x01db24eff922bdc1
Faulting application path: C:\Program Files\FME\fmeworkbench.exe
Faulting module path: C:\Windows\SYSTEM32\vm3dgl64.dll
Report Id: d5e27c45-69a0-43aa-b24a-7089f162eb56
Faulting package full name: 
Faulting package-relative application ID: 

VMware tools

12.5.0.24276846

Same issue for us. Can no longer start FME Workbench 2023.1.2

Event log:
Faulting application name: fmeworkbench.exe, version: 2023.7.47.23641, time stamp: 0x654ef1d9
Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726
Exception code: 0xc0000005
Fault offset: 0x0000000000e3696d
Faulting process id: 0x1050
Faulting application start time: 0x01db2516289f1e4e
Faulting application path: C:\Program Files\FME_2023_1_2\fmeworkbench.exe
Faulting module path: C:\Windows\SYSTEM32\vm3dgl64.dll
Report Id: 68ae7abc-d159-41ac-a249-b0f126d34bdc
Faulting package full name: 
Faulting package-relative application ID: 

VMware version 12.5.0.24276846

Same issue with FME version 2022.7.45.22800, time stamp: 0x646d60f8.

Not sure about VMware version

Hi Everyone!

We’ve seen a few reports on this where upgrading to VMware Tools 12.5 is causing FME to fail to launch with a faulting module of vm3dgl64.dll.

To summarize, (and thanks to everyone for sharing their workarounds as well as reporting this issue!) some folks have found workarounds by:

• reverting to VMware Tools 12.4
• OR defining an environment variable SVGA_ALLOW_LLVMPIPE=0 and running FME in the same instance of the command prompt

On a search for this dll crash, Autodesk Forums (external link) suggests either disabling 3D rendering, or uninstalling SVGA if those may be possible for you.

Please give those a try and let me know how it goes as we investigate this issue.

@jovitaatsafe  Thank you for the additional information. Do you have any information on whether the problem is related to the FME or rather VMWare? Depending on which component is causing the problem, we would create a support case with VMWare

Hi @schlomm, I’m not really sure at the moment as we’re still trying to reproduce the behaviour on our side, but it sounds like reports on this crash on vm3dgl64.dll are all occurring on VMware after the update to 12.5.

I think it’d be worth reporting it with VMWare to see if they have any further information. Are any other programs affected for you running on VMware?

Hello @jovitaatsafe ,

The problem is definitely caused by the update to VMWareTool v12.5. The data center has reset the VMWare Tools version to 12.4 for testing purposes and FME can be opened correctly with the older version.
Regarding the question of whether this also occurs with other programs: So far I have not been able to detect this problem with other programs installed on the same host. To test this in more detail, I would need to know which graphics stack FME uses (QT with OpenGL?).

Some additional information I found:

• RStudio has had a similar problem in the past: https://www.icpsr.umich.edu/VDE/pdfs/Rstudio-vm3dgl64.dll-crash.pdf 
• Official information from Broadcom (VMWare Tool Publisher) for an earlier version of VMWare Tools: https://knowledge.broadcom.com/external/article/331541/opengl-dll-is-not-unloaded-on-applicatio.html

At the moment I can't tell if the problem is caused by a faulty vm3dgl64.dll driver or e.g. an outdated usage in FME.

Thanks @schlomm  for sharing your findings! Yes, I believe you’re right on QT and OpenGL.

Bit of an update: Some folks may be aware that we’ve filed a report for development tracked internally as (FMEFORM-32248). The team had a chance to review it and we believe that this may be an issue on VMware’s side as we haven’t made any changes on ours.

We’re waiting to see if VMware will put out anything in their future updates, so please let us know if there’s any update if you have a support case with Broadcom/VMware.

We’re not currently planning to put out any patch, but we’d be happy to work with you further if you’re not able to find a solution, so please let us know!

Hi,

I saw the same issue for FME desktop on VMs. We have FME servers and please let us know if the version of tools will affect FME servers as well.

By the way, we also notice that the 12.5 tools will affect arcgis server print services. We have to downgrade tools to 12.4 to let print service works.

Thanks!

Nick

Is this problem still occurring with FME 2024.2? ​@jovitaatsafe do you have an update on this? 

Hi ​@nick.xu, I’m not aware of any reports with VMware Tools 12.5 affecting FME Server/Flow, so please do let us know if you run into any issues.

Good to know that VMware Tools 12.5 is also affecting ArcGIS Server, thanks for sharing that!

Hi ​@redgeographics,

I just installed FME 2024.2 on VMware with VMware Tools 12.5 and I can confirm there’s no change; FME can’t seem to launch on VMware Tools v12.5.

Some of the previous reports we were getting ranged from FME 2019.x through to 2024.x so the FME version didn’t seem to matter.

Windows Operating System :
---------------------------------------
Click on start --> Search and Open --> Edit the system Environment variables --> Environment Variables

--> System Variable --> New -->  Update below variable and restart --> Open FME to verify 

Variable name : SVGA_ALLOW_LLVMPIPE
Variable Value : 0

I’ll add us to the mix, we got hit over the Thanksgiving weekend, evidently our updates were a bit later.  But it hit my FME VM for FORM, not sure about FLOW yet, it opens, but we are in the process of building out new servers, so no automations or anything set up yet.  But also got both of our ArcGIS Servers with the print breakage.  I will try the variable reset to see if it will work.

Thanks,

Lorinda