Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5101
  • Last Modified:

'Sending' reported error (0x800CCC13) : 'Cannot connect to the network. Verify your network connection or modem.'

Exchange 2010 sp1 update rollup 5 in production environment.
I have a couple of users who have multiple email accounts so they are set up with their primary account in Outlook 2003 or 2007 as an exchange account. Their secondary account is set up as a pop account.
When they try to send a message with an attachment from the pop account, they get an error "'Sending' reported error (0x800CCC13) : 'Cannot connect to the network. Verify your network connection or modem.'"
Sending the same message with no attachment works fine.
I have read that Exchange 2010 sp1 was supposed to fix this, but it does not, at least not in my case. Running Outlook in cached mode does stop the error, but I can't run outlook in cached mode on a Windows Server 2003 remote desktop server.

 I can duplicate it all day long by adding a secondary pop account to any machine I have using Outlook 2003 and 2007, Windows XP and Windows 7.

It is obviously a problem with Exchange 2010 and I have seen many posts about this same issue but is there a real fix for it?
0
ljlkrl
Asked:
ljlkrl
  • 6
  • 5
1 Solution
 
AkhaterCommented:
The only quick fix for this i am aware about is to set the delivery of the pop3 account to a pst
0
 
ljlkrlAuthor Commented:
How do I set the pop 3 delivery to a pst file and leave the exchange account delivering to the exchange mailbox on the exchange server?
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
ljlkrlAuthor Commented:
Well that works for Outlook 2007 but I have Outlook 2003 on the remote desktop. That causes another problem though with mail stored in two different places.
I can't do that for someone who uses a laptop and the RDT server because they won't get all their mail on the laptop if they check it on the RDT server.
0
 
AkhaterCommented:
i have no idea if the same can be done on outlook 2003 sorry I never tried it.

emails doesn't have to be stored in 2 places, you can simply forward the inbound to the exchange account so that all inbound items will be on exchange server.

You will still have issues with the sent items however.

alternatively you could just give account 1(exchange) send as on account2(pop3) and remove the pop3 totally, let them work simply from exchange.

sorry but this is the only real solution that worked for this problem for me
0
 
ljlkrlAuthor Commented:
I might have to call MS and see if they have a solution other than SP1 which doesn't fix the problem.
0
 
AkhaterCommented:
keep me updated
0
 
ljlkrlAuthor Commented:
Microsoft has confirmed this is a bug they are working on.
No solution yet.
0
 
AkhaterCommented:
thank you for the update
0
 
ljlkrlAuthor Commented:
Ok, took a while but Microsoft finally figured this out for me.
I had to send them logs a few times, but it turns out it was corruption in my mailbox database.
They had me create a new mailbox database and then create a couple of test users in that database. I set one up with an exchange account and the other as a pop account in outlook 2003 and 2007.
I was able to send messages from the pop account with and without attachments with no erros.
I then moved my production account to the new database and tested it again, and had no problems sending mail from the pop account.
Although they said it was not the same bug that was fixed in sp1, it behaves the same way.
The corrupt database is the initial one created during install, and they could not tell me where the corruption is or what caused it.
I will now move all my users to the new database and delete the original one.

If anyone has this issue, try creating a new mail database and set up a couple of test users and see if it helps.

I am glad this one is behind me.
0
 
ljlkrlAuthor Commented:
This was resolved by Microsoft. I am merely posting this to help other users who may have this issue.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now