Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 )

marty

Moved to kopano-core area.

fbartels

@thctlo If I read https://forum.kopano.io/topic/2211/kopano-webapp-isn-t-loading-failed-to-open-store/4 then you managed to find your issue?

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

Now ive create new users. First i need to create the new company.

why a new “company” for your new users? does the same effect also occur within the existing tenant?

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

WARNING: Unable to get user store entry id. User possibly has no store.

here its interesting to know what kopano-server logged at the time the user/store was created.

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

-p “Somepassword123”

I would think this leads to the quotes being part of the password.

thctlo

Hai Felix,

Setup, kopano + mysql backend.

Wel, i’ve done my mail migration yesterday.
My opservations. ( keep in mind this setup runs about 2 years now, almost flawless ) …
After upgrading to 8.7.0. i noticed the followin.

i host about 10 domains on my kopano server.
My steps.
kopano-admin --create-company domain.tld
This record is used for postfix so its able to lookup the virtual domains.

kopano-admin --create-store email@adres.tld -c email@adres.tld -p My!Passw0Rd -e email@adres.tld -f "full name"
Looks correct, but if you try this, you see an error on the !, thats why i quoted the password,
but without success, i’ve change the users password to one without ! in it and characters like @ % work fine.

Now i try to login, and you get that mapi error. I discovered that the source of this is that :
kopano-admin --create-store email@adres.tld -c email@adres.tld …
The stores where not created with this command.

So i created store manual: kopano-storeadm -h default: -Cn email@adres.tld

The ones with password notifications fixed with: kopano-admin -P -u email@adres.tld

So in the end i got everything working .
I was very happy with the kopano-migration-imap tool, that saved me a lot of extra work.

Conclusion for me, the source of the webapp mapi error, was the store that wasnt created.

I hope this helps someone.

fbartels

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

kopano-admin --create-store email@adres.tld -c email@adres.tld -p My!Passw0Rd -e email@adres.tld -f “full name”

I think the explicit --create-store here could be the culprit. This is not needed, all you need to call is kopano-admin -c email@adres.tld -p [...]

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

I was very happy with the kopano-migration-imap tool, that saved me a lot of extra work.

I’m confused. Did you use the imap migration tool to migrate users from one server to the other?

thctlo

@fbartels said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

kopano-admin --create-store email@adres.tld -c email@adres.tld -p My!Passw0Rd -e email@adres.tld -f “full name”

I think the explicit --create-store here could be the culprit. This is not needed, all you need to call is kopano-admin -c email@adres.tld -p [...]

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

I was very happy with the kopano-migration-imap tool, that saved me a lot of extra work.

I’m confused. Did you use the imap migration tool to migrate users from one server to the other?

Well, i did try at first, kopano-admin -c email@adres.tld -p [...]
i looked my “zarafa” install examples, how i created the first domains and that is exact how you suggested.
In my first “zarafa” setup i did have passwords with ! , and adding a \ to it helped but it did not in kopano admin or migrator, i just can not test the migrator anymore, the source server is gone.

But what i could test again.
kopano-admin -c info@testdomain.tld -p MyS3cet\!Pas@@%d -e info@testdomain.tld -f "info test"

Without the Quotes the pass is accepted again, thanks for that tip, but it still results in.
kopano-admin --detail info@testdomain.tld

User object id:         00000000AC..... 
WARNING: Unable to get user store entry id. User possibly has no store.
..
Mapped properties:
        PR_EC_ENABLED_FEATURES  imap; mobile; outlook; pop3; webapp
        PR_EC_DISABLED_FEATURES
Unable to show object quota information: missing or invalid argument (0x80070057)

and

cat /etc/kopano/userscripts/createuser.d/00createstore
#! /bin/sh
PATH=$PATH:/sbin:/usr/local/sbin:/usr/sbin
exec kopano-storeadm -Cn "$KOPANO_USER"

looks correct also. but no store was created.
fix : kopano-storeadm -h default: -Cn info@testdomain.tld

About the “confused” part, i’ll explain a bit better. ( i hope ).
A working kopano 7.2 was upgraded all the way up to now 8.7. The server works fine.

I needed to migrate and old Axigen server to kopano, so i created all domains, created the users, stores, rest passwords where needed, then checked if i could login with the webapp.

When this was done and working, now was able to use the migrator.
like this

/usr/bin/kopano-migration-imap --addheader  \
    --host1 IP_OF_AXIGEN --port1 993 --ssl1 --user1 "info@test.tld" --password1  "testSomePASS" \
    --host2 localhost --port2 143 --user2 "info@test.tld" --password2  "testSomePASS" --delete2duplicates --automap --subscribeall

And this worked great, and the end result is a working setup.

