To fix it, either reboot, or alternatively this should work: Error: /Applications/VMware Fusion.app/Contents/Library/vmnet-bridge is already running, process ID: 2852 VMware Fusion 2235595: Error: Unable to start the bridge services. When you restart Fusion, it does try to start those processes again under its own control, but it notices they're already running and stops trying, and Fusion ends up in this state where network services are in fact running, but the settings to control them are unavailable.Īs a symptom of this issue, you can check system.log in Console and you may notice messages like: When that happens, Fusion can be restarted, network adapters removed and added again, but it still won't help because from Fusion's perspective, it has no control over low level network settings through those processes, so the settings are shown as being unavailable for editing. I believe this happens because one or more of the low level processes that manage networking for Fusion (the vmnet-* processes) gets stuck or Fusion is otherwise unable to communicate with them. I also wonder if it has anything to do with Cisco Any Connect client that I have - this has carried over from the update from 10.9 to 10.10 - and when I connected to the VPN there was an auto update - though this may not be related at all. The log did reflect that vmnet-bridge is already running. Ive tried stopping and starting the services. It seems as though just the networking element of fusion is broken - all VMs work fine - I just can change VM settings, or add new VMs due to the same issue. I figured it was a problem just for this VM, but no, all the VMs have the sam issue!Īlso when I go to the Fusion preferences, and go to the network tab - all this is greyed out too. It took me many frustrating hours to figure that out.I have done a upgrade to 10.10 and Fusion 7Įverything has been fine, and I created a new custom vmnet, and some VMS - almost had everything working.ĭuring the third VM that I made, I realised I needed to change the network so it was in the same vmnet.Īnyway, in the settings for the network its all greyed out - but all other settings for the VM are fine. I don't understand how Microsoft justifies changing those settings on foreign computers (which are not part of the Windows Domain) just by logging in to Microsoft 365. Macros settings are enabled again and you can change them. What I had to do was change the active account in the Office Program (you can do this in Word or Excel but not Outlook - at least I couldn't find a way) and then restart the application. When I (re)started Outlook, Excel or Word macros were disabled and the settings greyed out. I was not aware that you can set/overrule local Office settings with Microsft 365 account settings.Īnyway, every time I opened a customer SharePoint document - my active account in Office changed to my customer's 365 account. The one from my company does not have those restrictions. The customer one has strict settings set in Microsoft 365 to disable Macros. One from my company and one from one of my customers. Basically, I am using 2 Microsoft 365 accounts. I was able to figure out what was going on. In case someone else runs into the same issue:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |