OX80042109 Message when Unable to Send Email in 2003 Outlook using verizon DSL

[ptobinPR]

I was unable to send email in my outbox today using a new (2 week old)
Dell GX520,
microsoft small business edition (OUTLOOK 2003) and Verizon DSL.

Kept getting unable to connect to the outgoing server and this
0X80042109 message.

Also the incoming pop connection couldn't be made, although I still go
my incoming email. Only outgoing was stuck in the outgoing box.

Verizon said the OX is a microsoft error. He took out all my settings
for verizon and put them back in and then it worked.

But what does this OX signify?

He thought there might be a corruption in a DLL file.

This is my 3rd OPtiplex type computer from dell and it seems like I'm
having problems with outlook on all 3, and they blame me at dell.

Thanks.

 

[ptobinPR]

I use AVG anti-virus, no spyware, firewall. etc.

 

[ptobinPR]

I use AVG anti-virus (no firewall, spyware, etc).

 

[ptobinPR]

I use no other server, I am a solo user in a solo home office.

 

[Brian Tillman]

I was unable to send email in my outbox today using a new (2 week old)
Dell GX520,
microsoft small business edition (OUTLOOK 2003) and Verizon DSL.

Kept getting unable to connect to the outgoing server and this
0X80042109 message.

Also the incoming pop connection couldn't be made, although I still go
my incoming email. Only outgoing was stuck in the outgoing box.

Verizon said the OX is a microsoft error. He took out all my settings
for verizon and put them back in and then it worked.

But what does this OX signify?

It's not oh-ex, it's zero-ex: 0X80042109. The zero followed by the X means
that the remaining characters are hexadecimal (base 16) digits. Consult the
Microsoft Knowledgebase for possible explanations.
<http://support.microsoft.com/search...20&ast=1&ast=2&ast=3&ast=4&ast=7&mode=a&adv=1>

 

[Guest]

Hi Brian,

So we're you able to fix it then. Just return to original settings?

Leo

 

[Brian Tillman]

So we're you able to fix it then. Just return to original settings?

I didn't have to fix it. I wasn't the one with the problem. Read the
entire thread.