none
Outlook error Error is [0x80070005-00000000-00000000] RRS feed

  • Question

  • Outlook error when sending email from shared mailbox or from a user who has full access to a mailbox.

    This is the error users keep receiving when trying to send email from someone mailbox that they have full access to. They can read emails file just sending is a problem.

    Error is [0x80070005-00000000-00000000]

    Wednesday, June 5, 2013 8:17 PM

Answers

  • Happens to only specific mailboxes that had the older exchange shared mailbox mounted to their outlook and their mailboxes copied over to 2013. The work around i found was to setup those shared mailboxes first before creating their personal mailbox profile. And set their personal profile to default after the shared mailboxes were all working. No idea why this is happening, but if mount or open someones mailbox that has full access with a new user I do not run into these issues, it must be an artifact from migration of these users mailboxes and they still attempting to use old paths for exchange server for sending... there is no problem with grabbing new mails .. So it is/was a bit tricky issue but my workaround it seems to be working so far.
    • Marked as answer by Tony Chen CHN Friday, June 14, 2013 1:42 AM
    Wednesday, June 12, 2013 6:57 PM

All replies

  • Make sure your Outlook client is fully updated.

    In general, error 0x80070005 meams the issue is related to permission issue. Try to remove and re-add the full access permission from EMC to check if you still receive the NDRs.

    By the way, does it happen in specific user/mailbox or in all of mailbox. Thanks.

    Tony Chen
    TechNet Community Support


    • Proposed as answer by ElRandyTech Wednesday, May 18, 2016 1:11 PM
    Friday, June 7, 2013 7:00 AM
  • Happens to only specific mailboxes that had the older exchange shared mailbox mounted to their outlook and their mailboxes copied over to 2013. The work around i found was to setup those shared mailboxes first before creating their personal mailbox profile. And set their personal profile to default after the shared mailboxes were all working. No idea why this is happening, but if mount or open someones mailbox that has full access with a new user I do not run into these issues, it must be an artifact from migration of these users mailboxes and they still attempting to use old paths for exchange server for sending... there is no problem with grabbing new mails .. So it is/was a bit tricky issue but my workaround it seems to be working so far.
    • Marked as answer by Tony Chen CHN Friday, June 14, 2013 1:42 AM
    Wednesday, June 12, 2013 6:57 PM
  • tony, i realized the problem is back again this week. Nothing on exchange  changed but seems like the users unable to send again. This is one weird one. Can only read the mailboxes emails but cannot send from it. It was working last week and this week after exchange reboot looks like its back. Anyone ever run into this error and how was it resolved properly ?

    Monday, June 17, 2013 6:40 PM
  • We have it happening after migrating from a POP email to Office365 but it only happens when trying to send to an email address that just forwards to another real email.  The alias is JCohen@ourdomain.org and the real email that JCohen forwards to is JKohn@ourdomain.org
    • Proposed as answer by vdever Thursday, October 3, 2013 1:03 PM
    Monday, August 26, 2013 6:41 PM
  • Strangely enough, this only happens for one of our users from Outlook(Desktop).


    Tuesday, September 10, 2013 9:45 AM
  • We have been running in to this issue as well,  I have fixed this issue by deleting the offline address book folder and by  hitting the X on the type ahead. 

    I hope this helps people. 

    the path to the offline address book is  %appdata%\local\Microsoft\outlook\  make sure outlook and lync is closed and delete the offline address book folder re open outlook and try again.

    • Proposed as answer by Luxus Chris Thursday, January 7, 2016 5:46 PM
    Friday, October 4, 2013 2:49 PM
  • Yeah, you can solve it temporarily that way. This is the only way it got solved it permanently for me though:

    http://blog.groundx.se/error-0x80070005-00000000-00000000-outlook-2013/

    Thursday, November 7, 2013 1:22 PM
  • In O365, I just had to grant the user "Send As" permissions.  Overlooked that as we assumed the "Full Access" token would cover it.
    • Proposed as answer by Berserk41 Wednesday, July 9, 2014 5:55 AM
    • Unproposed as answer by Berserk41 Wednesday, July 9, 2014 5:55 AM
    • Proposed as answer by Protie Oy Wednesday, June 24, 2015 12:01 PM
    • Unproposed as answer by Protie Oy Wednesday, June 24, 2015 12:01 PM
    Wednesday, March 26, 2014 8:21 PM
  • Happened to me on Outlook 2013 & Exchange 2013.

    What worked for us was to disabled cached mode, restart outlook, enable cached mode, restart outlook.

    Hopefully this will help someone.

    • Proposed as answer by GerHalp Wednesday, February 17, 2016 10:13 AM
    Tuesday, July 1, 2014 4:09 PM
  • I ran into this after migrating mailboxes to Exchange 2013.  My mailbox migrated just fine, but my second and third did not work from my Outlook.  None of the suggestions worked, including deleting and recreating one of the Exchange accounts in my Outlook.  Eventually I figured out that even though Outlook was allowing the account setup and password I was typing, it was not using them. I had Send and Full Access permission to the mailbox, from years ago before Outlook 2010 allowed multiple accounts, and Outlook was using my credentials to connect and not the password I was providing.  Setting the account's More Settings/Security/Always prompt for logon credentials option forced it to ask, then I could turn that option off again.
    Monday, July 21, 2014 3:43 PM
  • I had this error when moving a client from On Premise exchange to O365.

    All the correct Send as permissions had been set in powershell. We had to re download the global address list and each user had to pick the address they wanted to Send As from the Global address list(rather than typing it for example). After that it worked fine and i was able to hide the distribution groups once again in the GAL so its looked tidy.

    Wednesday, October 1, 2014 8:24 AM
  • Just ran into this problem.  We solved it by also granting the users Send-as permission.  I'm not sure why Send-as trumped Full Access, though.
    • Proposed as answer by ElRandyTech Friday, November 21, 2014 8:37 PM
    Friday, November 21, 2014 8:37 PM
  • Full Access grants permission to access the mailbox and the mailbox folders and is an Exchange property.

    Send As permission grants AD access to send as the mailbox and is an Active Directory property.

    For example examine the EMC command for granting send as access:

    Add-ADPermission "Mailbox Name" -User "Domain\Username" -Extendedrights "Send As"

    Source: http://technet.microsoft.com/en-us/library/bb676368(v=exchg.141).aspx

    • Edited by Thorr686 Tuesday, January 13, 2015 10:27 AM
    • Proposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
    • Unproposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
    • Proposed as answer by Indy S Thursday, July 23, 2015 5:43 PM
    Tuesday, January 13, 2015 10:25 AM
  • I had this error today, not for the first time. But this time I realized that it occurred on Resend of a message which had been originally sent via an expired MS Office365 subscription (same domain as now).

    So I made a new Resend AND chose From explicitly (seemingly the same thing). The message went off OK.

    Friday, March 27, 2015 8:52 AM
  • If permissions are correct try removing the name from the from dropdown by pressing the X and then re-add the address.

    this normally happens if the from address has changed it's alias

    • Proposed as answer by rod.fuller Tuesday, May 26, 2015 8:49 PM
    Tuesday, April 7, 2015 1:25 AM
  • We also resolved it by removing the Send As name and adding it back in.
    Tuesday, May 26, 2015 8:48 PM
  • I recently had this issue with a user trying to forward a contact. Tried all the remedies and nothing worked. Ended up being a corrupt contact card. After deleting and recreating the card it worked just fine. 
    Wednesday, July 29, 2015 1:57 PM
  • We experienced this error with several people within a team, whose mailbox got migrated from one to another domain, and Exchange 2010 to Exchange 2013.

    All of them except one do have SendOnBehalf rights.

    Thank´s to everyone for coming up with the solution!

    1. Open a new e-mail

    1.1 Write down the additional mailbox into the "To..." field

    1.2 Left-click the "x" right of the suggested contact

    Try again to send the e-mail successfully. Proceed, if you fail again ...

    2. Close Outlook, Lync and all other applications which have access to the local Address Book file

    3. Delete the Folder %appdata%\local\Microsoft\outlook\Offline address Book

    Indeed you do delete a localy cached contact with this method, which seems to be the reason for the error message.

    Monday, September 21, 2015 12:56 PM
  • For me deleting the OAB worked fine.Before, I was only able to "sendas" from a shared mailbox when I selected the "From" sender directly from the GAL.

    Then, I was able to send the first mail, but when I wanted to send a 2nd mail by selecting the address added from the GAL before from the from field, I received the error 0x80070005-0x0004dc-0x000524 .

    Of course I checked before that I have added FA and Send as perm.

    So deleting the OAB did the trick for me. (Win 10 Prof, Outlook C2R 2016)

    KR

    Chris

    Thursday, January 7, 2016 5:49 PM
  • Thanks, Egg, this is the solution that worked for me.  Simple and quick.
    Thursday, January 14, 2016 10:18 PM
  • El error estriba en es una falta de conexión entre la "lista global de direcciones sin conexión" y la "lista global de direcciones" (el que realmente consulta al servidor de Exchange).

    En principio te indican que borres el **\Local\Microsoft\Outlook\Offline Address Books y vuelvas a descargar la “libreta de direcciones sin conexión”,

    Pero resulta que si tienes oculta la dirección desde la que intentas enviar el correo, no la actualiza, por lo que finalmente tienes que hacerla visible, seleccionarla desplegando el "Enviar desde otra direccion" y elegirla de la "Lista global de direcciones"

    Y entonces ya si te deja volver a enviar sin entrar en la “lista global de direcciones”

    Ciao, Ciao

    Wednesday, February 17, 2016 7:56 AM
  • Recently one of my user had a  similar issue. User was unable to send and receive emails through shared mail box and the error message he received was 0x80070005-00000000-00000000.

    In such a case check whether the user is a remote user or his mail box is located on premise.

    This happens when the user has his mailbox on cloud and the study folder is located on premise.

    As a work around you can  to login to OWA web based app to access the shared folder. Try to send receive email.

    It works.

    Friday, June 24, 2016 3:40 PM
  • It happened to me when I provided Full Access to the mailbox and not the Send As permission from ECP, and the person was watching the inbox of the other mailbox and when tried to answer, the On Behalf was showing the not-owner e-mail address. Hopefully my message wasn't too confusing.

    Friday, October 27, 2017 7:25 PM
  • We had this error as well using Exchange 2013 and outlook 2010 and 2013. 

    The clients had full access and OWA worked fine there however in outlook it was giving the error.

    FIX:

    - Start a new E-mail 

    - Click the drop down From Box

    - Delete the affected account by pressing the X

    - click Other Email

    - Find it in the list and select it

    It will work now (or did for us) 

    Thursday, March 15, 2018 1:50 AM
  • That worked for me.  Thank you so much.
    Tuesday, December 18, 2018 8:45 PM