Could not access CDO.Message Object.

[Kevin Hodgson]

I am getting a strange error from my application. I only get this error on
a Windows 2000 Terminal Server in Application Server mode. On my Windows 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 by
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?

 

[Jay B. Harlow [MVP - Outlook]]

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]

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.

 

[N Baluni]

I cant disable port 25 blocking. In this case can we use differrent port i.e. 26 to b more specific. Because when i done that it is also giving me the same error. one thing i like to say that this application is running fine at localhost but doesn't work in our remote server. which is needed to block the spam.

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com