[SOGo] LDAP Adress Book not accessible?

Simon Josi sogo@opengroupware.org
Tue, 22 Apr 2008 20:06:52 +0200


Hello,

I've setup SOGo on CentOS 5 with the RPMS's provided.  I can login via
the web user interface, but if I want to add a new card in the address
book, a new window shows up displaying this error:

An error occurred during object publishing
the requested object could not be found!

The following got written into the logfiles just after the action was
triggered:

2008-04-22 19:52:09.012 sogod-0.9[29981] Note(SoObject): SoDebugKeyLookup is enabled!
2008-04-22 19:52:09.013 sogod-0.9[29981] Note(SoObject): SoDebugBaseURL is enabled!
2008-04-22 19:52:09.013 sogod-0.9[29981] Note(SoObject): relative base URLs are enabled.
Apr 22 19:52:09 sogod-0.9 [29981]: <0x0x84e0570[GCSFolderManager]> Note: loading 4 GCS folder types:
Apr 22 19:52:09 sogod-0.9 [29981]: <0x0x84e0570[GCSFolderManager]>   contact: OK
Apr 22 19:52:09 sogod-0.9 [29981]: <0x0x84e0570[GCSFolderManager]>   appointment-oracle: OK
Apr 22 19:52:09 sogod-0.9 [29981]: <0x0x84e0570[GCSFolderManager]>   contact-oracle: OK
Apr 22 19:52:09 sogod-0.9 [29981]: <0x0x84e0570[GCSFolderManager]>   appointment: OK
2008-04-22 19:52:09.019 sogod-0.9[29981] Note: setup default manager at: postgresql://sogo:secret@localhost:5432/sogo/sogo_folder_info
77.57.89.150 - - [22/Apr/2008:19:52:09 GMT] "GET /SOGo/so/sjosi/Contacts//members/newcontact HTTP/1.1" 404 208/0 0.027 - - 0M


I provided the following SOGoLDAPSource:
{
 CNFieldName = cn;
 IDFieldName = uid;
 UIDFieldName = uid;
 baseDN = "ou=users,dc=example,dc=com";
 bindDN = "cn=Manager,dc=example,dc=com";
 bindFields = uid;
 bindPassword = secret;
 canAuthenticate = YES;
 isAddressBook = YES;
 id = members;
 displayName = "Members";
 hostname = ldap.example.com;
 port = 389;
}


I did take a look at the public sogo demo at sogo-demo.inverse.ca
and noticed a book "Shared Adresses - Adresses" which just behaves 
the same way: The context menu of this book is all grayed out and 
adding a new card to this book results in a new window opening up,
displaying the same error message.


Thanx in advance,
Simon