The poster should also check to see if he's running a script stopper such as
Norton or McAfee, which might be preventing automation of CDO by preventing
CreateObject or New from creating new instances of CDO.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"SvenC" wrote in message
...
Hi,

I have a VB6 app that has been working for 18months. But now generates
a 429 error at the line

Set oCDO = CreateObject("MAPI.Session")

I use Outlook 2003, Windows XP, CDO 1.21

I suppose either Windows, or the Outlook server may have changed
without my knowledge.

I haven't touched the code which, as I say has been working happily.

There are some other users of my app which experience the same problem
at the same time, which I guess points to either a change in the
Outlook server config, or a Windows update that we received
concurrently. I've checked that my cdo.dll is still in place, and it
is .

Did you ensure that CDO is selected in the Outlook setup options? It is
not selected by default.
Open regedit: do you have HKEY_CLASSES_ROOT\Mapi.Session? Do you see a
CLSID subkey?
Its default value should start with {3fa7d and so on.
Search that value in HKEY_CLASSES_ROOT\CLSID\
There should be an InprocServer32 subkey with a path to cdo.dll. Does that
file exist?

--
SvenC