@helmut If duplicates are caused by key ‘bin’ then it could a problem with source_key_auto_increment in ‘settings’ table which somehow got zeroed (or decreased significantly). For some unknown reason there is nothing in the code to handle this situation. So you can increase source_key_auto_increment manually or just check if it’s increasing automatically over time (with every error) and wait till it goes away. Took me like 6 hours to figure it out and yes, this problem IS in kopano also.

I think I solved it! Yaffas set ldap_user_unique_attribute to uid, but Kopano set it to uidnumber by default, and since I didn’t carry over all of Yaffas ldap-settings, the stores were orphaned.

Hello fbartel,

you enlightened me about status 405. So i removed that intercept and deeply cleaned the configuration and i finally got it working.

So the strict configuration you pasted runs perfectly for Z-push reverse proxy.

Thanks a lot

Walter

@ilmix said in Unable to bind to port 236: Name or service not known.:

“the asterisk is the multi-protocol address wildcard.” and I wasn’t sure which protocol is used there.

yes, but that means *:236 and not *127.0.0.1:236.

@ilmix said in Unable to bind to port 236: Name or service not known.:

directory ‘/data/zarafa/attachments’ - Permission denied.

That can either be accredited to appamor, systemd or your general system configuration. There was recently a topic on this forum and the general recommendation is to use the default paths.

8.5.5 is also already a quite old, I would recommend to use a more recent version.

Hey Petervbeck, I have read the issue you are encountering and I would suggest you to fix it by disabling it at a Group Policy level. You can do it by Starting Group Policy Editor and load the preferred Group Policy Object. Not extend User Configuration, Administrative Templates, Start Menu and Taskbar. After that just double-click the option that says Disable and Remove Links to Windows Update or the one that says Remove links and access to Windows Update. Pick the option Enabled, press OK and exit from GPE. To disable Microsoft Update according to per user base just start regedit.exe and go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer. You can read more about Microsoft Update issues from https://appuals.com/how-to-manage-and-synchronize-wsus-server-with-microsoft-updates/ as well. Choose the option of New from the edit menu and DWORD value. Here add a name of NoWindowsUpdate, and click Enter. Then just double-click NoWindowsUpdate, and set it to 1. At the end exits from regedit.

Nothing appears in the dagent log… even after increasing log level to 5

Chris

@Albert said in ZCP 7.2.1.51838 to Kopano 8.7.0:

My preferred solution is not doable

to me your approach seems very doable, in fact a lot of our customers have upgraded this way. there is no need to rename the database or change the database user, you can just continue the ones you have used with Zarafa.

As for the missing elements this would need to be investigated.

Our general recommendation is of course to use our supported packages, instead of the ones provided through Debian as they give you access to our support for questions.

HI @Coffee_is_life ,

I guess you are right :) didn’t noticed it. maybe it is a good idea to use your brain while fiddeling around with something unknown. but thats what testing system are for…
In the end I maybe just slapcat the ldif file and afterwards sed ZARAFA and zarafa to kopano/KOPANO.

btw. @fbartels
I got a little problem the script further down too:

grep: /usr/share/doc/packages/zarafa/zarafa.schema: Datei oder Verzeichnis nicht gefunden

even more interesting I found the schema here:

/usr/share/doc/zarafa/zarafa.schema.gz

this is all a bit confusing, since I 've got no decent experience with ldap.
But I haven’t broken it it, so there is still hope :)

is it possible that there “extra informations” like ZARAFAQUOTAWARN where only used the yaffas and not zarafa itself?

like you already said maybe I shouldn’t care so much about these schemas and just migrate and use it :)

greetings
1of16

@dw2412
Hi Andreas. I tried a new outlook profile and complete new user profile. No success.
Do you know a “special” windows 10 only related update, that i can check?

Thanks!

Frank

The last of these two

Dear Guys,

Thank you for you support and help… really apprecite
actually when i run the script the /tmp/detials.txt file was just 546 bytes and had only details of 2 usernames but i did a direct of the script itself to a file and it worked just the way i wanted

once again thanks a lot

regards

simon

Dear Guys ,

appreciate your quick response .
dear basti i have not created the users but my old zarafa has about 400 users.
would also weigh the option to have to probably contact support for profesional services as mr felix says

thanks guys once again

regards

simon

Klaus,

honestly… There will be no one giving you any warranty. Felix already mentioned that they’re not testing anything regarding the old legacy client anymore. On other hand they’re not breaking compatibility with newer versions of kopano core currently. Outlook 2003 is already far beyond being any point of suppport.

Actually with Outlook 2003 you should not experience any update troubles like with Outlook 2010 or 2013 since there are no updates at all anymore.

From the Kopano Core 8.6.7 version all I can tell you it that everything I need is working with Outlook 2010.

I actually still use Outlook 2010 and will use it as long as it works. Either I will have time to finish some project regarding Mapi over HTTP (but other things have more priority currently than that like i.e. family inc. children) or I will change to DeskApp until I have a working Mapi over HTTP interface. So I’m at least being prepared for some change in kopano core that might break compability to old Zarafa Client. Don’t know what you mean with calender only synchronisation but if it is meant in context to have calendar details of all employees available on the road - maybe you should have a look at latest 2.4.4 Z-Push and use some iPad / Android Tab for this purpose… There are changes in 2.4.4. regarding making shared stores available by using formatted user names for login to shared stores.

Best regards

Andreas

i enabled as much debug logging as i can and found the following in the webapp debug file, because i dont’t see anything in server.log, etc.

[02-Aug-2018 20:08:53] ERROR - array ( 'msg' => 'Undefined offset: 267976962', 'file' => '/usr/share/kopano-webapp/server/includes/core/class.operations.php:3457', ) [02-Aug-2018 20:08:53] - ' @ class.operations.php:3457 - kopano_error_handler(...) @ class.operations.php:1773 - Operations->getAttachmentsInfo(...) @ class.itemmodule.php:452 - Operations->getMessageProps(...) @ class.itemmodule.php:55 - ItemModule->open(...) @ class.jsonrequest.php:57 - ItemModule->execute() @ kopano.php:139 - JSONRequest->execute(...)

When i look into the webapp sourcecode into the coresponding file, it looks also like attachment loading code.

Edit: I do a test with Outlook and KOE and all attachments are available and viewable as expected.

Thanks guys …
i will check it out and let you guys know

regards

simon

@jsatterfield said in Error: Unable to get store entry id .... 0x8004010F:

an organization entry, not a user or a company

Can you explain a bit more what you mean with organisation entry?

Hi there,

@fbartels and me finally found the issue.

Univention is using LDAP. The restore of the mysql dump creates an orphant. This is why the front ends were always empty.

This is the link about how to link an orphant to a user:

https://documentation.kopano.io/kopanocore_administrator_manual/user_management.html?highlight=orphan#reattaching-stores-from-deleted-users

This finding and action closes the topic. Thanks so much to @fbartels

Regards,
Horst