my suggestion is, is it possible, when you login into the webapp and an user store is not create, that the messages is “unable to login, no user store” .

I spend 1-2 hours checking my webserver and php logs due to the mapi error, i was thinking this was a php thing.

fbartels

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

kopano-admin -c info@testdomain.tld -p MyS3cet!Pas@@%d -e info@testdomain.tld -f “info test”

it works for me:

root@felix-debian-9-supported-master:~# kopano-cli --list-users
User list for Default (1):
User             Full Name            Homeserver
----------------------------------------------------------
SYSTEM           SYSTEM               Unknown

root@felix-debian-9-supported-master:~# kopano-admin -c info@testdomain.tld -p MyS3cet\!Pas@@%d -e info@testdomain.tld -f "info test"
User created.
root@felix-debian-9-supported-master:~# kopano-cli --list-users
User list for Default (2):
User             Full Name            Homeserver
----------------------------------------------------------
SYSTEM           SYSTEM               Unknown
info@testdomain.tld info test            Unknown

root@felix-debian-9-supported-master:~# kopano-cli -u info@testdomain.tld
Name:                          info@testdomain.tld
Full name:                     info test
Email address:                 info@testdomain.tld
Active:                        yes
Administrator:                 no
Address Book:                  visible
Features:                      mobile; outlook; webapp
Store:                         1898CC25C17E45128D14CBA4FA1FEE88
Store size:                    0.00 MB
Send-as:
Delegation:
Auto-accept meeting requests:  no
Auto-process meeting request:  yes
Out-Of-Office:                 disabled
Current user store quota settings:
    Quota overrides:           no
    Warning level:             unlimited
    Soft level:                unlimited
    Hard level:                unlimited
Groups (1):
Groupname
----------------
Everyone

Permissions:
root@felix-debian-9-supported-master:~# kopano-admin --details info@testdomain.tld
User object id:         00000000AC21A95040D3EE48B319FBA753304425010000000600000032000000574155594F4B78615176716D68333334624C705779413D3D00000000
User store id:          0000000038A1BB1005E5101AA1BB08002B2A56C200007A617261666136636C69656E742E646C6C00000000001898CC25C17E45128D14CBA4FA1FEE8801000000010000002CD1AF6418B4419B98B9C02F0B519E3470736575646F3A2F2F556E6B6E6F776E00
Username:               info@testdomain.tld
Fullname:               info test
Emailaddress:           info@testdomain.tld
Active:                 yes
Administrator:          no
Address book:           Visible
Auto-accept meeting req:no
Out Of Office:          disabled
Server version:         8.7.80
Mapped properties:
        PR_EC_ENABLED_FEATURES  mobile; outlook; webapp
        PR_EC_DISABLED_FEATURES imap; pop3
Current user store quota settings:
 Quota overrides:       no
 Warning level:         unlimited
 Soft level:            unlimited
 Hard level:            unlimited
Current store size:     0.00 MB
Groups (1):
        Everyone

thctlo

@fbartels said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

kopano-cli --list-users

hmm…

kopano-cli --list-users

no output.

kopano-admin --list-users
And all my users are there.

i tested again the user creation, but again no store and no errors wil running the command.
A missing python package? of problems due to the upgrades, you did a clean install.

i think if we find no output problem of the kopano-cli --list-users then i expect the store creation to be fixed also.

Im open for your suggestions on debugging this.

some extra info.
i’ve configured
https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#configure-language-for-store-creation
/etc/kopano/admin.cfg contains : default_store_locale = nl_NL.UTF-8

And i dont see any errors in the logs…

fbartels

@thctlo since you’re using a supported version I would recommend to get in direct contact with our support on this.

thctlo

@fbartels
Are you sure? Because this is a “contribute” (supported) version.

I have no problem with reporting it and helping out to get this fix.
I just dont have support blocks.
Thats why i report here.

fbartels

@thctlo one of the requirements of said version is:

are only allowed to be used for private installations or development purposes.

When you are talking about multiple companies, that does not sound like a private installation to me.

But since the same command works for me on a test installation I anyways suspect that this is a local configuration error in your system and not a general issue.

thctlo

@fbartels said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

that does not sound like a private installation to me.

Hai Felix,

Ow yes it is, and i have about multiple personal domains, i do a lot of testing and i report back a lot.
Im testing now the kopano with SQL, next ldap then samba4 but if thats a problem, license wise, tell me, i’ll remove it.

It only makes i harder for me to debug, now im compairing between these 2. (communitie and contributed)
Its your choice, since you gave me the contributed license.

jm23

Hi thctlo,

I had a similar error. My situation with active-directory are a complete sync of all users and groups. I see any of my user with “kopano-cli --list-users” but no one has a store. Login to webapp has the same MAPI_E_NOT_FOUND.

