Maybe try a regular “su” instead of a “su -”
That would change the User path, although I’m not sure if it would be significant.
I can try another test install, but you know that I already did so not that long ago which successfully progressed past the point your install is failing.
TSU
Hi TSU!
Thanks a lot for your persistent support here - and also for offering to repeat the installation on your machine!
As for the latter, I doubt that repeating the installation will help. I have the feeling that this problem is specific
to my configuration - possibly because of the VMware Remote Console, which was installed a few weeks ago.
However, I followed your advice and installed using “su” (not “su -”). Unfortunately this didn’t do the trick.
The error log in /var/log/vmware-installer is exactly the same as before and always:
[2017-10-07 19:22:45,817] Running on a real machine!
[2017-10-07 19:22:53,642] Cannot use vmware-app-control to shut down open VMs, defaulting to fallback message.
[2017-10-07 19:22:53,648] Ignored execution error: [Errno 2] No such file or directory when running command: [path('/etc/init.d/vmware'), 'stoppable']
[2017-10-07 19:22:59,410] This system has KVM enabled. You cannot run VMs with KVM enabled.
[2017-10-07 19:23:00,703] destination /usr/lib/vmware/setup/vmware-config already exists, overwriting.
[2017-10-07 19:23:00,853] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1507396980, fileType 0, and uid 8.
[2017-10-07 19:23:00,854] [vmware-player-setup 14.0.0] Installation failed, rolling back installation.
[2017-10-07 19:23:01,053] Top level exception handler
Traceback (most recent call last):
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/transaction.py", line 430, in RunThreadedTransaction
txn.Run()
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/transaction.py", line 78, in Run
self.get()()
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/common.py", line 138, in Show
i.Execute(txn.temp, onProgress)
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/install.py", line 385, in Execute
db.files.Add(filePath, fileMtime, dest.fileType.id, uid)
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/db.py", line 33, in decorator
raise IntegrityError(unicode(e))
IntegrityError: UNIQUE constraint failed: files.path
[2017-10-07 19:23:01,064] Rollback failed
Traceback (most recent call last):
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/transaction.py", line 478, in RunThreadedTransaction
resolveResults = Resolve(], common.repository.installed, ], db.database)
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/dependency.py", line 1416, in Resolve
positiveGraph.constructLinks(installed)
File "/tmp/vmis.SdYh5C/install/vmware-installer/vmis/core/dependency.py", line 383, in constructLinks
raise exception
UnsatisfiedDependency: Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0
I am now thinking about un-installing the VMRC. Tthis would be less laborious than reinstalling the complete system (which is my/the last ratio).
VMware Remote Console
That is not installed anymore?
Try to install that once more and uninstall it with the Installer.
No, it IS still installed but seems to have an “issue”.
More precisely: When I do execute the following command (after having executed “su -”):
Thales:~ # vmware-installer -u vmware-vmrc
… an error dialog pops up with this message:
Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0
Note: This is the installed - and working - version:
Thales:~ # vmware-installer -l
Product Name Product Version
==================== ====================
vmware-vmrc 10.0.1.5898794
In the meantime I have done the following:
A) Re-installation followed by de-installation of VMRC:
B) Get rid of the “KVM is enabled”-warning :
Looks like I have to consider the Microsoft approach: Re-install the OS 
Try to install the vmware-usbarbitor once more:
As root:
./VMware-Player-14.0.0-6661328.x86_64.bundle -x /tmp/vm
Copy it to /etc/init.d:
cp -v /tmp/vm/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d
Change the rights:
chmod 755 /etc/init.d/vmware-USBArbitrator
Copy the bin:
cp -v /tmp/vm/vmware-usbarbitrator/bin/vmware-usbarbitrator /usr/bin
Restart:
/etc/init.d/vmware-USBArbitrator start
Hi Sauerland,
many thanks to you too!
I did execute all the steps by actually copying and pasting 'em into my shell:
Thales:/home/hardy/Downloads # ./VMware-Player-14.0.0-6661328.x86_64.bundle -x /tmp/vm
Extracting VMware Installer...done.
Thales:/home/hardy/Downloads # cp -v /tmp/vm/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d
'/tmp/vm/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator' -> '/etc/init.d/vmware-USBArbitrator'
Thales:/home/hardy/Downloads # chmod 755 /etc/init.d/vmware-USBArbitrator
Thales:/home/hardy/Downloads # cp -v /tmp/vm/vmware-usbarbitrator/bin/vmware-usbarbitrator /usr/bin
'/tmp/vm/vmware-usbarbitrator/bin/vmware-usbarbitrator' -> '/usr/bin/vmware-usbarbitrator'
Thales:/home/hardy/Downloads # /etc/init.d/vmware-USBArbitrator start
failed
Only the last command failed. The USBArbitrator script returned “failed”…
Continuation:
Even if it doesn’t necessarily make sense, I undid the blacklisting for the kvm modules (kvm and kvm_intel) and
restarted the machine.
Then I tried to start the USBArbitrator again, but unfortunately it returned the very same “failed” error as before…
[FONT=courier new]**Thales:/etc #** /etc/init.d/vmware-USBArbitrator start
failed
[/FONT]
/etc/init.d/vmware-USBArbitrator restart
But can you now delete the vmware-vmrc?
Nope. Same error as always:
**Thales:/etc #** vmware-installer -u vmware-vmrc
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 62: bad alias
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 70: bad alias
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 78: bad alias
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 86: bad alias
...snip like 50 more lines with identical message but other line numbers...
…then I do get a dialog with this error message:
Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0
Later I also tried to “start”/“restart” the USB Arbitrator, same effect, it returns “failed”
According to the vmrc documentation, it’s unusual to install it by itself.
Normally it’s part of, and is invoked using either VSphere client or vRealize Automation.
Have you, or do you still have either of these two other VMware products installed?
Also, up a ways, all you did was to rename the file that was to be overwritten.
That sometimes doesn’t work.
<Move> that file to another temporary location altogether, like /Documents.
Leaving a renamed file in the same directory is not a sure-fire way to disable the file.
TSU
I did download the VMRC from here: https://my.vmware.com/web/vmware/details?downloadGroup=VMRC1001&productId=614
I was referred to that URL by my “VMware ESXi Embedded Host Client” - which is a VMware Flings tool, a browser-based alternative to the (Windows-only) vSphere client.
But to answer your question: No, I don’t have vSphere Client nor vRealize Automation installed on my openSuse 42.3 Leap machine.
With respect to your rename/move suggestion: I did move all files in folder usr/lib/vmware/setup/ into some folder in my /home area (again and again). The installation always did create a new usr/lib/vmware/setup/vmware-config file successfully, but then fails with the next step, when the integrity is tested/checked. Saying this, I have to confess that I have no idea what kind of integrity check this could be and why it fails…
I was able to use version 12.5.7 of Workstation Player with the edited module code. The current version is 14.0.0 and I was able to install that version without issue. The new version of Workstation Player explicitly supports the current version of openSuse. I would suggest starting from there if possible. All I had to do was ‘su’ to root and run the installer (after changing the permission of the installer to run it locally of course).
@f16c
Thanks a lot for your comments!
Unfortunately I have failed to install v12 and v14 in very much the same way. I have tried to install in many different ways, like:
sudo ./VMware-Player-12.5.7-5813279.x86_64.bundle
sudo ./VMware-Player-12.5.7-5813279.x86_64.bundle --console
su -
# ./VMware-Player-12.5.7-5813279.x86_64.bundle
…and some more variantions. Always the same error:
[2017-10-01 18:03:51,017] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1506873830, fileType 0, and uid 8.
[2017-10-01 18:03:51,017] [vmware-player-setup 14.0.0] Installation failed, rolling back installation.
Looks like my system was messed up somehow - possibly by installing VMRC.
I might have to reinstall the complete system in order to get that working…
Don’t post just that error snippet, post or inspect the entire log.
When I inspected my own log, I found numerous minor errors but were actually only warnings… Whatever the error was, it was handled by code.
It’s not possible to know the context of any of your errors and whether any were truly fatal or were handled.
If you’re unable to post the entire log in a Forum post, upload it to a pastebin and provide a link in your Forum post.
TSU
@TSU
Got it, makes sense. Here we go:
[FONT=courier new][2017-10-21 13:43:31,448]
[2017-10-21 13:43:31,462]
[2017-10-21 13:43:31,463] Installer running.
[2017-10-21 13:43:31,463] Command Line Arguments:
[2017-10-21 13:43:31,463] '/tmp/vmis.hgFT7G/install/vmware-installer/vmware-installer.py', '--set-setting', 'vmware-installer', 'libconf', '/tmp/vmis.hgFT7G/install/vmwar
e-installer/lib/libconf', '--install-component', '/tmp/vmis.hgFT7G/install/vmware-installer', '--install-bundle', '/home/hardy/Downloads/./VMware-Player-14.0.0-6661328.x86
_64.bundle', '']
[2017-10-21 13:43:31,646] Successfully loaded GTK libraries.
[2017-10-21 13:43:31,707] Using UI type gtk
[2017-10-21 13:43:31,714] System installer version is: 2.1.0.6502171
[2017-10-21 13:43:31,715] Running installer version is: 2.1.0.6502171
[2017-10-21 13:43:31,715] Opening database file /etc/vmware-installer/database
[2017-10-21 13:43:32,132] Could not locate installer App Control.
[2017-10-21 13:43:32,139] Opening database file /etc/vmware-installer/database
[2017-10-21 13:43:32,308] destination /tmp/tmpENlohR/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-21 13:43:32,369] destination /tmp/tmpENlohR/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-21 13:43:32,406] destination /tmp/tmpENlohR/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-21 13:43:32,429] destination /tmp/tmpENlohR/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-21 13:43:32,451] destination /tmp/tmpENlohR/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-21 13:43:32,481] destination /tmp/tmpENlohR/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-21 13:43:32,547] destination /tmp/tmpENlohR/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-21 13:43:32,574] destination /tmp/tmpENlohR/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-21 13:43:32,601] destination /tmp/tmpENlohR/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-21 13:43:32,620] destination /tmp/tmpENlohR/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-21 13:43:32,944] destination /tmp/tmpENlohR/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-21 13:43:32,978] destination /tmp/tmpENlohR/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-21 13:43:33,000] destination /tmp/tmpENlohR/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-21 13:43:33,051] destination /tmp/tmpENlohR/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-21 13:43:33,074] destination /tmp/tmpENlohR/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-21 13:43:33,336] destination /tmp/tmpENlohR/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-21 13:43:33,401] destination /tmp/tmpENlohR/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-21 13:43:33,419] destination /tmp/tmpENlohR/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-21 13:43:33,442] destination /tmp/tmpENlohR/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-21 13:43:33,487] destination /tmp/tmpENlohR/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-21 13:43:33,853] Not running in a virtual machine.
[2017-10-21 13:43:33,855] Running on a real machine!
[2017-10-21 13:43:43,049] Cannot use vmware-app-control to shut down open VMs, defaulting to fallback message.
[2017-10-21 13:43:43,054] Ignored execution error: [Errno 2] No such file or directory when running command: [path('/etc/init.d/vmware'), 'stoppable']
[2017-10-21 13:43:50,505] This system has KVM enabled. You cannot run VMs with KVM enabled.
[2017-10-21 13:43:51,833] destination /usr/lib/vmware/setup/vmware-config already exists, overwriting.
[2017-10-21 13:43:51,939] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1508586231, fileType 0, and uid 8.
[2017-10-21 13:43:51,939] [vmware-player-setup 14.0.0] Installation failed, rolling back installation.
[2017-10-21 13:43:52,084] Top level exception handler
Traceback (most recent call last):
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 430, in RunThreadedTransaction
txn.Run()
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 78, in Run
self.get()()
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/common.py", line 138, in Show
i.Execute(txn.temp, onProgress)
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/install.py", line 385, in Execute
db.files.Add(filePath, fileMtime, dest.fileType.id, uid)
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/db.py", line 33, in decorator
raise IntegrityError(unicode(e))
IntegrityError: UNIQUE constraint failed: files.path
[2017-10-21 13:43:52,095] Rollback failed
Traceback (most recent call last):
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 478, in RunThreadedTransaction
resolveResults = Resolve(], common.repository.installed, ], db.database)
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/dependency.py", line 1416, in Resolve
positiveGraph.constructLinks(installed)
File "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/dependency.py", line 383, in constructLinks
raise exception
UnsatisfiedDependency: Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0
[/FONT]
Try either of the two following…
Each is a different approach to addressing the same issue about the mysterious KVM module enabled. Based on what has been described, it seems that the vmware installer is throwing a misleading error… The installer is likely detecting that the KVM module is <loaded> although it’s saying that the module is <enabled> which aren’t the same.
So, the following describes unloading the module altogether. You’ll have to reload it after your vmware install if you want KVM support
https://askubuntu.com/questions/373469/how-to-disable-kvm-for-installing-vmware-player
Instead of unloading, you might be able to blacklist the kvm module(s) and then reboot (After which you can test for the modules if you wish). If you can successfully blacklist the kvm modules, then you should be able to run your vmware installer. I’d expect you should be able to remove the blacklisting after the vmware install to restore kvm support if you wish
https://communities.vmware.com/thread/188359
You <may> need to search your system for vmware files and manually remove to provide as clean a system as possible. To do this, I’d recommend using the locate utility (in the mlocate package). If you don’t know or can’t figure out how to use locate, somewhere I’ve posted full instructions in these forums (I’ve actually posted a number of times)
HTH,
TSU
Hi Tony,
I did follow your advice and tried to install again after having unloaded the two running kvm modules
with this command and as sudo:
[FONT=courier new]# rmmod kvm_intel kvm
[/FONT]Then I did execute the installer again:
[FONT=courier new]# ./VMware-Player-14.0.0-6661328.x86_64.bundle
[/FONT]The installation failed again with the well known “Integrity Error”.
The only difference was, that the error logged in /var/log/vmware-installer (see below) does not complain about a running KVM.
[2017-10-31 15:33:41,943]
[2017-10-31 15:33:41,957]
[2017-10-31 15:33:41,957] Installer running.
[2017-10-31 15:33:41,957] Command Line Arguments:
[2017-10-31 15:33:41,957] '/tmp/vmis.iP9te5/install/vmware-installer/vmware-installer.py', '--set-setting', 'vmware-installer', 'libconf', '/tmp/vmis.iP9te5/install/vmwar
e-installer/lib/libconf', '--install-component', '/tmp/vmis.iP9te5/install/vmware-installer', '--install-bundle', '/home/hardy/Downloads/./VMware-Player-14.0.0-6661328.x86
_64.bundle', '']
[2017-10-31 15:33:42,064] Successfully loaded GTK libraries.
[2017-10-31 15:33:42,125] Using UI type gtk
[2017-10-31 15:33:42,132] System installer version is: 2.1.0.6502171
[2017-10-31 15:33:42,132] Running installer version is: 2.1.0.6502171
[2017-10-31 15:33:42,133] Opening database file /etc/vmware-installer/database
[2017-10-31 15:33:42,527] Could not locate installer App Control.
[2017-10-31 15:33:42,534] Opening database file /etc/vmware-installer/database
[2017-10-31 15:33:42,699] destination /tmp/tmpKDIpOX/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-31 15:33:42,754] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-31 15:33:42,789] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-31 15:33:42,822] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-31 15:33:42,844] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-31 15:33:42,863] destination /tmp/tmpKDIpOX/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-31 15:33:42,923] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-31 15:33:42,946] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-31 15:33:43,003] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-31 15:33:43,047] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-31 15:33:43,396] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-31 15:33:43,436] destination /tmp/tmpKDIpOX/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-31 15:33:43,460] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-31 15:33:43,507] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-31 15:33:43,527] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-31 15:33:43,751] destination /tmp/tmpKDIpOX/.installer/14.0.0/__init__.py already exists, overwriting.
[2017-10-31 15:33:43,812] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/update.py already exists, overwriting.
[2017-10-31 15:33:43,835] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/versions.py already exists, overwriting.
[2017-10-31 15:33:43,858] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/systemType.py already exists, overwriting.
[2017-10-31 15:33:43,880] destination /tmp/tmpKDIpOX/.installer/14.0.0/include/initscript.py already exists, overwriting.
[2017-10-31 15:33:44,284] Not running in a virtual machine.
[2017-10-31 15:33:44,286] Running on a real machine!
[2017-10-31 15:33:51,409] Cannot use vmware-app-control to shut down open VMs, defaulting to fallback message.
[2017-10-31 15:33:51,414] Ignored execution error: [Errno 2] No such file or directory when running command: [path('/etc/init.d/vmware'), 'stoppable']
[2017-10-31 15:33:59,441] destination /usr/lib/vmware/setup/vmware-config already exists, overwriting.
[2017-10-31 15:33:59,567] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1509460439, fileType 0, and uid 8.
[2017-10-31 15:33:59,567] [vmware-player-setup 14.0.0] Installation failed, rolling back installation.
[2017-10-31 15:33:59,760] Top level exception handler
Traceback (most recent call last):
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/transaction.py", line 430, in RunThreadedTransaction
txn.Run()
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/transaction.py", line 78, in Run
self.get()()
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/common.py", line 138, in Show
i.Execute(txn.temp, onProgress)
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/install.py", line 385, in Execute
db.files.Add(filePath, fileMtime, dest.fileType.id, uid)
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/db.py", line 33, in decorator
raise IntegrityError(unicode(e))
IntegrityError: UNIQUE constraint failed: files.path
[2017-10-31 15:33:59,772] Rollback failed
Traceback (most recent call last):
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/transaction.py", line 478, in RunThreadedTransaction
resolveResults = Resolve(], common.repository.installed, ], db.database)
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/dependency.py", line 1416, in Resolve
positiveGraph.constructLinks(installed)
File "/tmp/vmis.iP9te5/install/vmware-installer/vmis/core/dependency.py", line 383, in constructLinks
raise exception
UnsatisfiedDependency: Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0
Any idea why the “Integrity Error” reports a UID 8 in this context?
[2017-10-31 15:33:59,567] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1509460439, fileType 0, and** uid 8.**
The Yast “User and Group Administration” tells me that UID 8 is associated with the “Mailer Daemon”…
I have good news today, the installation was successful after all.
Thanks a lot to everybody who contributed to this thread! Especially to tsu2 and Sauerland !!!
The problem seems to be caused by a mutual exclusivity of VMware Player and VMware vmrc …
Briefly:
Then I tried once more to install the VMware Workstation Player v14:
Finally, tried to install vmrc by executing VMware-Remote-Console-10.0.1-5898794.x86_64.bundle, which failed…
However, when I tried to launch the remote console with my “ESXi Embedded Host Client”, it opened the
VMware Workstation Player instead (and not “vmrc”).
All the best!
Hardy
Great news and congrats.
TSU
Ups, just one more information, even if a bit off-topic:
The installed VMware Workstation Player 14.0.0 does NOT work on my old machine
as its CPU “Intel(R) Core™2 Duo CPU E8600 @ 3.33GHz” is unsupported…:’(
(https://docs.vmware.com/en/VMware-Workstation-Pro/14.0.0/rn/workstation-14-release-notes.html)
Looks like I have to go back to VMware Workstation Player v12.5.7.