T
ticketdirector
Hi,
In the event viewer on our production web server (win2k3), I am seeing
that if a call to the System.Net.Mail.SmtpClient.Send() function fails
/ throws an exception, it is popping up an assertion failure message
box. But since this is a remote server, there is no logged in user, so
the assertion failure message box is just sitting there waiting forever
for someone to come along and hit "OK" button. This is causing problems
on the server.
We have this call in a try/catch, so I can't understand why assertion
failires or exceptions are not caught. Why is this call causing an
application assertion failure popup message that can never be seen? Is
there a way to fix this?
thanks for any help.
Roy.
In the event viewer on our production web server (win2k3), I am seeing
that if a call to the System.Net.Mail.SmtpClient.Send() function fails
/ throws an exception, it is popping up an assertion failure message
box. But since this is a remote server, there is no logged in user, so
the assertion failure message box is just sitting there waiting forever
for someone to come along and hit "OK" button. This is causing problems
on the server.
We have this call in a try/catch, so I can't understand why assertion
failires or exceptions are not caught. Why is this call causing an
application assertion failure popup message that can never be seen? Is
there a way to fix this?
thanks for any help.
Roy.