Could not access 'CDO.Message'

[cbanks]

I have read most of the posts about this and still cannot resolve my
issue. I have an application using system.web.mail to send notes from
one user to another. When a user logs into the application, their
e-mail address is stored in a session variable. If they want to send
information from within the app to another user, they type the note
then select a user and click send. This causes the app to lookup (via
a stored procedure) the user id and pull the e-mail address.

This works about 95% of the time with no issues. The other 5% I get
the error "Could not access 'CDO.Message'" I handle the error within a
Try error routine which does return both e-mail address when I get the
error. I also have it notify the user an error has occured, so they
can try to send again. Usally, the second or third time it goes from
what I am told.

Has anyone else run accross this or have any ideas on what is going on?

Thanks
Charles

[Bruce Barker]

this message is misleading. if cdo gets any error sending mail, your .net
code receives this error. you will need to track down the "real" error.
maybe your mail system is logging them.

-- bruce (sqlwork.com)

<cb****@bjtsupport.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

I have read most of the posts about this and still cannot resolve my
issue. I have an application using system.web.mail to send notes from
one user to another. When a user logs into the application, their
e-mail address is stored in a session variable. If they want to send
information from within the app to another user, they type the note
then select a user and click send. This causes the app to lookup (via
a stored procedure) the user id and pull the e-mail address.

This works about 95% of the time with no issues. The other 5% I get
the error "Could not access 'CDO.Message'" I handle the error within a
Try error routine which does return both e-mail address when I get the
error. I also have it notify the user an error has occured, so they
can try to send again. Usally, the second or third time it goes from
what I am told.

Has anyone else run accross this or have any ideas on what is going on?

Thanks
Charles

[cbanks]

Great! I always like misleading errors. I have checked various logs
and cannot find any other error messages related to this. Based off
the other posts, I have re-checked security which is ok. Since I have
a try statement that will send me everything used to instantiate the
process on error, how else can I track down the "real" error?