Click to get started.Outlook 2007/2010 SMTP Error 0x800CCC13 With Exchange 2010
8 comment(s)Task '<Account> - Sending' reported error (0x800CCC13) : 'Cannot connect to the network. Verify your network connection or modem.' Say what?
I have been battling the above frustrating error for a few months now, and never actually found a good workaround until today. I started having the issue when I was running Outlook 2010 Beta, so I just shrugged the issue off as an Outlook beta problem. I'm now running the proper RTM version of Outlook, and the issue still exists. I have my primary account setup with Exchange on our Exchange 2010 server, and a handful of POP3/SMTP accounts setup that pull mail down into my Exchange box, and give me appropriate Send As rights for other accounts I need to be able to send from, that exist outside my organization.
Every now and again, I would notice my Outbox had stuck mail in it... pretty unusual for an Exchange box. The only messages that would stick are ones destined out a POP/SMTP account, with a file attachment. After chasing down permission issues, virus scanning, relay permissions, server issues, etc. I was pretty stumped.
The whole problem here is a bug in Exchange 2010, it was present in the Beta version, and is still present as of RTM Update Rollup 3 (will be trying again with Update Rollup 4 when we can appropriately test it). The issue only exists if you do not run cached Exchange mode. If you wish to leave cached mode off (as I do), you can work around the issue if you set your POP3 accounts to deliver mail to an alternate data file, a simple PST. For my purposes, this is fine, I just changed my alternate accounts to forward to my Exchange primary address, so e-mail still makes it to my inbox, but sent mail simply sits under the local data PST file. Once Microsoft gets around to fixing the issue, I'll simply merge the sent folders back into my Exchange Mailbox, and put this issue behind me.
I'm glad I found this useful thread that helped shine some light on the issue. I was approaching the problem from my logical perspective, and that was between my Outlook and the SMTP server... why would the dropping of the mail into my Exchange Mailbox Sent Items have anything to do with this? I'm still not pleased that this bug exists, but at least there's a workaround. This issue only happened when I went to Outlook 2010, because that was the point in which I swapped away from Cached mode.
Comments
Hi, Daniel - I ran into the
Hi, Daniel -
I ran into the same problem this weekend, and it was frustrating to no end. These users still need to use POP3 until they begin hosting e-mail internally in a few weeks. I did install Update Rollup 4 yesterday and it seemed to fix the problem at first -- but not for everyone. At first, NO POP3 e-mail would go out, and would remain stuck in the Outbox. Now most of it seems to go except for an occasional reply, or anything with an attachment. I don't see how MS could release a product with such a major bug and leave it unfixed for so long. Whether they care or not, there will always be people who need to use Exchange and also POP3 who don't want to use the POP3 connector. I'll keep an eye on your blog for updates, and let you know if I find anything out myself.
Another Concerned Exchange 2010 user :(
I managed to apply Update
I managed to apply Update Rollup 4 this weekend, but didn't get around to testing it until this morning. On the two machines I tested, both experienced the same issue.
Thanks for your response and confirmation the issue still exists on your end too. I'll definitely keep an eye out for it, but for this moment, my workaround is keeping my mail flowing just fine.
It did seem like an instant
It did seem like an instant fix at first -- the situation was definitely improved. Unfortunately it wasn't a total fix. I'd found another thread on the issue where they mentioned applying SP1 Beta did not resolve for them, so I skipped that step. I've e-mailed my Exchange contact at MS regarding the issue but haven't heard back yet. I'm having little choice but get them converted away from POP3 sooner than we'd planned, hopefully within a few days. I'll keep you posted and will keep checking back here in the meantime. :)
I have the same issue when
I have the same issue when sending attachments via pop3 accounts
Sending' reported error (0x800CCC13) : 'Cannot connect to Networ
I had the same problem w/Outlook 2010 OS Win 7. Problem was:
Account Settings > E-mail Accounts > E-mail =
"RealName@Pprovider.Net POP/SMPT (Send from this account by default)"
(Set as E-mail Default)
AND Account Settings > E-mail Accounts > Data Files =
"BogusName@Provider.Net C:\User\Name\Documents\Outlook Files\RealName@Provider.pst"
(Set as Data File Default)
I corrected my profile, replacing the bogus name under Data File that also corrected my Error 0x800CCC13.
I had this same exact issue,
I had this same exact issue, but nobody on the interwebs had a solution...I figured one out, but here are my details....
Got an 0x800ccc13 error in Outlook (Environments: 2007 with XP and 7, 2010 with 7) when sending any emails with attachments that totaled over 100kb and the messages would get stuck in the Outbox (all emails without attachments were able to be sent). Also, any received emails with attachments over 100kb would not display those attachments. The users in question were using Google Apps Sync to Gmail, but even simple IMAP and POP profiles for them wouldn't work (no Exchange used). Nothing was wrong with the IMAP connection settings nor with the PST/OST settings for the account, and the users did not have any anti-virus software that scanned incoming or outgoing emails. Running Outlook in Safe Mode didn't fix it, and neither did checking to see if there was a hidden Read Receipt in the PST. Using Msconfig to turn off all extraneous applications and services on startup, doing an uninstall/reinstall with Office, and uninstalling any recent Microsoft updates did not solve it as well.
I found that the issue was only confined to the user profile on that specific workstation (these were domain users, but it could apply to local computer users too)...I would log into the same workstation under a different user, create an Outlook profile on there for the user with the issue, and the error would go away; also, I would log into a different workstation using the credentials of the user in question, and the issue was not there.
As a last-ditch effort before blowing away the user profile and recreating it, I used ProcMon and filtered for the Outlook process...where I found that the user's Temp directory was clogged with files (C:\Documents and Settings\\Local Settings\Temp\ for XP and C:\Users\\AppData\Local\Temp for Vista/7). I had an issue accessing the folder without causing Windows Explorer to completely freeze up, mostly because of the 200,000+ empty temp files that were put in there for some reason...so instead of opening up the folder, waiting for it to load, selecting all of the files to delete, and then permanently deleting all of them, I created a simple WinForms app to delete all of the temp files for me.
Feel free to message me if you would like me to send you the app.
Hola a todos, yo he tenido el
Hola a todos, yo he tenido el mismo problema que uds. Probe de todo, pero finalmente lo termine solucionando muy facilmente. Hice una copia del archivo PST, obviamente para no perder los mail, luego borre el archivo original, di de baja la cuenta y borre el perfil. Finalmente genere un nuevo perfil, cree nuevamente la cuenta y genere un archivo nuevo de datos, y eureka, funciono perfectamente. Entonces procedi a restaurar el archivo pst original y decirle al sistema que guarde los datos ahi y que lo tomo como predeterminado y asi funciono perfectamente. Espero les sirva de ayuda y suerte a todos. Saludos desde Argentina.
Can not send attachments 0x800ccc13 cannot connect to the networ
Thank you this worked great.