Kopano 8.1 license

german

#1

I have a problem with blood Kopano 8.1, the Kopano-dsd License Service will not install from the App Store. installation from the repository is not possible. The message is Kopano-DSD: “Depend of: libmicrohttpd10”.


#2

I have a problem with license Kopano 8.1, the license service Kopano-DSD will not install from the App Store. installation from repository is not possible. The message is Kopano-DSD: “It depends on: libmicrohttpd10”.


#3

Hallo f.pigliacelli,

kopano-dsd is currently not needed when running Kopano (and therefore also not automatically installed).


#4

I have a license of kopano and I can not enter the serial. If I’m going to integrate it with active directory it will not work.


#5

Are you maybe more hitting a limitation of Univention, than Kopano? Because we don’t care of the ldap source is a local ldap, exterbak openldap or activedirectory.

Or said differently: where do you get this error message and what does it say exactly?


#6

I installed Univention connected to an active directory server, I installed the plugin Kopano on windows server 2012 r2, I configure the email server on microsoft but Univention no matter the user created.
This is a limitation of the license free of Kopano, I do not understand how to install the serial Kopano of Univention.

hu Jan 5 22:45:47 2017: [warning] Failed to authenticate user “administrator” from “192.168.1.5” using program “apache2”
Thu Jan 5 22:53:35 2017: [error ] LDAP search error: Can’t contact LDAP server . Will unbind, reconnect and retry.
Thu Jan 5 22:54:44 2017: [warning] Shutting down
Thu Jan 5 22:54:46 2017: [ notice] Server shutdown complete.
Thu Jan 5 22:56:44 2017: [ notice] Starting server version 8,1,0,335, pid 5963
Thu Jan 5 23:01:55 2017: [warning] Object not found unknown user "administrator ": administrator not found in LDAP
Thu Jan 5 23:01:57 2017: [warning] Object not found unknown user “administrator s”: administrators not found in LDAP
Thu Jan 5 23:04:17 2017: [warning] Shutting down
Thu Jan 5 23:04:19 2017: [ notice] Server shutdown complete.
Thu Jan 5 23:04:20 2017: [ notice] Starting server version 8,1,0,335, pid 7338
Thu Jan 5 23:04:24 2017: [error ] createStore(): already exists
Thu Jan 5 23:04:24 2017: [error ] Failed to create store (id=1), errorcode=0x8 0000008
Thu Jan 5 23:12:46 2017: [error ] LDAP search error: Can’t contact LDAP server . Will unbind, reconnect and retry.
Thu Jan 5 23:20:39 2017: [warning] Shutting down
Thu Jan 5 23:20:41 2017: [ notice] Server shutdown complete.
Thu Jan 5 23:20:42 2017: [ notice] Starting server version 8,1,0,335, pid 9875
Thu Jan 5 23:20:45 2017: [error ] createStore(): already exists
Thu Jan 5 23:20:45 2017: [error ] Failed to create store (id=1), errorcode=0x8 0000008
Thu Jan 5 23:30:35 2017: [warning] Log connection was reset
Thu Jan 5 23:35:38 2017: [warning] Shutting down
Thu Jan 5 23:35:40 2017: [ notice] Server shutdown complete.
Thu Jan 5 23:35:41 2017: [ notice] Starting server version 8,1,0,335, pid 17180
Thu Jan 5 23:35:44 2017: [error ] createStore(): already exists
Thu Jan 5 23:35:44 2017: [error ] Failed to create store (id=1), errorcode=0x8 0000008
Thu Jan 5 23:36:31 2017: [warning] Log connection was reset


#7

Are you referring to the “createStore(): already exists” errors?

The way I understand the AD join (membermode its called afaik) of Univention you don’t need to install the Kopano Schema on your AD anymore. The Univention server gets joined into the domain and therefore can locally authenticate users. All additional attributes are then managed in Univention and not your AD.

Maybe it could be a good idea to get in contact with the Kopano support or your reseller to have a direct look at your system.


#8

It seems a problem linked to the ldap. I am attaching the logs.

root@mailserver:~# tail -f /var/log/univention/con
config-registry.replog connector.log connector-status.log
root@mailserver:~# tail -f /var/log/univention/connector.log
12.01.2017 04:48:42,679 LDAP (PROCESS): Using DEMO as AD Netbios domain name
12.01.2017 09:56:14,527 MAIN (------ ): DEBUG_INIT
12.01.2017 09:56:14,539 LDAP (ERROR ): Failed to lookup AD LDAP base, using UCR value.
12.01.2017 09:56:14,987 LDAP (PROCESS): Building internal group membership cache
12.01.2017 09:56:14,996 LDAP (PROCESS): Internal group membership cache was created
12.01.2017 09:56:15,6 LDAP (PROCESS): Using DEMO as AD Netbios domain name
12.01.2017 10:01:15,327 LDAP (PROCESS): sync to ucs: [ user] [ modify] uid=administrator,cn=users,dc=demo,dc=loc
12.01.2017 10:01:15,330 LDAP (WARNING): __set_values: The attributes for lastname have not been removed as it represents a mandatory attribute
12.01.2017 10:05:54,470 LDAP (PROCESS): sync to ucs: [ user] [ modify] uid=administrator,cn=users,dc=demo,dc=loc
12.01.2017 10:05:54,473 LDAP (WARNING): __set_values: The attributes for lastname have not been removed as it represents a mandatory attribute


#9

I created a user of Univention and Kopano works. but it does not appear in the active directory users.
if you create a user in the AD Kopano connector in does not work to access to Kopano.


#10

I don’t think the Univention AD coupling works, the way you intent it to.

When you join Univention into the AD and install an app through Univention you don’t need to install any ad extensions. The way it is intended is that you manage additional attributes required by Univention apps only through Univention.

Also users created in Univention don’t sync back to the ad.