Server App 3.0: no existing connection from which credentials can be copied

I am having this same issue as well. If I destroy the OD master and set up one from scratch it works. However if I restore my OD archvie I cannot authenticate or modify users. Not sure what the fix is yet.

I have the same problem. I also have the problem that network users cannot access file shares/Time Machine Server.

I made big error of upgrading my MAC Mini Server runin Mountain Lion (10.8) to "Maverick's" (10.9). I found out that I also had to spill out $19.99 for the new MAC OS X Server App. Thanks Apple . . . . . After the upgrade I have the same situation as described above by charliefromnew milford

Yesturday although my MAC did not have any pending software upgrades, I noticed that the OS X server had an update. I applied the OS X Server update and now the the app does not crash, but we are getting the "no existing connection from which credentials can be copied" error. I have the same problem. I also have the problem that network users cannot access file shares/Time Machine Server.

An sudgestions??

Same exact problem. In the end I backed up critical data, destroyed the OD Master & started over. Lame.

I did a clean install of 10.9, migrated data back using the Migration Asisstant at first boot (from a block copy clone of the boot drive), and then upgraded the server bits by downloading Server App v3 from the 'Store. Everything seemed to be ok until I ran into this issue.

Same problem here. That is really a bad thing especially in a productive environment. Does anybody have an other solution than building it from ground up?

I resolved this by deleting my Open Directory Master, and thus deleting all the user & groups. I created a new Open Directory Master when I turned the service back on. I don't have a solution for environments with too many users to do this for, so all users and groups have to be RECREATED. If you try this, BE SURE TO FIRST ARCHIVE THE EXISTING OPEN DIRECTORY MASTER as a precaution so what I've outlined can be undone.

I don't know to what extent doing this will have on the other services and all the shares and permissions have to be set up again. I use the wiki service and I lost some of my different groups with this.

Hi,

What about existing mailboxes if I delete and recreate the OpenDirectory server? Do I need to manually copy the Maildir directories to the new created users or will they link if I give the new users the same usernames?

Really crappy stuff. Everytime I update OSX server something seriously breaks...

//Staffan

I have the same problem. I have this problem when i try, for example, to change a password for ONLY newly created accounts, the accounts i created after the upgrade. The accounts i had from before, i have no problem with. Plus, i have the Server app crashing on me in many occasions. I hope they fix it soo.

I solved my probelm. since i upgraded to Mavericks i started geting some errors like " existing connections is not authenticated: Password change is denied" and " no existing connection from which....". i followed this http://support.apple.com/kb/TS5289. and it solved my problem. simply run this code:

sudo touch /var/db/openldap/migration/.rekerberize

sudo killall PasswordService

and then re open your Server app.

good luck

Thanks for the answer/reply but I still have the same issue.

the same at me. has someone tested OS X 10.9.1?

this is a serious issue for us, we have 50 users being disrupted by this issue currently. we considered experimenting with 10.9.2 in the hopes that it fixed it, but we decided against it

So has any one got work around on this? I have the same issue after upgrading my company's mac server and now I can't do anything on the user management part. Have about 30 users on this server, hope I can fix this issue by weekend if not have to work OT.

I our case the resolution was correcting the hostname and computer name. In the initail install of the server, the hostname was entered incorrectly. Once they were corrected everything worked (see image below). Just run the server app, select the server and make sure that the host name is correct. In our case the hostname macprensa.local Once the host name and computer name were corrected and the server re-booted everything worked. Hope this helps