none
Outlook2016/2019 - The operation failed. after 1908 update RRS feed

  • Question

  • Outlook:

    Microsoft Office Home and Business 2016/2019

    Version 1908 (Build 11929.20254 Click-to-Run)

    Exchange:

    Exchange 2010 SP3 Update Rollup 19

    --

    After updating Outlook to 1908 our users are unable to add attachments or send emails that contain embedded images. You will get the error "The operation failed." when trying to attach any file type and "Cannot send this item" if trying to reply or forward a message with an embedded image.

    We have tried blowing out profiles and reinstalling Outlook, but the only thing that seems to fix it is to revert back to version 1907.

    Is anyone else experiencing any similar issues with the new Outlook 1908 update?



    Thursday, August 29, 2019 5:09 PM

All replies

  • Same issue here on 2 PCs in the office environment. Rolled them back to an earlier version and disabled updates.

    - System 

      - Provider 

       [ Name]  Microsoft Office 16 Alerts 
     
      - EventID 300 

       [ Qualifiers]  0 
     
       Level 4 
     
       Task 0 
     
       Keywords 0x80000000000000 
     
      - TimeCreated 

       [ SystemTime]  2019-08-29T16:44:03.000000000Z 
     
       EventRecordID 1523 
     
       Channel OAlerts 
     
       Computer NAME HERE
     
       Security 
     

    - EventData 

       Microsoft Outlook  
       The operation failed.  
       300032  
       16.0.11929.20254  
       749m 
       0x8004010F  


    • Edited by Bryan W Richter Thursday, August 29, 2019 7:33 PM
    • Proposed as answer by Mark Je74 Friday, August 30, 2019 4:18 AM
    • Unproposed as answer by Mark Je74 Friday, August 30, 2019 4:18 AM
    • Proposed as answer by Mark Je74 Friday, August 30, 2019 4:18 AM
    • Unproposed as answer by Mark Je74 Friday, August 30, 2019 4:18 AM
    Thursday, August 29, 2019 7:26 PM
  • Yep, Rolled Back to 1907 which is Office 2016 version=16.0.11901.20176

    Could try August 13, 2019 Version 1907 (Build 11901.20218), havent tested it. OfficeC2RClient.exe /update user updatetoversion=16.0.11901.20218

    1. Win+R
    2. CMD
    3. cd C:\Program Files\Common Files\microsoft shared\ClickToRun\
    4. OfficeC2RClient.exe /update user updatetoversion=16.0.11901.20176
    5. Disabled office updates


    • Proposed as answer by Mark Je74 Friday, August 30, 2019 4:27 AM
    • Edited by Mark Je74 Friday, August 30, 2019 4:47 AM
    Friday, August 30, 2019 4:27 AM
  • Hi BrandonShmandon,

    If we remove embedded image, will error continues? 

    Currently, I haven’t found official articles which reports this. As a workaround, we can revert to a previous version of Office or use linked images.

    I’ll keep tracking on this issue and post back once I find anything.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Friday, August 30, 2019 5:37 AM
    Moderator
  • Hi.

    We have the exact same problem with the same Outlook and Exchange Server version.

    Sending an email works without attachments or embedded image, if there is an image embedded the client gives the above mentioned error, if we try to attach a file it's the same.

    Friday, August 30, 2019 8:43 AM
  • yes we are having the same issues with 3 of our pc so far. outlook version 1908.
    Friday, August 30, 2019 2:00 PM
  • We are also running Exchange 2010 same patch level. 

    %programfiles%\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe /update user updatetoversion=16.0.11901.20218


    Friday, August 30, 2019 2:07 PM
  • Yep, here too.
    Exchange 2010 on prem. Outlook 1908 can no longer send any html message containing an image.

    Have discovered that changing from online mode to cached mode allows messages to send.  Can anyone else confirm that cached mode works?

    Friday, August 30, 2019 2:15 PM
  • Yes Perry,  removing images allows the message to be sent, as does converting to plain text (which removed images).  We've discovered that changing Outlook from Online mode to Cached mode allows html messages with images to be sent normally.
    Friday, August 30, 2019 2:20 PM
  • We have the same issue. Same Exchange and Office version. The only thing that worked for us was rolling back to Version 1907 (Build 11901.20218)

    Friday, August 30, 2019 2:39 PM
  • We have alot of outlook with this new update. Alot of then are not the clicktorun version. I hate to uninstall and reinstall. Is microsoft doing anything about it?
    Sunday, September 1, 2019 1:35 AM
  • Same issue here but I'm running Exchange 2010 SP3 Rollup 29 (installed mid-July) and the issue has only started since update 1908.
    Monday, September 2, 2019 8:43 AM
  • Same issue here with ca. 30 Clients and an up-to-date Exchange 2010.


    Monday, September 2, 2019 10:19 AM
  • Same issues at our Exchange 2010 / Office 365 customers.

    Patchlevel Exchange 2010 doesn't seem to matter. It's in the latest update for Office 365. (1908)

    Did one downgrade of Office 365 and that solved the problem for now. But I'm not looking for downgrading such a big amount of installations.

    I think MS must fix this.

    Monday, September 2, 2019 10:37 AM
  • Same problem here as well. 40+ clients affected, all connecting to Exchange 2010. Users without the 1908-build has no problems.

    Let's hope for a quick fix and better testing by MS in the future ...


    Monday, September 2, 2019 12:08 PM
  • Let's hope for a quick fix and better testing by MS in the future ...

    MS do testing? lol I thought thats why they implemented the delayed update schedules :P Just send it and see how many people whinge here :P 
    Tuesday, September 3, 2019 1:18 AM
  • Same issue here. Outlook 2016 Home & Business (16.0.11929.20254), non-Cached Mode, Exchange 2010 (14.03.0468.000, a.k.a. SP3 Rollup 29)

    Turning on Cached Mode fixes the problem. End user was recently changed to non-Cached Mode because their calendars weren't syncing for days at a time.

    Confirmed that using the below command in an elevated command prompt allowed attachments in non-Cached Mode:

    %programfiles%\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe /update user updatetoversion=16.0.11901.20218

    Tuesday, September 3, 2019 2:09 AM
  • Hi All,

    I got the chance to test with Exchange 2010 account(Online mode) on Office 365 1908 and got following results:

    1. When I try to send an email with pictures, I receive this error:

    2. If I try to insert a attachment, I receive this error:

    Is this the same as yours? 

    Everything works normally under Cached Exchange mode. I'll try to submit it in an internal way. Any updates, I'll post back.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, September 3, 2019 6:53 AM
    Moderator
  • Perry,

    Yep that's about the size of the problem...

    A quick fix would be nice.

    Chris

    Tuesday, September 3, 2019 9:04 AM
  • Hi, 

    I can confirm that changing to cached mode works. I did it on all computers here in my network. 

    Tuesday, September 3, 2019 2:46 PM
  • We have the same issue. Exchange 2010 and outlook 2016, 2019, 365. Enabling Cached mode does appear to be a work around.

    Jonathan Icenhour

    Tuesday, September 3, 2019 6:14 PM
  • Perry,

    This is our exact issue as well.

    Thanks,


    Jonathan Icenhour

    Tuesday, September 3, 2019 6:17 PM
  • Client facing same issue.  Exchange 2010 Update 29, Office 365 ProPlus build 1908. Enabling cache mode works, but since it's an RDS environment this isn't an option.  Will try downgrading.
    Tuesday, September 3, 2019 11:08 PM
  • For us, it doesn't matter if the email is composed in HTML, Rich Text or Plain Text and the type of attachment doesn't matter either, even a simple notepad text file cannot be attached.

    Is this not an issue with Exchange 2013, 2016 or 2019?


    RF1983

    Wednesday, September 4, 2019 5:03 AM
  • Same issue here. We´ve experienced this on Outlook 2016 and Outlook 2019

    Since our customers have different Exchange servers and CU(s) running, it is unlikely to have anything to do with Exchange.

    I will try to uninstall the latest Office/Outlook update.

    Wednesday, September 4, 2019 8:04 AM
  • We are part way through moving mailboxes from Exchange 2010 to 2016 and the only affected users are the ones who still have their mailbox on Exchange 2010. When a user reports this issue then we're moving the mailbox onto the Exchange 2016 server and the issue goes away.

    At the moment we are trying to avoid cached exchange mode.

    Wednesday, September 4, 2019 11:08 AM
  • This came from a colleague

    Here’s something to try:

    On the machine of the affected User, edit the reg below

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\CDNBaseUrl

    Change from:

    (Monthly Channel)

    CDNBaseUrl = http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60

    To:

    (Semi-Annual Channel)

    CDNBaseUrl = http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114

    Then Do 'Update Now' in Office, and hopefully it'll revert from

    Version 1908 (Build 11929.20254)

    to

    Version 1902 (Build 11328.20392)

    Refs:

    https://docs.microsoft.com/en-us/officeupdates/monthly-channel-2019

    https://docs.microsoft.com/en-us/officeupdates/semi-annual-channel-2019

    https://docs.microsoft.com/en-gb/sccm/sum/deploy-use/manage-office-365-proplus-updates#change-the-update-channel-after-you-enable-office-365-clients-to-receive-updates-from-configuration-manager

    Wednesday, September 4, 2019 1:48 PM
  • Is there any word from Microsoft on this? Oddly, not all of our users on the 1908 version were affected, but the number of affected users grew each day, and rolling back to 1907 always fixed it. We ended up rolling back to 1907 for everyone.

    We disabled cached exchange mode in GP, because it causes other problems for us.


    • Edited by R0w-n Wednesday, September 4, 2019 4:16 PM
    Wednesday, September 4, 2019 4:15 PM
  • Hi all,

    The Outlook Team just made a change from the service that should mitigate the issue.  It may take another hour for that change to propagate.  To confirm that the change mitigates the issue you will need to restart Outlook a couple times for it to pick up the change from the service.

    Wednesday, September 4, 2019 5:38 PM
  • How do we get the fix?  Will we have to manually update the client?
    Wednesday, September 4, 2019 6:15 PM
  • force ran updates and now it works again in Build 1908
    Wednesday, September 4, 2019 6:26 PM
  • @Gabriel Bratton

    Are you able to clarify what you mean by "mitigate?" What behavior should we expect to see? Also, is there any way for us to confirm that the change in service was picked up?

    • Edited by R0w-n Wednesday, September 4, 2019 6:28 PM
    Wednesday, September 4, 2019 6:27 PM
  • @R0w-n,

    After restarting Outlook the issue should no longer occur.  There is not an easy way to see the service change without getting log files.  Please test and check if you are still seeing the issue.  

    Wednesday, September 4, 2019 8:34 PM
  • The issue still occurs. Thank you
    Wednesday, September 4, 2019 8:56 PM
  • Hi All,

    Update here: This issue has been fixed.

    The Outlook Team disabled the flight that was causing the issue "Microsoft.Office.Outlook.Attachments.LoadAttachmentsBackground".  The customer will need to restart Outlook to pick up the change. 

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, September 5, 2019 1:49 AM
    Moderator
  • Do we need to update to get this fix?
    Thursday, September 5, 2019 3:11 AM
  • This is still an issue after restarting Outlook. I also tried checking for Office updates, running Outlook in safe mode, and creating a new profile.

    Edit: We use Office 365. If it matters, we have exchange server 2010 on prem

    • Edited by R0w-n Thursday, September 5, 2019 8:27 PM
    Thursday, September 5, 2019 12:39 PM
  • Please provide a fix for non 365 affected users. People who are on Office 2016 and 2019 are still having the issue.
    Thursday, September 5, 2019 6:08 PM
  • Exch 2010 on prem and office 2016/19 all working now on 1908.11929.20254 C2R after new updates were pushed out.

    i had issues with images and any attachments

    Thanks

    • Edited by pa_an_br Saturday, September 7, 2019 9:29 AM update
    Saturday, September 7, 2019 9:28 AM
  • Does anyone still encounter this issue? I got the internal information that this issue was fixed already.

    If you are still having this problem, please share the detailed version of Exchange server and Outlook client here.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, September 9, 2019 8:39 AM
    Moderator
  • I am still affected. The rest of our users are back one version of Office via GP. I'm the only one not in that GP, for testing, and I still have the issue. Until this is fixed, we can't permit Office updates.

    Exchange Server 2010 on prem. My Office version is 1908 (Build 11929.20254), monthly channel

    Monday, September 9, 2019 4:55 PM
  • Does anyone still encounter this issue? I got the internal information that this issue was fixed already.

    If you are still having this problem, please share the detailed version of Exchange server and Outlook client here.

    Regards,

    Perry

    Still no good here with Online Mode or Cached Mode and Office 365 Version 1908 (Build 11929.20254 Click-to-run)

    Exchange 2010 Update Rollup 29 on prem.

    The problem started for us with 1907 Build 11901.20080.

    I've tried all the Monthly Targeted builds below as they've been coming out and none have worked

    August 25, 2019
    Version 1908 (Build 11929.20254)

    August 16, 2019
    Version 1908 (Build 11929.20182)

    August 13, 2019
    Version 1908 (Build 11929.20114)

    July 27, 2019
    Version 1907 (Build 11901.20176)

    July 25, 2019
    Version 1907 (Build 11901.20156)

    July 22, 2019
    Version 1907 (Build 11901.20120)

    July 15, 2019
    Version 1907 (Build 11901.20080)

    If I downgrade to July 9, 2019 Version 1906 (Build 11727.20244) all works ok again

    Cheers

    Tuesday, September 10, 2019 7:07 AM
  • Is there any update on this? The most recent patch, Office Version 1909 (Build 12026.20108) did NOT fix this.
    Tuesday, September 10, 2019 5:57 PM
  • Is there any update on this? The most recent patch, Office Version 1909 (Build 12026.20108) did NOT fix this.

    @R0w-n does running these get it temporarily working again for you? (obviously back on 1906 Build 11727.20244 though)

    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun

    officec2rclient.exe /update user updatetoversion=16.0.11727.20244



    • Edited by Grubsy Tuesday, September 10, 2019 11:05 PM fix formatting
    Tuesday, September 10, 2019 11:04 PM
  • We already rolled back our users (excluding me, for testing) to 1907 and disabled updates to temporarily fix this. We can't hold off on Office updates forever, though.
    • Edited by R0w-n Wednesday, September 11, 2019 1:16 PM
    Wednesday, September 11, 2019 1:16 PM
  • We are also experiencing this.  We have had to roll back to the previous version and switch off office updates, but we don't want to have to do that forever.  We are running Exchange 2010 On Prem and so any update for O365 is no fix for us.

    Whatever was fixed in the update for O365 must also be fixed for Outlook clients that connect to Exchange On Prem.

    When are we going to get a fix Microsoft?  Thanks.

    Wednesday, September 11, 2019 3:40 PM
  • I had the problem, reverted back to 16.0.11901.20218. I just pushed 16.0.11929.2054 out to my machine, and it's working.  Going to try a partial deployment and see what happens.

    Wednesday, September 11, 2019 5:18 PM
  • build 11929.20300 is now working for us.  (online mode, Exchange 2010 on-prem, html messages with images)
    Thursday, September 12, 2019 8:00 PM
  • Does anyone still encounter this issue? I got the internal information that this issue was fixed already.

    If you are still having this problem, please share the detailed version of Exchange server and Outlook client here.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tried September 10, 2019 Version 1909 (Build 12026.20108)

    Still no good here. Had to revert back to 1906

    I see another version is out. Will try that and report back

    September 16, 2019 Version 1909 (Build 12026.20190)



    • Edited by Grubsy Tuesday, September 17, 2019 3:19 AM
    Tuesday, September 17, 2019 3:18 AM
  • It works if cached exchange mode is enabled, but cached exchange mode is not an option for us, due to the bugs it causes. In fact, we disabled it via GP a while ago.
    Tuesday, September 17, 2019 1:21 PM
  • Tried September 10, 2019 Version 1909 (Build 12026.20108)

    Still no good here. Had to revert back to 1906

    I see another version is out. Will try that and report back

    September 16, 2019 Version 1909 (Build 12026.20190)



    So we have some improvement. Sending, replying, forwarding emails seems to work all ok now.

    Only issue is we can't add new attachments. Forwarding an existing attachment works ok.

    I can say 100% but the user testing thinks it was actually like this with 12026.20108 also.

    Update: I just asked her to send me a screenshot of the error pasted in the body of the email. The clicking send issue returned. Deleted the image and she could send fine again. So maybe no improvement at all :(

    Tuesday, September 17, 2019 10:52 PM