My way to resolve was:

Backup current database
Edit 127.0.0.1 to 0.0.0.0 in /etc/mysql/mariadb.conf.d/50-server.cnf
Delete all entry in database (kopano) under /tables/users
systemctl restart mysql
systemctl restart kopano-server
wait and jump

Now all stores are created.

thctlo

Hi JM, thank you for the reply.
Its fixed, but its in my opinion a bug, i just can’t find the exact source of it, but i expect it to be the same as @samba lots of bug due to python2 => 3 changes.

@fbartels
i missed this part from you.
But since the same command works for me on a test installation I anyways suspect that this is a local configuration error in your system and not a general issue.

yeah, sure all my clean install also work everytime, i suggest that you keep a server installed, add a few users and upgrade it every release.

After lets say 5 updates, i suggest, you remove kopano from you server.
install mlocate, run updatedb en run : locate kopano
And be amazed with the “left overs” that might be the cause these problems.

This might sound a bit hars, in trying to not offend here, but when i do the same commands on a :

zarafa-7.2 it works fine.
kopano-8.1 ( i skipped 8.0) works fine.
kopano-8.2 works fine.
kopano-8.4 ( i skipped 8.3) works fine.
kopano-8.5 works fine.
kopano-8.6 works fine.
kopano-8.7 it does not work.

I did say, im using this server since 7.2 without any problems, and older users did work and keept working after the upgrade. I’ve reviewed all config changes and match them again.
Im not a complete newbe, i might not know all but i know a lot.

This is a bug in 8.7.0 and i say it related to python modules which are not in the dependicy list of the packages and/or you have these installed and/or a left over from a previous install.

lets start here.

The /usr/sbin/kopano-cli file

#!/usr/bin/python3
# SPDX-License-Identifier: AGPL-3.0-or-later
import sys
import kopano_cli
from kopano_cli import __version__

if __name__ == '__main__':
    sys.exit(kopano_cli.main())

I would start with, fix the interpeter. #!/usr/bin/env python3
and… here it stops for me. . i dont know python. :-( sorry… we cant know everything…

The difference kopano-admin is a binary, kopano-cli not, so thats why i suspect missing packages.

Felix, if you dont mind, could you export you package list installed and pm it or post it somewhere.
I’ll compaire it with my server and try again, if i found the missing package, i’ll report it back.

I suspect an other package, which you have installed, has the depend to the file that i’m missing.

Any other suggestions are apriciated to get this fixed, not for me, i have a good work around.
But to make kopano a better product.
That simple.

I’m just trying to help out here.

jm23

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):
…python2 => 3 changes…

I think so too.

An example: /usr/sbin/kopano-localize-folders

I start with the installed file from repo “kopano-localize-folders -u username --lang de_DE.utf8” and get an mapi-error.

After i replace the content in this file with one from here (switching from master to python3), everything went through.

fbartels

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

This might sound a bit hars, in trying to not offend here, but

Isn’t that the same trope as saying “i am not racist, but I am going to say something racist right now, but you’re not allowed be be angry about it since I am not a racist”?

Anyways…

I see that you are trying to help, but at least for me it does not help that much. Of course I have also older systems and also systems that already made the transition from python2 to python3. But in my cases I do not experience the same issue you are describing.

Also just to entertain the idea I removed all kopano packages from a testing environment (apt remove kopano-* followed by a apt autoremove) ran your suggested mlocate command and all that was left for me were old configuration files (that you usually want to keep in case you reinstall), systemd units, data in /var/lib/kopano. So nothing that will interfere with an upgrade program wise.

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

I would start with, fix the interpeter. #!/usr/bin/env python3
and… here it stops for me. . i dont know python. :-( sorry… we cant know everything…

yeah. that changes exactly zero in how the program will behave in the end.

@thctlo said in Webapp - Unknown MAPI Error: MAPI_E_NOT_FOUND (kopano 8.7.0.0-0+1.1 / webapp 3.5.2 ):

The difference kopano-admin is a binary, kopano-cli not, so thats why i suspect missing packages.

If there is something missing in python, then there is usually an error message. But what in the end creates the store is not python, but again c code (triggered through the server).

@jm23 you did not mention which version you are running at the moment. There are indeed still some issues due to the python3 transition in the 8.7.0 packages. We are currently chasing behind a different issue that keeps us from releasing a 8.7.1 (which has a lot of, if not all, of these issues resolved). For the meantime there are updated packages in the core:pre-final repository for those willing to give feedback and hurting from these python changes.

jm23

@fbartels
Excuse me. I did not think necessary because I had replied in “MAPI_E_NOT_FOUND kopano 8.7.0.0-0”.

fbartels

@jm23 no problem.