Dear all,

I have users with 2nd mailbox attached to their Outlook, after movement the mailboxes to Exchange 2013 they're no longer able to send any e-mails from the 2nd mailbox

And they also get this ERROR:0x80070005-00000000-00000000 

If I attach the same mailbox to my Outlook, I have no problems with sending e-mails. 

Does anyone know what might that be?

Thank you

Hello

tip: update offline addressbook:

get-offlineaddressbook | update-offlineaddressbook
after update go to client and download full offlineaddressbook
restart outlook and test again.

the thing is that I cannot update offline address book in Outlook, I receive an error message with the code: 0x8004010F

Hello

on exchange 2013 db set offline address book?
check over ecp please servers-->database--> db double click-->client settings
and if empty add offlineaddressbook.
restart outlook client and try download again addressbook

thank you for your suggestion, you were right there wasn't offline address book in DB. I have changed it but the problem is still exists. ((( 

Hello

havent use  a proxy?

https://support.microsoft.com/hu-hu/kb/939765/en-us

I've tried it as well, but still no success (((

Hello

try create new outlook profile

https://support.microsoft.com/en-us/kb/2659085

and check oab url with outlook "test automatic configuration" and oab url copy to internet explorer and try open.

Hello

and if not help check: https://social.technet.microsoft.com/Forums/office/en-US/home?searchTerm=0x8004010F

Hi San,

Thank you for your question.

First of all, we could make sure there are no shared mailboxes which were mounted on outlook, then keep outlook in cache mode to check if the issue persist.

If the issue persist, we could rebuild the profile, then re-add the 2^nd mailbox attachmed to outlook.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Thank you for the answer.

I've also tried to move mailboxes to the Exchange 2010 database and then remove all permissions from the 2nd mailbox. After that I migrated them back to Exchange 2013 database and assigned permissions again, it worked for me as well.