Comments on: Error message 0x8004011D

By: markvcam

markvcam — Wed, 17 Jun 2009 13:28:13 +0000

check out this article as well for some other workarounds:

http://www.theemailadmin.com/2009/06/troubleshooting-error-code-0x8004010f/

By: platypus

platypus — Fri, 19 Aug 2005 16:26:58 +0000

Just as a test, add an entry to your ‘hosts’ file for your exchange server, see if that solves that problem. If it does, it points to a DNS issue. At that point, you can concentrate on DNS on that machine, or, if this is a ‘one-time’ issue only on this machine, just leave the entry in the hosts file! I put these entries in my domain PCs’ hosts file, just as a backup in case DNS/WINS fails.

By: gatman2000

gatman2000 — Fri, 19 Aug 2005 08:36:01 +0000

http://support.microsoft.com/kb/289971/EN-US

Covers the specific error message you are encountering.

By: aquaticous

aquaticous — Fri, 19 Aug 2005 07:43:16 +0000

WORKAROUND
To work around this problem, when you send a message by using CDO and MAPI, set the PR_MESSAGE_CLASS property of the message to “IPM.Note” (with the quotation marks). In the example that is mentioned in the “Cause” section, insert the following line before the “oMessage.Send” line:
oMessage.Fields(&H001A001E).Value = “IPM.Note”

Check this Link: http://support.microsoft.com/?kbid=840835

By: poomba1

poomba1 — Fri, 19 Aug 2005 03:10:40 +0000

I’d also look at the network, confirm the port on the switch and NIC card match speeds (auto or 100FD) etc (NIC sriverup to date). Then is the firewall turned on, was one installed on there then uninstalled? I’ve seen Zone Alarm not remove itself cleanly. Any local AV, I’ve seen where in odd ocasion on Symantec, the Exchange Plug-in gets installed on the client (it’s a pig), I use SAV server side, client side is horrible, causes those issues.