Error '-14120'

Not of any help but I am geeting the same thing, even after rebuilding the server from scratch. After creating users with these plugin errors I then lose the ability to authenticate in Workgroup Manager too!

I too got this issue...Google turned up nothing useful, but at least it's "nice" to see there's a thread here about the issue, hopefully we can figure it out.

could be that your OD data was bad, do you have a resent archive of the data you can try and reinstall?

Well I was able to finally fix my plugin errors after demoting the system to standalone and recreating my users from scratch and NOT touching any of the Policy settings.

As soon as I enabled Policy settings I would start getting plugin errors even with a completely clean setup.

I have been surprised that there hasn't been more people complaining about OD bugs with 10.5

Not to hijack your thread, but would somebody with a working server try binding to another LDAP server via Directory Utility and tell me if you're successful? In another thread I describe 14002 errors. And the kicker is the exact setup worked flawlessly under 10.4.

FWIW-- even after confirming forward and reverse DNS entries, etc, I can't even get OD to start up.

-Damian

I get the same thing when trying to create a group or a user. Here are my system log errors:

Nov 14 05:57:48: --- last message repeated 1 time ---
Nov 14 05:57:48 macserver servermgrd[2161]: servermgr_accounts: got error -14090 trying to log to local LDAP node
Nov 14 05:57:48 macserver Server Preferences[2775]: XSAdminQueueController: gotServerError: -14120 forTransaction: <XSAdminTransaction: 0x16b37610>
Nov 14 05:57:48 macserver Server Preferences[2775]: Error creating user: {\n command = createUser;\n error = "-14120";\n}
servermgrd[2161]: DirectoryService crash detected, reauthorizing node
Nov 14 06:07:39 macserver slapd[2709]: Bad IPLOCALPORT value

I'm running a local standalone setup.

I went into Applications > Utilites > Directory Utility and saw that the light was green on the "Local Server" listed in directory services.

If I try to click "Advanced Settings" button and then click "Services" tap and uncheck "LDAPv3" in the list, after that it won't let me login to the "Server Preferences" until I renable it.

Anyone have any ideas?

Our Leopard server is giving the same error codes. I've moved it back and forward from Open Directory Master to local. When on Open Directory Master I was able to turn iCal Server on (I haven't been able to before), but then hours later the server stopped allowing file sharing and administration access.

Turning OD back to local let's me gain administration and screen sharing access but authentication still fails for file sharing clients.

add my name to the pile. i have gotten this error code for 'unable to write config file' since the first install of server10.5. upgrade did not fix it. i have lots of little permission issues and they often affect OD operations, or certificate authenticating, etc, etc.

it would be nice to have a definitive fix for this stuff.

I also have the same error message. However I am just changing the name of anyone in the 'Contact Info' tab of the Users settings. Need a fix soon...

Same Exact error. I am installing Leopard Server on a powerbook that meets all of the specs just to test it before putting it on my server. I have setup the server as stand alone and when I try to create a user, this is the exact error that I recieve. "The server reported the error '-14120' while trying to create the user". Any idea???

We get the same error -14120 error preventing us from adding or deleting users.

After much frustration with Leopard server we did a clean install, and decided to use the Workgroup mode (rather than advanced). But after adding a few users and share points Server Preferences is now giving this error.

Leopard server seems hopeless.

Same thing here. Repairing permissions didn't help.

Now I have the same error. i didn't expect this from Apple. I thought "it just works". I have a brand new Mac Mini as a test for Leopard Server before buying an XServe. I installed it from a clean re-format of the drive as a Standard Server and didn't expect to be immediately unable to create any users ....
I see that these messages were all more than a month ago but I don't find any Apple response or solution. Has there been one?

I had a similar problem and was able to resolve it with what I thought was an unrelated issue. During my initial configuration, the server defaulted to a DHCP network setup, so I went with it figuring I could just change it later. I forgot that it was on DHCP and I was getting a ton of errors trying to manage the server. was also losing my connection to the Server Setup even though I was connecting to localhost. I called Apple Support and they told me that Leopard Server is very buggy if you don't use a static IP. I had also put in the wrong DNS name for my computer so the person recommended that I do a fresh install using the correct networking info. Once I reinstalled and got all the networking info correct, I haven't had a single issue with it.

Even with a static IP this is still a problem.

I have installed Leopard server no less than 10 times. I have found that connecting to server preferences using myserver.myhost.com works as expected. If I use myserver.local it also seems to work. And if I use my internal static IP 192.168.1.3 it also works. Problem is, mixing and matching these connection methods it hoses the system. I have also found that opening workgroup manager can hose the system. This is a huge problem. The system should not let you connect in an "incorrect" manner.