That's a problem when you use dynamic logons with CDO, they each create a
new profile entry in the registry. You can write additional code to delete
any profile created that way from the registry when you are finished with
the profile, or if there are existing profiles on the computer that can be
used then use the profile names in the logon call instead of using dynamic
profiles.

It's been many years since I wrote any production CDO code, I moved over to
Redemption coding instead a long time ago. But I vaguely recall that using
client side CDO with dynamic logons creates memory leaks. I could be
mistaken about that however.

--
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


"Bob Smith" wrote in message
...
It's a VBscript calling CDO 1.2. I got this working now by passing in the
users Legacy Exchange DN. I do however run into a slight problem after
some
time where I receieve an error there is not enouogh memory. I checked and
the
script is only using about 20MB and this server has a lot of memory. What
I
do see though is 1000's of Auto Created MAPI sessions are not being
cleaned
up. I have set objSession.Logoff and objSession = Nothing, but it doesn't
seem to clean up the mapi sessions in the registry.