spent a couple of hours running this to the ground.

first we changed permission on /etc/vmware/hostd and files therein, to no effect.

next we uninstalled vmware server 2.0 and cleaned up the OS to remove all remnants thereof. Re-installed vmware server 2.0, and this time chose root as the default administrator (it was previously another user with sudoers privilges). This allowed us to add exactly one (1) user in the permissions tab for the host.

next we edited /etc/vmware/hostd/authorization.xml as described by drossgatech

This fixed it. We can now add as many groups and users in the permissions tab as we desire.

So the bug is that the "add permissions" code seems unable to increment the counter past 11, when it is at 11. Changing the counter to the correct number higher than 11 fixes the problem, and the counter then increments correctly.

my vote is for drossgatech to get credit for the correct answer, and for someone in the Server 2.0 team to have a look at the incrementing code for "new permissions"

I noticed an additional thing here. I was able to add 1 permission and after that, I received the same error message. I then followed the steps from drossgatech but it still didn't work. Then I had a look at the file /etc/vmware/hostd/authorization.xml and noticed that the order in which the entries appeard was: id 11 followed by id 10 and the NextAceId was 11 (I also tried 12 but that didn't work either)

I then swapped the order of the entries so that 10 came first, followed by 11 and set the NextAceId to 12 and that fixed my problem.

Hope this helps the others who were still running into the problem

Greetinx

Johan

Hi guys,

Mattrich is right (way above in the thread) that the only way to get progress on this problem is by bringing it up in the VMware Server forum.