MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.



  • It’s been a while since I’ve added new users to the system, and since last time we have upgraded the server from Debian 8 to Debian 9, and Kopano has gone through a few versions since then as well, and is now at 8.7.5. The last users I’ve created didn’t get any stores automatically created like before , and when they try to login they just get the “Unbekannter MAPI-Fehler: MAPI_E_NOT_FOUND”
    I can create the missing stores with “kopano-storeadm -h default: -Cn new_user”, but I would like to have my system creating these stores for me automatically, like before.

    Anyone know where I should start looking?



  • hello @klausade

    in the past i encountered an update that deleted the createscripts in /etc/kopano/userscripts/
    check if the scripts are present and if not you should find them in /usr/lib/kopano/userscripts

    best regards
    coffee_is_life



  • The script is present in /etc/kopano/userscripts/createuser.d/00createstore



  • can you use the “kopano-admin -l” command without errors?

    the script should point to ‘kopano-admin -v --utf8 --create-store “${KOPANO_USER}” --lang “${KOPANO_LANG}”’
    is the command working if you substitute the vars with the actual user and the language?

    what are the permissions on the folder “userscripts”, “createuser.d” and on the files?



  • I can use the “kopano-admin -l” command without errors, but it’s an ELF 64-bit LSB shared object at /usr/sbin/kopano-admin

    All the dirs and files at “userscripts”, “createuser.d” and on the files are root:root and 755.


  • Kopano

    @klausade what would help here is the logging of kopano-server from around the time you created the new user in ldap.



  • @fbartels said in MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.:

    @klausade what would help here is the logging of kopano-server from around the time you created the new user in ldap.

    I’ve just created a user in ldap, and at the same time i’m doing tailf on syslog, and there is nothing being registered there. For reference I’ve just done a “kopano-admin --details” on a non-existing user, and the I see " kopano-server[1755]: K-1515: Object not found unknown user “pest”: pest not found in LDAP", so it’s logging something.

    Doing a kopano-admin --details on this new user gives me:

    kopano-admin --details test3
    WARNING: Unable to get user store entry id. User possibly has no store.

    Object id: 2957
    Extern id: 12490
    Username: test3
    Fullname: ma3 test
    Emailaddress: test3@
    Active: yes
    Administrator: no
    Address book: Visible to current user
    Auto-accept meeting req:no
    Mapped properties:
    0x8C6D0102 48 bytes
    PR_SURNAME test
    PR_EC_ENABLED_FEATURES imap; mobile; outlook; webapp
    PR_EC_DISABLED_FEATURES pop3
    Unable to show object quota information: missing or invalid argument (0x80070057)
    Groups (1):
    Everyone


  • Kopano

    @klausade said in MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.:

    I’ve just created a user in ldap, and at the same time i’m doing tailf on syslog

    did you also do a kopano-cli --sync?



  • @fbartels said in MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.:

    you also do a kopano-cli --sync?

    No, but I did a kopano-admin --sync, what is the differene between those (kopano-admin --sync and kopano-cli --sync)? Anyway, a kopano-cli --sync didn’t help.


  • Kopano

    they are just two different tools. the end result is the same.

    The store creation message is usually logged on the default log_level. If you don’t see it then you must use a log level with lower detail.

    edit: oh, and since someone else had that recently: you do not have enabled the user_safe_mode by any chance?



  • @fbartels said in MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.:

    The store creation message is usually logged on the default log_level. If you don’t see it then you must use a log level with lower detail.
    edit: oh, and since someone else had that recently: you do not have enabled the user_safe_mode by any chance?

    /etc/kopano/server.cfg:user_safe_mode = no

    I now have “log_level = 6” in /etc/kopano/server.cfg, but there is not nothing happening when I add users.

    I have another location with the same OS and Kopano version setup, and there it works just fine.Can this indicate a problem with the database?


  • Kopano

    @klausade no, a database issue is unlikely.

    As a next step I would recommend a remote session on your system. Please get in contact with our support for this.



  • And they found the error, and fast!
    https://jira.kopano.io/browse/KC-1339 “Cannot create stores on some machine after upgrading to 8.7” turns out my pointers to the scripts was not updated.

    The fix was just uncomment the set values of the following settings in server.cfg:

    #createuser_script = /etc/kopano/userscripts/createuser
    #deleteuser_script = /etc/kopano/userscripts/deleteuser
    #creategroup_script = /etc/kopano/userscripts/creategroup
    #deletegroup_script = /etc/kopano/userscripts/deletegroup
    #createcompany_script = /etc/kopano/userscripts/createcompany
    #deletecompany_script = /etc/kopano/userscripts/deletecompany


  • Kopano

    @klausade which is exactly what @Coffee_is_life already suggested, but you denied being the case…



  • @fbartels said in MAPI_E_NOT_FOUND error, no store automatically created for new ldap-users.:

    @klausade which is exactly what @Coffee_is_life already suggested, but you denied being the case…

    @Coffee_is_life: sorry for not paying attention to your suggestion, I didn’t have enough coffee!
    But to my defense, the scripts were there, in /etc/kopano/userscripts, I thought that was how it should have been. Anyway, next time I will listen, and not pull a support-ticket.



  • addition to your defense, i should ask for the folders (createuser.d;createcompany.d etc.) aswell, not just the scripts
    :)

    but its solved so well - mistakes were made :)
    drink more coffee ;)


Log in to reply