Expedition Fusion remote exception

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Expedition Fusion remote exception

L2 Linker

Does anyone have an idea as to why I get a "remote exception" error when running Expedition on Fusion?


I also noticed the Jobs and Task Manager won't start.






L2 Linker

I fixed this issue by running "sudo apt-get dist-upgrade".

If I understand correctly, it doesn't seem to be related to VMWare Fusion version of Expedition, but some interal state of the Ubuntu virtual machine, that got fixed through the update.


So, this seemed to be a OS/package corrupted filesystem issue, not that much related to Expedition of Fusion. Does it make sense?

That makes sense. I suspected it was an issue with Fusion because there was a different solution to fixing the errors when it was loaded on ESXi. In that case we had to convert it with the OVF tool before loading it on ESXi. I haven't tried installing it on Workstation or Player yet.

I'm still having this issue after doing the sudo apt-get dist-upgrade. I  convert it with VMware Workstation to an ovf before loading it on ESX. 

Any tips for me on how to get his fixed?


Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!