This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
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.
to stop wlm from keeping trying to send the stuck e-mail with photos,
Task Manager
Details tab
find wlmail.exe (there may be several instances of it running)
delete them all
delete the e-mail from your outbox
close the programme
I've tried reinstalling the programme
I've tried dicsonnecting and re-connecting to the e-mail account
I've tried all of the attachment options shown above
no joy
I just want it go back to how it was please
Worked!!! Thanks much iFiredog! So appreciative.
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?
[PS] 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.
Thank you for this information and solution, ¡Firedog!
For those reporting that this solution does not work, please realize that it can take a long time for Live Mail to timeout after disconnecting the network cable. In my case, about 20 minutes.
Once that happened, Live Mail prompted to delete the offending outbound message. However, that did not remove it from the actual Outbox folder in Live Mail. That had to also be done manually once in the program's normal user interface.
Anyone know if or when Microsoft will get it fixed?
Not as far as I'm aware.
How do I let Microsoft know I also have this problem? thanks
Vote here: UserVoice
I have the same problem and it has been going on for several days. Anyone know if or when Microsoft will get it fixed? How do I let Microsoft know I also have this problem? thanks
Quite frankly, I think this matter is now quite out of control. Who knows when Microsoft will get around to resolving the issue, but unless they pull their collective fingers out very soon, I believe their many loyal customers will migrate to a competitor who gives them respect and addresses critical bugs when they appear without any excuses. All you can do is pray!
