ASP.Net and error messages from submitting a MCMS posting

[jademoon]

I am having problems since we built a new Exchange Server 2003 (member
server) and removed the Exchange 2000 (member server) from out network.
The error comes about when an MCMS Author "submits" a web page. Using
the MCMS Workflow, this hooks into smtp and delivers mail to the
editors. Since the changeover in exchange servers this functionability
no longer works.

Environment:
First Server:
MCMS 2002 Server Enterpise SP1a
running on Win 2K Server SP4
using C#.net/VS.net 2003
MS.Net Framework 1.1.4322 SP1
IIS 5 - SMTP relay set up to Exchange server
cdosys.dll v. 6.1.3940.33

Second Server:
Exchange 2003 Enterpise SP1
running on Win 2003 Server SP1
MS.Net Framework SDK 1.1
IIS 6 - SMTP relay set up for MCMS server
cdosys.dll v.6.5.6755.0

Third Server:
SQL 2000 ver. 8.00.760 SP3
running on Win 2003 Server SP1
MS.Net Framework SDK 1.1
IIS 6
cdosys.dll v.6.5.6747.0

I can telnet from and to the Exchange box to and from the MCMS server -
works great!

I've ensured that the ASPnet account has access to wwwroot on the MCMS
server with Read&Execute, Read and List Folder Contents.

On the MCMS server cdoex.dll has been unregistered and cdosys.dll has
been registered.

However, I continue to receive these two errors:
COMException 0x80040213 - The transport failed to connect to the server
and
HttpException 0x80004005 - Could not access CDO.Message object

Any help would be most appreciated. I've tried the solutions posted but
am still having problems. Any other ideas out there that could help
resolve this issue please?

TIA,
Edy

I am also posting this on the exchange and mcms groups to see if there
is any help available as these are all connected applications.

 

[jademoon]

Just wanted to share on the solution I found that resolved my specific
problem.

I worked through all of the solutions provided on the systemwebmail
website. However, nothing appeared to work until I reset the browser
service on our main DC, the mail server and the CMS server, once I did
that on all three, the boxes were then communicating and no more error
messages.

I don't know if this will help anyone else, but I wanted to share
because this has been such a painstaking journey but oh so worth it
when it is resolved.

Thanks again for everyone who contributed in finding solutions for our
problems.