Fusion

 View Only
Expand all | Collapse all

Transport (VMDB) error -14: Pipe connection has been broken

  • 1.  Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 04, 2022 08:44 AM

    I have received this message when I try to access the virtual machine on my mac. 

    Transport (VMDB) error -14: Pipe connection has been broken

    I have uninstalled it and reinstalled the machine but the message remains. Does anyone know how to fix this?

    Thanks 



  • 2.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 04, 2022 08:59 AM

    A moderator should move your thread to the area for Fusion now that I have reported it.

     



  • 3.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 04, 2022 12:14 PM

    Host OS Version?  Fusion version?  What guest VM are you trying to load?  Has it run successfully in the past?



  • 4.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 08:23 AM

    Hi,

    I'm using the VMware fusion to run kali linux. It has been working in the past with no issues until now.



  • 5.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 08:28 AM

    Have there been any changes in terms of your Mac, your MacOS version, your Fusion version?

     



  • 6.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 08:31 AM

    Hi,

    Yes my Mac updated recently, but there have been no updates with the VMware.



  • 7.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 08:59 AM

    You still haven't said what Mac you have, what MacOS version you have, what version of Fusion you have...

     



  • 8.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 09:03 AM

    okay sorry, I've attached an image detailing the details of the Mac. The VMware version I am using is the 12.2.3 

    Screenshot 2022-04-05 at 10.00.26.png



  • 9.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 09:10 AM

    Can Fusion start any VMs at all?

    Have you built a new one to try? (it doesn't need to have an OS installed, just a successful power on will be a test)

     



  • 10.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Apr 05, 2022 09:12 AM

    Kali Linux had been working completely fine with issues at all before, but I will try a new VM and see if that works



  • 11.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Jul 23, 2022 07:46 PM

    I had the same problem after my Intel-chip Mac running Monterey 12.4 lost power due to a storm, and my Windows virtual machine wouldn't reload. 

    I filed a Service Request, but after three days the VMWare tech couldn't solve the problem despite his genuine diligent efforts (and my generating two "Problem Report" zip files).  We tried uninstalling and reinstalling Fusion 12.2.4, but to no avail.

    Last night, I updated to Monterey 12.5, and when I rebooted, the problem was gone and my Windows VM loaded without a hitch.

    Hope this works for you.

     



  • 12.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Aug 03, 2022 11:45 PM

    Problem solved. tqvm!

    Thanks RGLLC!


  • 13.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Aug 31, 2022 09:55 PM

    UPDATE

    About a month after my last post about updating to Monterey 12.5, the problem came back with the same error message.

    By that time I had updated to Monterey 12.5.1, although it hadn’t caused any problem at the time nor for several weeks afterward.  

    So I filed another Service Request, and the VMWare representative solved the problem in about 3 minutes.  I asked him what had happened, and he said that there was a missing tmp folder, probably caused by the recent update. 

    I asked him to please outline the steps he took so I can self-help in case the problem returns, and this is what he wrote:  

    -- Checked the tmp folder for the folder named as vmware-[username].

    [Note that he located the tmp folder by using the Mac search function and typing in “/tmp” (without the quotation marks).]

    -- Created the folder with name vmware-[username].

    -- Enabled read and write access for the folder.

    And that was that!  Simple, low tech, and effective.

    I really hopes this helps those forlorn souls who are afflicted with the same problem but have been unable to find any other solution. 



  • 14.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Aug 31, 2022 11:52 PM

    Your "simple and effective" is my "cheap and dirty". That directory should not have to be created manually on a properly configured macOS Monterey system. There's something afoot here as this is the latest in a long line of posts where that solution or something similar has had to be done to fix the specific issue of Fusion being unable to create that directory - leading to this occurrence of the dreaded "Transport (VMDB) error"..

    I'm curious.

    What are the permissions on /tmp (should be a link to /private/tmp) and /private/tmp?

    (use a Terminal shell to find out, not the Finder)

    ls -ald /tmp /private/tmp

    The privileges for /private/tmp on a fresh macOS installation should be rwxrwxrwt with owner root and group wheel.

    My bet is you will find that the permissions for /private/tmp are not what they should be. Which is the real root cause of why Fusion could not create that directory for you like it should have been able to do. If that's the case, fixing that issue is the correct way to address the error.



  • 15.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Sep 01, 2022 08:22 PM

    If that's the case, I really want to know what's causing the permission problem.   Ever since Apple removed 'repair permissions' from disk utility, I've been skeptical about the self-healing the OS supposedly does.



  • 16.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Sep 01, 2022 10:14 PM

    Based on the repeated occurrences but seeming to only affect some people, I'd be inclined to suspect an updater for a third-party application which happens to be installed by the people in question but not by others. There have been known cases of this sort of thing in the past, where an installer or updater messed with permissions on standard folders.



  • 17.  RE: Transport (VMDB) error -14: Pipe connection has been broken

    Posted Sep 01, 2022 10:48 PM

    You're probably right, and I bet it's some sort of EDR, MDM, or other endpoint security tool.