Photo email feature broken

Anonymous
2015-06-25T12:32:01+00:00

Update 14 July 2016

The fault that caused this error for a short period in 2015 was corrected. Users now having trouble using the photo email feature are facing a different problem. The most likely reason is that the Microsoft Account being used has been migrated to the Outlook Mail platform; users will often see an error message including error code 0x8007007A.

Users seeing this error code may not be able to send any messages at all until the offending message has been removed from the outbox (below the account folders in the folder pane). Some alternative methods of sharing pictures are explained in this article: Avoid 'photo email' and send photos by email


Stop press 8 July 2015 13:00 UTC

This bug appears to have been fixed. Once the error has been cleared, it should now be possible to send photo email again. The 'slideshow' view may not work at OneDrive, but the photos can be viewed and downloaded.


In the past two days, a number of users have complained that the photo email feature is no longer working. After creating a photo email and clicking send, the process starts and then stalls.

At this stage, the following is recorded in the program log:

[13:04:26.65] 17d8                 Mail:            Zone_MailChk ERROR: (containx.cpp:3808), failed with 0x800CCE05 <br> <br><br>[13:04:26.65] 17d8                 Mail:            Zone_MailChk ERROR: (containx.cpp:3808), failed with 0x800CCE05 <br> <br><br>[13:04:27.20] 0e78                 Mail:            Canvas_Error [db] <br><br>Photomail failed to complete publish: System.Runtime.InteropServices.COMException (0x80010105):<br> <br><br>The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) <br><br>   at WindowsLive.Writer.PostEditor.PhotoAlbums.PhotoMail.IPublishCallback.PublishComplete(Int32 hr, IHTMLDocument2 newEmail, IPhotomailAlbum photoAlbum) <br><br>   at WindowsLive.Writer.PostEditor.PhotoAlbums.PhotoMail.PhotoMailPublisher.Publish(IPublishCallback callback, IHTMLDocument2 document2, String language, String wpost)

To clear the error, the user must:

1.   Disconnect from the Internet (e.g. switch off Wi-Fi or unplug the Ethernet cable).

      This will stop the program from trying to send.

2.   Remove the message from the outbox (below the account folders in the folder pane).

3.   Click Stop in the send/receive progress window.

      An error message with code 0x80004004 (ABORT) is displayed.

4.   Close the progress window.

Instead of using the photo email feature, users could:

A.     Start a new email message from within Windows Live Mail (Ctrl-N), then use either

Attach files to send images as attachments to the message, or

Insert > Single photo to embed images into the message and apply some formatting.

The images will still be sent as attachments, but they will usually be visible to the recipient

in the body of the message.

B.     Upload the images to OneDrive, then use the sharing options there to send a link to addressees by email.

Will support staff please confirm this fault and inform users about when they may expect the broken feature to be mended?

There is a suggestion on the OneDrive UserVoice page asking the OneDrive team please to reverse the change that caused this fault. The more votes the suggestion gets, the more likely it is that the team will look at the problem.

PS A number of users have posted solutions involving forcefully closing down Windows Live Mail, e.g. by using Task Manager to end the wlmail.exe process or by re-starting the computer. These methods can't be recommended except in the last resort, because Windows Live Mail often conducts internal housekeeping after the program interface has disappeared. If this process is interrupted, damage to the program's databases may result.

The program will normally stop trying to send the message soon after the Internet connection has been broken; clicking once on Working online on the status bar may also speed up the release of the program's handle on the unsendable message so it can be removed from the outbox.

Windows for home | Other | Email and communications

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

103 answers

Sort by: Most helpful
  1. Anonymous
    2015-07-08T21:37:24+00:00

    You're right onto it, Bart!  How fortunate we have been that knowledgeable people like Firedog has been prepared to help us.  Once again, a BIG THANK YOU to him for pulling us all out of the ****.  But what about all those who didn't discover the 'Photo Email Feature Broken' thread and have had to put up with all those unsatisfactory answers and excuses from the online Microsoft techos.  And have we had ANY apologies or explanations from Microsoft?  I haven't seen any. 

    This has disrupted many lives internationally over the past two weeks and is a perfect example of the arrogance of the decision makers at large companies like Microsoft, whose minds seem to be obsessively driven by goals and profits instead of looking after their customers.  Communication and keeping all users in the loop is absolutely key to customer satisfaction and loyalty.  Making mistakes is part of the human condition and therefore excusable; refusing to recognise them and attempting to shift the blame is simply rude and an insult to the intelligence of everyone.

    As for now, has the problem really been fixed?  Could it recur?  Can all those nervous customers feel confident once again?  So far the silence from Microsoft has been deafening.   I wonder if we can ever expect some official explanation or do you think anyone who really matters is even listening?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-07-08T20:37:14+00:00

    thanks. much for fixing.

    I misinterpreted the 'error to be cleared' to mean something other than what it was.

    It works fine now, thanks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-07-08T20:31:22+00:00

    G'day all,

    The problem has been solved.

    I am glad Bill Gates did something!!!

    I offered him to join me for a cold beer if he fixed the problem.

    Wait, I think that is him knocking on my door now!!!

    All seems to be back to normal so I am signing off.

    Cheers Perry from Sunny Queensland.  Fine one day and beautiful the next.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-07-08T19:53:49+00:00

    You have to go back to the top of page 1. The Stop emails link is below the original post.

    Alternatively, visit your profileand, when you're signed in, you'll see Stop emails links for all threads you're subscribed to on the right-hand side of your Activity listing.

    Thanks for your assistance firedog!

    R Larsen

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-07-08T19:14:43+00:00

    While I don't want to defend Microsofts appaling way (as detailed by you) of dealing with the consumer facing side of this issue I do want to comment on the software side.

    I'm pretty sure this bug slipped through QA (I hope someone already added an automated test). That said, once they noticed this bug they should have immediately done a rollback.

    I'm pretty sure they became aware of it the same day or the day after but some manager decided breaking something old while something new (Windows 10) is coming soon is a fair trade off but to that person I want to say the following:

    You sir/mam, are wrong. Your consumers do not currently have Windows 10 in hands, while they do have a broken feature at the moment (or up to today). As long as you guys inside Microsoft don't learn this crucial way of making decisions (customer first, whatever happens), even if this would have meant postponing the Windows 10 release a few days then yes do that but do explain to everyone why, making mistakes (bugs) isn't bad, not delivering quality software is, and breaking something that worked is a big no-no). And yes I'm aware of your (hardware)partners, but they need to learn this same lesson.

    You still aren't communicating openly. Listen to Paul Thurrot. Listen to consumers.

    Whoever at Microsoft reads this; please print this and deliver it on said decision makers desk.

    Thank you.

    Kind regards,

    Bart

    Was this answer helpful?

    0 comments No comments