ComputerGroups not accessible after upgrade to 10.5

[craigsheppard]

I finally upgraded my 10.4.11 server (intel xserve) to 10.5.6 server today. Everything went well, except now in WGManager, I have *no* computer groups (not even the default ones). I can see my old 10.4 computer lists no problem (if I use the inspector).

When I try to create a new group, I get an error:

Got Unexpected Error
Error of type eDSOperationFailed (-14483) on line 1139 of /SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/PMMUGMainView.mm

I tried restoring from a pre-10.5 open directory archive, as well as deleting all of my computer lists and computers, and I still get the same problem.

So I go to dscl to see what’s up…

Everything seems fine here as well, except inside ComputerGroups, when I do an ls I get:

/LDAPv3/127.0.0.1/ComputerGroups > ls
ls: DS error: eDSOperationFailed
<dscl_cmd> DS Error: -14483 (eDSOperationFailed)

I can’t seem to find *any* info on what’s happening here, all I get from internet searches is what the error means: “Specified operation failed during authentication.”

Any ideas at all? Unfortunately, this is of course a production server with a few hundred managed computers… I think they will continue to work as computer lists, but I have to use WGManager from 10.4 to make changes or additions to the management, and I’m not able to include the management options that persuaded me to upgrade in the first place!

Is there any way to replace the computer groups part of the schema with the default one and continue from there?

Thanks! Craig

[jevenhouse]

I have a very similar issue. How did you resolve this?

Thanks!
John

[craigsheppard]

Oooh – this was a while ago 🙂

I *think* I just crossed my fingers and made an archive of the open directory (via server admin), and then restored it… I’m not sure but I *might* have demoted to standalone and re-promoted the server back to a master before doing the restore. I do remember I was at the point where I was going to have to do something, or start re-creating all of the accounts by hand, so I tried this on a hunch.

Whatever I did, everything has been fine since (and passwords did not need to be changed). Backup your server and give it a try. Maybe post back for others (unlike I did 😉 )…

Craig

[kelshafie]

I was getting a similar error trying to access the directory. I archived and restored without demoting to standalone and everything was back right away. Just FYI for a future viewer. 🙂

[jevenhouse]

Upon the advice of others, I ended up demoting to standalone, archiving/restoring, and then promoting to master. I lost my passwords but everything seems to be working normally again. Thank you!

[Author]

Posts