Ok I am getting a little fed up of Leopard server now. Not only does the iCal server not work for me but I am now getting the following errors when trying to create users or change which groups they are part of...
"Error '-14120' occurred while processing a command of type 'setMembership' in plug-in 'servermgr_accounts'"
and
"The server reported the error '-14120' while trying to create the user."
I think somehow I have lost permission to create users etc? Strange seeing as I am the main administrator.
Anyone got any bright ideas?
Macbook,
Mac OS X (10.4.6),
2GB Ram, 120BG HD and Black Case :)
Afraid not... I've been running on 10.5.1 since they made the patch available, and have also been getting these plugin errors continually as well.
I just did a complete rebuild of my OD and am still having the problems, and since the rebuild, one of my groups can no longer access their wiki, despite the fact that all other groups can access theirs. The short names and GUIDs match, so I can't imagine what the problem is.
I have had the same issue- I entered the wrong DNS setting for the machine when setting it up. I found my mistake later and have changed it in a few places to be correct- maybe this is why it now kicks up the -14120 when I try to create a new user in Server Preferences. I can add a user from the main system settings, but this user is not available or found in the Workgroup Manager. I guess this may call for a clean install, bummer!
Same exact problem here. I have all the latest updates (10.5.1) installed and Im able to login into the server remotely using Server Preferences, but Remote Desktop does not work.
Apple, come out with a fix! The server is useless at the moment!
If a Leopard server is configured using DHCP, Open Directory ends up populated with old server addresses which no longer work. The first step is to set a fixed address - change Network Setting from DHCP to "DHCP with fixed IP". If you are not behind an Airport or other NAT gateway, you will need to get one or work with your admin to register your fixed IP. Hijacking a DHCP address for your own use may work as a short term solution as long as your server does not go down for long time.
Next, fix the open directory. If you remember the old ip address, you can use "changeip" command line. I didn't and so I had to dig into LDAP directory using dscl. In my case, I had to do:
Ok so I've had the same problem and i think i just fixed it. Since it seems this error is a time out or what not on resolving dns for the open directory service what i did seemed to fix it. This is my first time using leopard server, installed it last night. Everything seemed to work untill i tried to add users. and got the same error as u guys
Root of problem: When you first install the server it asks for a dns name or what not for me and for you guys i figured i could change this later. It resolved my ip to my internet company rr-biz-something.com. This is because when i set it up i just plugged it straight into the Cable modem router since it supports 4 ip's, I then planned on migrating it into the network that is routed via an Airport extreme. Anyways i guess this configuration writes itself across the hostname entry for the Open Directory Service (LDAP Server) when i changed the hostname later and made it a static IP under network preferences the Open Directory Server didn't pick this up. So whenever the admin apps wanted to edit the Directory it could find and traverse the tree. Or something, this is just what i observed, I'm a photographer who's done plenty of network consulting in his life, lol i'm no LDAP jedi.
How I fixed it:
1. Open server admin. If you arn't running the advanced configuration switch your server that "mode" i did the workgroup set up as i figured it would be enough, which it was, i just ended up having this problem.
2. Goto the "Open Directory" light under your server in the left sidebar.
3. Click on the settings tab at the top.
4. Click on the general tab then click on replica tree, there's probably a bunch of **** in there that was the inital configuration. All the assigned IP's were in there and the hostnames they resolved to. Also if you peak under the ldap tab the search base will probably be wrong. but for whatever reason you can't change it manually. So back to the General Tab
5. you will see "Role: Open Directory Master" at the top click change
6. It will give you some options select stand alone. and click next or go or something.
7. it will do its thing and bring you back out. If i can remember, i just did this however sometimes you just click stuff lol
8. under role: it will say standalone server.
9. Click change again.
10. Change it to Open Directory Master
11. It will ask for a username and password. I unknowingly went with the default which is Directory Administrator. This is the master user/pass for your server. Wish i would've made it "admin" i'll probably just add "admin" as a short name later though. Anyways remember what you put here. There may also be a space for your ip just make sure the settings you want are filled out properly.
12. click continue
13. It should set it up and relaunch the service.
14. If you didn't keep the same user/pass as the admin account you first started up you will need to remove the server from your server list in server admin and re add it using the new user/pass and then it will log you back in.
15. Side note: all of apple's admin apps are just gui's that connect to services on the server, even if the app is being run locally.
Let me know your results this resoved my error -14120 when trying to add a user
Had nothing but problems with the first install after trying to move data locations. Wouldn't it be nice if Apple adjusted the privileges of the "Streaming" folder from within the "Server Admin" app when you set your streaming folder location to somewhere other than the boot disk? Anyway, after much work, I gave up, reinstalled and decided not to touch anything beyond the "Keep It Simple Stupid" interface. Adding my 3rd user to a stand along machine and here we are
"The server reported the error '-14120' while trying to create the user"
We are really talking "just installed" and "just Software Update'ed" and adding the 3rd user. Maybe it will be stable by 10.5.8 but 10.5.2 is definitely not ready for prime time. Mac software was never this fragile before Mac OS X.
I stumbled upon this error as well. In my case, adding some DNS records and then making sure the server was Kerberized (Server Admin > Open Directory > Kerberize...) solved the problem.
