Currently Being ModeratedAug 20, 2012 1:02 AM (in response to AnalogKid)
Well, I did a clean install of ML and then of Server.app and started over. I can edit these group access parameters now, but that's a pretty draconian solution once this server has been deployed.
Anybody know where the groups to services mappings are held? I suspect a file went corrupt somewhere, but I don't know which one.
Currently Being ModeratedAug 23, 2012 6:15 AM (in response to AnalogKid)
I can only say that i've got the same problem. I unfortunately don't have the luxury of clean installing ML. Just like you, i can edit the default 'Workgroup' group, but the second i try and edit groups created by me, i get the same symptoms as you, the spinner at the bottom right of the server app just carries on spinning while saying nothing, and while the 'Edit Access to Services' box appears, all that is in there is a white square. When that happens, i then can't even edit the 'Workgroup' group, or even touch anything else Open Directory related until i've restarted the machine, as it's clearly stuck doing a task in the background.
Is there anyway to even debug the server app so i can see what it is doing? As you say, the logs don't seem to be much help.
Currently Being ModeratedAug 25, 2012 7:52 AM (in response to AnalogKid)
Just an update in case anyone else in the future has this problem and
can't work out what the **** to do.
I managed (after a lot of heartache) to finally stop the service hanging
by going into the 'Directory Utlity' app, then using the 'Directory
Editor' to access the /Local/Default node. In there go to the 'Groups'
section and there is a list of service access records called
com.apple.access.nameofservice. I deleted all of them, and this fixed the
hanging. Of course if you had setup any server access settings, you will
have to do this again. But that's a small price to pay.
Currently Being ModeratedAug 25, 2012 1:43 PM (in response to Ben Pirozzolo)
I can't replicate the problem because I've rebuilt my server from the ground up, but I really appreciate you reporting back on this. I've been quietly worried this problem would crop up again and it's good to have a solution at hand.
I'd call this a bug and report it to Apple.