Just a SWAG: I ran into a problem with CDO once before and reinstalling it helped.

CDO:
http://www.microsoft.com/downloads/details.aspx?familyid=2714320D-C997-4DE1-986F-24F081725D36&displaylang=en

Mapi and CDO:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e

It may or may not help, but it fixed whatever was causing the problem for me. At the time, I didn't get valid objects after createobject.

Also, are you using a local smtp server? If so, is IIS running your test machine? You could test running the smtp service on your machine:
Add/Remove Programs, Add/Remove Windows Components, IIS, check SMTP


>Unfortunately I don't know about CDO related stuff, so I can't answer that question.
>Even after re-registering CDO, the error persist and is exactly the same.
>(obs: The object created with CreateObj("CDO.Configuration") does point to CLID in registry, etc)
>
>I would say that CDO.Message works fine, but CDO.Configuration is access denied by some unknown reason.
>By the way, cdosys.dll has Apr/13/2008 as its version date tag.
>
>Dany
>
>>Did you install anything CDO related on the PC?
>>It looks like "CDO.Configuration" points to the wrong class.
>>Try to re-register CDO 2000 from the Command prompt
>>

>>Regsvr32.exe  cdosys.dll
>>

>>
>>PS. Pleas enable 'Auto quote' from the 'Message setup view'. It's hard to follow discussion w/o previous message included
>>
>>>Just after objCDOConfig.count: OLE error code 0x80020006 Unknown name
>>>
>>>Just after objCDOConfig.Fields(0).name: Member FIELDS does not evaluate to an object
>>>
>>>Understood that objCDOMessage is working.
>>>