I had the same thing, I went to my mail clicked on the out going box to make sure it was empty and then turned my computer off and then back on, no more message now. There might be other ways to get rid of the message, but this worked for me.
Photo email feature broken
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
103 answers
Sort by: Most helpful
-
Anonymous
2015-07-13T12:14:59+00:00 -
Anonymous
2015-07-13T02:06:52+00:00 Thanks to all for the help in solving this problem. I got rid of the 'stuck email..., my outbox is now empty.....and email in WLM 2012 works just fine..........................BUT......when I close the program, I still get a message telling me that there is unsent email in my outbox, and asking if I want to send it! Groan! I re-checked the outbox and there is nothing in it. How do I get rid of this message?
SeasiderWR
-
Anonymous
2015-07-12T17:54:54+00:00 ...
Roll back a web UI update for Microsoft services (Outlook.com, OneDrive, etc.) for nearly a half billion people when it only impacted at best less than a few million using a 5 yr old legacy email application?
- Photo email using OneDrive was first introduced in the 2nd quarter 2010
The issue wasn't WLM a legacy application last updated in Feb 2013 or the OneDrive desktop app or the Photo email engine...but code impacting the backend server's ability to handshake with the local email client.
Yes, it probably was overlooked relative to WLM's legacy email client Photo e-mail feature and needed to be resolved......but roll back an entire web UI update that improved the feature set and experience for 250-500 times the population of the impacted and local only end-user base.
As Homer Simpson would say when realizing how incredulous that sounds.... Doh!
I'm well aware that the issue was caused by a modified response after the images are uploaded to OneDrive.
Yes, they should have done a rollback. The numbers don't matter. That's exactly the problem. They should never, ever matter. That said reality necessitates that they do but one has to be very careful. And that's not what happened here.
If you re-read what I posted you'll understand I'm not even shooting at the one who broke this code, the one that didn't write the automated test, the one that didn't QA this etc. etc. I'm blaming the manager(s) who didn't take the correct decision.
An update to existing software should never impact existing users. If it does a rollback needs to be considered.
Does the update cause a visual glitch (typo, visual disruption like a short flicker whatever, an action that previously took a few seconds now taking half a minute etc.) then no, no rollback.
In this case however a previously functioning feature is now entirely broken for the end user. That's a giant red flag and warrants an immediate rollback.
I don't give one flying f*** if that means updating 10000 servers and takes a while. If the infrastructure or methods to perform that rollback aren't in place at the moment then that's another issue entirely and needs to be adressed ASAP as well.
Here, I'll make a Nostradamus-like prediction that will also hopefully make my reasoning make more sense:
Some time after Windows 10 is rolled out, they'll perform an update to the login routine that causes all the on-line functionality to be broken on the Client-side with the bug being on the server-side.
They won't perform a rollback and the functionality will remain broken for a set amount of time (because the issue is perceived to be a lot more important than the Photo publishing feature they'll throw more manpower at it).
Good luck Microsoft, you've still got a long way to go and a lot of lessons to learn.
Kind regards,
Bart
Past history, if you've actually been using the application for this specific issue, indicates that fixes are done to address a minor population before a rollback removing other features for the majority population not even using the impacted application.
The comment "...a previously functioning feature is now entirely broken for the end user."
- In case you missed it -'is' is now 'was'. i.e. fixed without a need to rollback anything
Before predicting or complaining about the past which at best provides nothing more than entertainment value for discussion sake it doesn't negate what everyone agrees to by use of the application software and the integrated services - the TOU
- No assurances to the accuracy or results of any output by use of the software. Nor does it preclude MSFT's ability to add or remove features without end-user approval.
Bottom line...you, I and everyone by use of the software and its integrated services agree to allowing MSFT to choose the path for deployment, improvement, removal and corrective action.
- which also indicates MSFT's right to, if desired, deprecate the entire 'legacy' no longer supported Windows Essentials product line and its available features (e.g. photo email, contact/calendar sync) using the web services (e.g. OneDrive, People, Calendar) at any point in time deemed necessary. In fact at least three more features will disappear in the near future - the use of DeltaSync Htpp protocol in Windows Live Mail when Outlook.com accounts move to the Office 365 platform impacting the use of the protocol and the loss of synchronization.
Rather than complain about what should be done or predicting the future...it might be more appropriate to devote those efforts to using the alternative and supported MSFT products (Outlook.com, Outlook 2010 and later).
-
Anonymous
2015-07-12T10:31:16+00:00 ...
Roll back a web UI update for Microsoft services (Outlook.com, OneDrive, etc.) for nearly a half billion people when it only impacted at best less than a few million using a 5 yr old legacy email application?
- Photo email using OneDrive was first introduced in the 2nd quarter 2010
The issue wasn't WLM a legacy application last updated in Feb 2013 or the OneDrive desktop app or the Photo email engine...but code impacting the backend server's ability to handshake with the local email client.
Yes, it probably was overlooked relative to WLM's legacy email client Photo e-mail feature and needed to be resolved......but roll back an entire web UI update that improved the feature set and experience for 250-500 times the population of the impacted and local only end-user base.
As Homer Simpson would say when realizing how incredulous that sounds.... Doh!
I'm well aware that the issue was caused by a modified response after the images are uploaded to OneDrive.
Yes, they should have done a rollback. The numbers don't matter. That's exactly the problem. They should never, ever matter. That said reality necessitates that they do but one has to be very careful. And that's not what happened here.
If you re-read what I posted you'll understand I'm not even shooting at the one who broke this code, the one that didn't write the automated test, the one that didn't QA this etc. etc. I'm blaming the manager(s) who didn't take the correct decision.
An update to existing software should never impact existing users. If it does a rollback needs to be considered.
Does the update cause a visual glitch (typo, visual disruption like a short flicker whatever, an action that previously took a few seconds now taking half a minute etc.) then no, no rollback.
In this case however a previously functioning feature is now entirely broken for the end user. That's a giant red flag and warrants an immediate rollback.
I don't give one flying f*** if that means updating 10000 servers and takes a while. If the infrastructure or methods to perform that rollback aren't in place at the moment then that's another issue entirely and needs to be adressed ASAP as well.
Here, I'll make a Nostradamus-like prediction that will also hopefully make my reasoning make more sense:
Some time after Windows 10 is rolled out, they'll perform an update to the login routine that causes all the on-line functionality to be broken on the Client-side with the bug being on the server-side.
They won't perform a rollback and the functionality will remain broken for a set amount of time (because the issue is perceived to be a lot more important than the Photo publishing feature they'll throw more manpower at it).
Good luck Microsoft, you've still got a long way to go and a lot of lessons to learn.
Kind regards,
Bart
-
Anonymous
2015-07-09T00:33:04+00:00 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.
Roll back a web UI update for Microsoft services (Outlook.com, OneDrive, etc.) for nearly a half billion people when it only impacted at best less than a few million using a 5 yr old legacy email application?
- Photo email using OneDrive was first introduced in the 2nd quarter 2010
The issue wasn't WLM a legacy application last updated in Feb 2013 or the OneDrive desktop app or the Photo email engine...but code impacting the backend server's ability to handshake with the local email client.
Yes, it probably was overlooked relative to WLM's legacy email client Photo e-mail feature and needed to be resolved......but roll back an entire web UI update that improved the feature set and experience for 250-500 times the population of the impacted and local only end-user base.
As Homer Simpson would say when realizing how incredulous that sounds.... Doh!