Error retrieving Global Shared Address Book error

Hi'

I am' having the same problem - Kerio Mailserver (with OpenDir extension) is installed, could this have anything to do with this?

Me too ... I'm sure I wound up deleting a user, but I'll be damned if I can figure out which one had this GUID and why it's that important.

com.apple.SharedAddressBookAdmin group seems to be added from 10.6.0 to 10.6.2 update. Afterward I converted OD master to standalone role, since the machine isn't being used for LDAP at all. Once in standalone mode, and Server Admin is open and running..

servermgrd[81]: Error retrieving Global Shared Address Book info: Error Domain=com.apple.SharedAddressBookAdmin Code=1 UserInfo=0x10069e2f0 "Record with GUID '77C3B992-8E81-45BF-A48D-6896877D2428' not found"
servermgrd[81]: Error retrieving Global Shared Address Book info: Error Domain=com.apple.SharedAddressBookAdmin Code=1 UserInfo=0x10069e2f0 "Record with GUID '77C3B992-8E81-45BF-A48D-6896877D2428' not found"

Repeated over and over in the logs. I really hope I can come up with a solution here. This is annoying.

I install OS X server in VMware Fusion and I just deleted the 2 added addressbook groups and nothing seemed to immediately break, but since its in VMware and local, I cannot be sure it is an OK thing to do...

I couldn't figure out how to get proxy cleanup to work on 10.6.2 so that was a bust for me. In my jerking around, I managed to bungle the OD and lock the diradmin out of any changes in the Workgroup Manager.

However, in desperation I backed up my OD database, exported the user and group records for extra measure, then shutdown all the services, then converted the OD Master to standalone, then converted it back to a master, then restored the backup onto the new master ... (at least I think that's how I did it). Anyway, this stupid error went away and the open directory acts as it should now.

I found out by reinstalling on vmware, and going through the workgroup manager looking for the missing GUID that the OD master has a group called "Workgroup" with a GUID equal to the one listed in the system log.

When I converted to standalone ldap, Workgroup group goes away. Problem starts. If I manually enter a workgroup group in my Local LDAP with the same settings as it had in the OD master groups, the message goes away.

This is a giant, ugly hack, and I am not even sure what Workgroup is used for, etc, etc. When Apple releases updates to OS X server, I will be removing that entry and seeing if the updates solve the issue.

This is a huge find. I wound up stumbling onto a similar but largely ineffective fix ... I had the name of the group wrong. I realize now it should have been Workgroup, but I just fudged a new group with the mystery GUID, naming it appropriately enough, Mystery. In the course of reloading the OD, it looks like a new Workgroup group is created ... along with my now useless Mystery group. Next time I'll just skip to Joe's fix.

check /Local/Default/Groups/com.apple.server.globalSharedAddressBook/NestedGroups

This entry contained the invalid GUID in my case. Removed it, allowed all users access to the AddressBook (via ServerAdmin, Access) and the problem went away.