WGM problem cannot create new users
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Trying to add a new user to OD via WGM 10.5.3, I gets error
Error of type eDSRecordAlreadyExists (-14135) on line 1189 of /SourceCache/WorkgroupManager/WorkgroupManager-319.1.1/PMMUGMainView.mm
All preexisting users work fine.
11 replies
Sign in or join Beachball Help to reply.
- 0
Camelot ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
eDSRecordAlreadyExists
This means there's already a record (account) in the directory with the same details as the one you're trying to add.
Do you get this with a specific username, or does it happen for any username?
If it's just this username then either you've already done what you're trying to do (add this user), or you have two users with the same name (so someone's going to have to get a different name).
If it's any username then you may have some corruption in your Open Directory, which is going to take some time to work out. - 0
Jean-Luc. Mounier ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Camelot wrote:
Do you get this with a specific username, or does it happen for any username?I've got it before I can type a username. I've got it just after I click on the New user icon !
Message was edited by: Jean-Luc. Mounier
- 0
Antonio Rocco ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi
Your Rider states:
+*10.3 Server upgraded to 10.4 Server upgraded to 10.5*+
This, more than likely, is the cause of your problem. There are problems when upgrading to 10.5 especially if its an OD Master. Apple extended the LDAP Schema fairly extensively from 10.3 when 10.4 was released. DNS and Kerberos are also key players in Open Directory creation more so than they were in 10.3. In fact you could have a 10.3 OD Master without Kerberos and DNS, although it worked better if you did.
The impact was slightly minimised when upgrading from 10.3 to 10.4. Further changes for 10.5 have probably caused this accommodation from 10.3 to 10.4 to break. One reason could be because GUIDs for user accounts in 10.3 don't translate too well to 10.5. Kerberos authentication can get confused and user accounts GUIDs tend to be mapped to the LKDC rather than the OD KDC.
If you want a 10.5 OD Master it would be better if you started with a clean install and used a restored LDAP database - provided everything has stayed the same in terms of IP address and domain name, you should be OK. Or import an exported Users and Groups list and re-define passwords or use a password policy to force users to change the passwords themselves. Although even this can cause problems. Unshare the sharepoint used for home folder creation first as well as un-automounting it.
Your other option is to wait until someone posts with a possible solution. Ultimately only you can decide what your best options are.
Tony
- 0
Jean-Luc. Mounier ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Antonio Rocco wrote:
HiHi
Your Rider states:
+*10.3 Server upgraded to 10.4 Server upgraded to 10.5*+
This, more than likely, is the cause of your problem.
I know but it has worked for several month in 10.4 and also in 10.5 without any problem.
There are problems when upgrading to 10.5 especially if its an OD Master. Apple extended the LDAP Schema fairly extensively from 10.3 when 10.4 was released.
Yes, the schema changed was between 10.3.8 and 10.3.9 and it works fine for me.
DNS and Kerberos are also key players in Open Directory creation more so than they were in 10.3. In fact you could have a 10.3 OD Master without Kerberos and DNS, although it worked better if you did.
DNS is on another clean linux server.
Services have been Kerberized in 10.4 and all is Ok.The impact was slightly minimised when upgrading from 10.3 to 10.4. Further changes for 10.5 have probably caused this accommodation from 10.3 to 10.4 to break. One reason could be because GUIDs for user accounts in 10.3 don't translate too well to 10.5.
For most of the users, I change the default GUID.
It has works for many month in every version of 10.4 up to 10.4.11. It has also worked for many month in 10.5.Kerberos authentication can get confused and user accounts GUIDs tend to be mapped to the LKDC rather than the OD KDC.
If you want a 10.5 OD Master it would be better if you started with a clean install and used a restored LDAP database - provided everything has stayed the same in terms of IP address and domain name, you should be OK.
I know that my LDAP is corrupt. It has been corrupted by a Workgroup Manager or a Server Admin program. If I dump the configuration and restore it on the same machine with Server Admin, the user list is empty ! and the log files tells me :
Error: command failed with exit code 256: /usr/sbin/slapadd -c -l /tmp/slapconfig_stage2023WJmgjh/backup2023.ldifOr import an exported Users and Groups list and re-define passwords or use a password policy to force users to change the passwords themselves.
Only a few user are MacOS users. Most of them are linux users, windows users, web users so they cannot change the password at first login.
What I'm looking for are some commands that can show me where is the corruption and manually correct it.
It is very difficult to do these changes because the server used every days and I can only test on week-ends. - 0
wstrucke ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am getting this same error when I try to add a group in workgroup manager -- this worked fine when I was using server admin tools version 10.5.3. I just updated to 10.5.5 today and now the second I click "New Group" i get the eDSRecordAlreadyExists error. This is, for obvious reasons, quite a predicament. I have already tried trashing my workgroup manager prefs but that has not made a difference.
My workstation is running 10.5.5 and the server is 10.5.5. It was a fresh install of 10.5.0 with an imported directory archived from 10.4.11.
- 0
Jean-Luc. Mounier ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
In my last test, Workgroup Manager 10.5.3 works and Workgroup Manager 10.5.5 does not with :
Error of type eDSRecordAlreadyExists (-14135) on line 1189 of /SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/PMMUGMainView.mmCan somebody tell us what have been changed near line 1189 between the two versions ?
- 0
Edward Westerhout ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Got the same problem. I'm unable to ad/recreate some groupnames in WGM. Groupname doesn't exist in WGM but is available in de SA groups-window. Your not able to re-use the old name again in de WGM because the SA (or something else) isn't able to delete this old entries.
Help is welcome... It's very disturbing getting old inactive groups in the SA filesharing window and having to use new naming for them.
Somebody knows a solution? It's more than welcome.
- 0
Jim Boree ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Would just like to add myself as someone affected by this. A re-install isnt an option - our students are in the middle of their exams and we cant afford any disruptions. Whats going on?
- 0
tallstrider ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same issue here for both Users & groups
Are there any good utilities to check and repair
users & groups for 10.5 Server?I get errors like:
"You can't assign the same name "GroupName" to 2 different groups.
Remember that names are not case-sensative when checking for conflicts.""Error of type eDSRecordAlreadyExists (-14135) on
line 1189 of /SourceCache/WorkGroupManager/WorkGroupManager-319.2.2/
PMMUGMainView.mm""Error of type EDSSchemaError (-14142) on line 649
of /SourceCache/WorkGroupManager/WorkGroupManager-319.2.2/
Plugins/GroupAccounts/GroupBasicPluginView.mm"frankly - I'm no longer tooting the horn about Apple's
new 10.5 Server nor their support of it.Chris
- 0
jasonpvp ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
We have the same and similar problem also. We upgraded from 10.3 to 10.4 to 10.5, which did compound the issues. Due to corruption, we couldn't even archive the directory after this. To try to fix it, we started with a clean 10.5.6 install and rebuilt the directory from a slapcat export. (Since we were storing passwords with reversible encryption, we were able to migrate the password database intact) This left us with most of the same problems, except we can at least archive, now, and it runs faster. The server still locks up periodically, however.
There are only two points I can mention that showed a little promise, but which we haven't fully explored yet.
1) Our installation was generating users with negative user ID's. This apparently causes many problems, and deleting all of them helped improve performance of WGM. It still generates negative UIDs sometimes, though, so it's something to watch out for. When creating new accts, you need to assign anunused UID number since canceling user creation when a negative comes up simply results in an untitled user name with a negative UID and still causes problems. (Note: this has been a problem since 10.4. What's more, WGM has sometimes assigned duplicate UIDs since 10.4. Maybe it's all related, but I thought computers were supposed to be good with numbers...)
2) During tests, I initially rebuilt the directory by manually exporting users/computers/groups from old WGM and manually importing to new WGM. This seemed to (almost) completely eliminate errors and negative UIDs in the test environment, but for the final rebuild I decided to slapcat the old directory, and import all at once, but neglected to delete the negative UIDs, thus bringing them to the new server (crap). There might be some other corruption that I carried over at the same time. We might have better luck doing the manual export/import, but don't have time to rebuild again just now.
- 0
jasonpvp ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Additional note - I just found two users, untitled_1 and untitled_2, both with uidNumber=99. When I deleted these, I stopped getting the username alread exists error