The dreaded 0x800CCC0F sending error

Windows *was* completely up to date, when the error first appeared; in fact, I had correlated the problem with the three July updates to Windows 8.1. I backed out those updates, but no change; (*sigh*). They're ready to get applied again when I reboot.

I left 2SV on after I set an app password, to no avail. But Diane's article says my version of Outlook will work fine w/o 2SV and an App PW, so I've since backed them out for both my GWA account and my GMail account.

I only run Symantec Endpoint, which I temporarily disabled as a test, again, to no avail. I don't have any other AV (e.g., Defender) enabled. The firewall is obviously not implicated, since test messages are sent/returned to my inbox.

I'll review those other articles, thanks.

Error 0x800CCC0F,is typically encountered when there is a credential issue with the account - very frequently with Yahoo / AOL / AT&T accounts where the user has not used an <App Password> as the email address for the account in Outlook.

You've gone though everything I can think of from a trouble-shooting standpoint so the only thing left is making sure that Windows is completely up-to-date.

This may also seem like an odd-question to ask, but you didn't turn off 2FA on the Google account after you generated the <App Password> did you? (reason for asking is that one user who was encountering issues did so - just covering all bases)

Outlook MVO Diane Poremsky (the author of the article you referenced) has a variety of articles / reference points on the subject (she is the pre-eminent expert in all things Outlook) which brings the focus back to the <timeout> setting for the account

Error 0x800CCC0F when sending or receiving email.

Usually caused by Antivirus software scanning email, but antispam scanners may cause Outlook to return this error as well. Disable the email scanning or increase the timeout setting. Also, make sure your firewall is allowing the scanner software to connect to the Internet.

as described in

Common Outlook Outgoing Server (SMTP) Errors

https://www.slipstick.com/problems/common-outlo...

Outlook 2016 0x800CCC0F 'The connection to the server was interrupted'

https://forums.slipstick.com/threads/95290-outl...

Well, my wife's computer has Word, but not Office; so I don't have another computer I can experiment with.

...but I think I've gone down a rabbit-hole anyway. The error reported by the change Google made is 0x800CCC92, not 0x800CCC0F, according to this website:

Task '******@gmail.com - Receiving' reported error (0x800CCC92): 'Your email server rejected your login. Verify your username and password for this account in Account Settings. The server responded: -ERR [AUTH] Username and password not accepted."

And since I have the retail version of Outlook 2016, I'm unaffected by this change anyway:

Users with Outlook 2016 (retail version), 2019, 2021, and 365 won't have a problem when Less Secure Apps is disabled. 

c:\Program Files\Microsoft Office\Office16>cscript ospp.vbs /dstatus Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing--------------------------

PRODUCT ID: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx SKU ID: xxxxx LICENSE NAME: Office 15, OfficeProPlusR_Retail edition LICENSE DESCRIPTION: Office 15, RETAIL channel LICENSE STATUS: ---LICENSED--- Last 5 characters of installed product key: 2PMG3

So this was all for naught; especially considering, that each reconfig of an email service successfully transmits an email to the server.

So I've got to focus on why my Outlook client is returning an error of 0x800CCC0F - the original subject of this thread.

Given everything else, I'd go for trying your wife's computer to see if things work. I unfortunately no longer have any test systems with Win 8.1 so can't test anything

If things work on Win 10, it would point to something obscure on Win 8.1 - either way would be good info to have if and when you finally connect with the Google folks

OK - just to sum everything up to this point

#1 - You've created a new Outlook profile - correct? (That takes a corrupt Outlook profile out of the equation)

Yes. Brand spankin' new.

#2 - You configured the accounts again

Yes,

#3 - No addins

None.

#4 - Issue exists even when sending the most benign message

Yes.

#5 - This only involves Google accounts

Yes. Perhaps I should resurrect a yahoo account, or icloud...

I'd suggest reinstalling Office at this point but personally think that would be a complete waste of time since only Google accounts are impacted with this

I removed the 32-bit version I had been using, and installed the 64-bit version. Still no love.

That leaves 2 other things to try in this quest

#6 - Do you by any chance have another machine you can try using these accounts to see if this is a machine specific thing?

Hmmm... I guess I could try my wife's Windows 10 machine. (Mine is 8.1).

#7 - If you turn off EndPoint - does that change anything? (I'd be surprised if it did but have to check)

I disabled it; still no love.

*** any words of wisdom yet from the Google folks?

The handoff to Tier 2 was about two hours ago. I haven't closed the chat window, but no signs of life.