We did eventually solve this problem.
It turns out a new version of McAfee Anti-Virus was installed on this
Terminal Server, and it blocked port 25 by default, to stop spam zombies.
Disabling the Port 25 blocking got everything moving again.
"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP@msn.com> wrote in message
news:%23k05A8quEHA.228@TK2MSFTNGP10.phx.gbl...[color=blue]
> Kevin,
> Have you check the information at:
>
>
http://www.systemwebmail.net/
>
> Other then considering asking in one of the Terminal Server specific
> newsgroups, as this sounds more like a terminal server configuration
> problem, I don't use Terminal Server to offer any help there...
>
> Hope this helps
> Jay
>
> "Kevin Hodgson" <kevin@caseware.com> wrote in message
> news:OYtnF$ouEHA.2684@TK2MSFTNGP10.phx.gbl...[color=green]
> >I am getting a strange error from my application. I only get this error[/color][/color]
on[color=blue][color=green]
> > a Windows 2000 Terminal Server in Application Server mode. On my[/color][/color]
Windows[color=blue][color=green]
> > XP
> > Development workstation, this same code works without error.
> >
> > On the Terminal Server I get:
> >
> > Could not access 'CDO.Message' object.
> > System.Reflection.TargetInvocationException: Exception has been thrown[/color][/color]
by[color=blue][color=green]
> > the target of an invocation. --->
> > System.Runtime.InteropServices>COMException (0x80040211): The message
> > could
> > not be sent to the SMTP Server. The transport error code was 0x800ccc15.
> > The
> > server response was not available.
> >
> > Exact same code, with the exact same settings for the mail message, and
> > the
> > SMTP Server. Does anyone know why I might be getting the above error?
> >
> >[/color]
>
>[/color]