I have the same problem. I hope it am soon repaired.
It would be great if someone at VMWare would reply to this and tell the public if there is a fix coming or not.
I dont know what the offical patch will be but here is a workaround I found translating a German document I found.
edit the line that talks about
incrament it past the current "root" or administrator account you have.
so it now reads
I also deleted
doesnt seem to be used anywhere
and relogged in.
I was then able to add users. Looks like the initial script doesnt incrament well and keeps trying to add you to an existing userid. I dunno why they didnt just use the userid for the users in /etc/password or ldap.
hope that helps
I already found that, however the server falls then with me.
This worked great! Thanks for the help. I used a different Admin so I had to specify the UID for the user I created to be the admin. Very easy fix.
Same problem here. Same fix. Thanks.
Shouldn't this be in the Server 2.0 discussion, and not the VIX API discussion?
what difference does it make where it is being posted as long as it provides a viable solution?
FYI folks - I tried this out and it worked on my setup. Thanks for sharing.
My thanks as well...worked perfectly
I have got the same problem. VUt this was just a missing access right to the vmware files.
Worked perfectly. THANK YOU!
The posted fix that seems to have helped everyone else did not work for me. What worked for me was the following:
My setup is CentOS 5.2, VMware Server 2.0.
On initial config using vmware-config.pl, I specified a user other than root as the administrative user. That user was then unable to add permissions. I ran vmware-config.pl again and specified a different uesr as teh administrative user to no avail. That user could not add permissions. I then ran vmware-config.pl again and specified root as the administrative user. I was then able to login as root through the Web UI and add permissions. It was an unfortunate fix, as I would prefer not to have the root account directly accessible from any remote interface. As such, I then logged in as one of the newly added administrators and removed root's permissions, which prevented root from logging in.
Keep your heels low and center your gravity.
In linux systems the problem is, that vmware-config create the folder /etc/vmware/hostd for user and group root. if you chose another user as administrator for your vmware-enviroment, you won't be able to write into this file, but you need to do, if you want to change and/or add permissions for virtual machines. so the workaround, which works for me and which is still secure, is to give the files in /etc/vmware/hostd group-rights to your administrator-user and allow write-right to the group, e.g. if your administrator-user is "admin" then you should have a group called "admin" (in debian-system this is standard), which one and only member is the user "admin"and change permissions as follows
chgrp admin /etc/vmware/hostd/*
chmod g+w /etc/vmware/hostd/*
Actually you dont need to change permissions for all files, but I'm to lazy to find out, which files will be affected and I want to prevent future permission problems, so I change permissions for the whole directory.
Both entries are used in my authorization.xml
I don't think I will ever approach 100 Roles (AceId) so this is what I used.
As roles are added, they have low numbers and as members are added, they get the high numbers.
I think their terms are not applied correctly.