By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,136 Members | 2,135 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,136 IT Pros & Developers. It's quick & easy.

Could not access 'CDO.Message' object

P: n/a
Hi,

I'm using the System.Web.Mail class to send an e-mail from my ASP.Net
application, but when sending the e-mail, I'm getting the above error. It
seems to be because I have Office XP installed, and the version of CDO is
replaced by this installation. I haven't been able to find this error
anywhere on any MS site. Anyone have a clue on how to then actually send the
e-mail?

Thanks

Thys Brits
MCSD/MCAD
Jul 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi Thys,

Have you ever sent e-mail successfully with System.Web.Mail class before
you installed the Office XP?
Can you tell me if your smtp server used to send email need client
authentication, which may caused the problem, Since you can not set the
client authentication with the System.Web.Mail class?
Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

--------------------
From: "Thys Brits" <th**@jtsoftware.co.za>
Subject: Could not access 'CDO.Message' object
Date: Sun, 21 Sep 2003 17:57:41 +0200
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <O1**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: c5-pta-49.dial-up.net 196.33.244.49
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:109325
X-Tomcat-NG: microsoft.public.dotnet.general

Hi,

I'm using the System.Web.Mail class to send an e-mail from my ASP.Net
application, but when sending the e-mail, I'm getting the above error. It
seems to be because I have Office XP installed, and the version of CDO is
replaced by this installation. I haven't been able to find this error
anywhere on any MS site. Anyone have a clue on how to then actually send thee-mail?

Thanks

Thys Brits
MCSD/MCAD


Jul 21 '05 #2

P: n/a
Hi,

I added a reference to Microsoft CDO for Exchange library in my project, and
changed the code to use CDO.MessageClass (and had to change a few
properties, including the Configuration.Fields). This works, although there
are no authentication properties set. I'm using my local SMTP server, and it
worked using the code below (the code is run in a web server control):

CDO.MessageClass mail = new CDO.MessageClass();
mail.Subject = "Record change";
mail.From = "te**@test.co.za)";
mail.HTMLBody = "<HTML><Body><Font Face=\"Arial\" Size=\"2\">";
mail.HTMLBody += "A change has been made to a record in the table <b>" +
strTable + "</b> by " + this.Page.Session["UserName"] + ".<br>";
string sURL = this.Page.Request.Url.ToString();
mail.HTMLBody += "<p>To view the change(s), visit the website at <A href=\""
+ sURL + "\">" + sURL + "</a>.";
mail.HTMLBody += "</Font></Body></HTML>";
mail.BCC = "te**@test.co.za";
mail.To = recip.Substring(0, recip.Length - 1); //recip is a string
containing all the recipients
mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/se
ndusing"].Value = 2;
mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/sm
tpserverport"].Value = 25;
if(this.Page.Application["MailServer"] != null)
{

mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/sm
tpserver"].Value = this.Page.Application["MailServer"].ToString();
}
mail.Configuration.Fields.Update();
mail.Send();

I haven't tried sending mail before installing Office XP, the only reason I
thought it might be this, is because I found an article on MS website saying
that Office XP replaces the CDO library, and replaces the reference to it in
the registry. Any further ideas?

Thys Brits

PS - I should warn everyone - don't post with your real e-mail address -
since posting my original message, I've been spammed with these stupid
"Microsoft Update" virus e-mails - I've received about 30 in the last 18
hours.... MS should find these people and sue them for identity theft, etc,
etc, etc....

"Peter Huang [MSFT]" <v-******@online.microsoft.com> wrote in message
news:Pq**************@cpmsftngxa06.phx.gbl...
Hi Thys,

Have you ever sent e-mail successfully with System.Web.Mail class before
you installed the Office XP?
Can you tell me if your smtp server used to send email need client
authentication, which may caused the problem, Since you can not set the
client authentication with the System.Web.Mail class?
Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

--------------------
From: "Thys Brits" <th**@jtsoftware.co.za>
Subject: Could not access 'CDO.Message' object
Date: Sun, 21 Sep 2003 17:57:41 +0200
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <O1**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: c5-pta-49.dial-up.net 196.33.244.49
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:109325
X-Tomcat-NG: microsoft.public.dotnet.general

Hi,

I'm using the System.Web.Mail class to send an e-mail from my ASP.Net
application, but when sending the e-mail, I'm getting the above error. It
seems to be because I have Office XP installed, and the version of CDO is
replaced by this installation. I haven't been able to find this error
anywhere on any MS site. Anyone have a clue on how to then actually send

the
e-mail?

Thanks

Thys Brits
MCSD/MCAD

Jul 21 '05 #3

P: n/a
For those of you who were wondering about this, I found the solution. It's a
permissions problem. I added the following code at the top of my class, and
it worked!

using System.Security.Permissions;
[assembly:PermissionSetAttribute(SecurityAction.Req uestMinimum, Name =
"LocalIntranet")]

Thys Brits
MCSD/MCSD.Net

"Thys Brits" <th**@jtsoftware.co.za> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...
Hi,

I added a reference to Microsoft CDO for Exchange library in my project, and changed the code to use CDO.MessageClass (and had to change a few
properties, including the Configuration.Fields). This works, although there are no authentication properties set. I'm using my local SMTP server, and it worked using the code below (the code is run in a web server control):

CDO.MessageClass mail = new CDO.MessageClass();
mail.Subject = "Record change";
mail.From = "te**@test.co.za)";
mail.HTMLBody = "<HTML><Body><Font Face=\"Arial\" Size=\"2\">";
mail.HTMLBody += "A change has been made to a record in the table <b>" +
strTable + "</b> by " + this.Page.Session["UserName"] + ".<br>";
string sURL = this.Page.Request.Url.ToString();
mail.HTMLBody += "<p>To view the change(s), visit the website at <A href=\"" + sURL + "\">" + sURL + "</a>.";
mail.HTMLBody += "</Font></Body></HTML>";
mail.BCC = "te**@test.co.za";
mail.To = recip.Substring(0, recip.Length - 1); //recip is a string
containing all the recipients
mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/se ndusing"].Value = 2;
mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/sm tpserverport"].Value = 25;
if(this.Page.Application["MailServer"] != null)
{

mail.Configuration.Fields["http://schemas.microsoft.com/cdo/configuration/sm tpserver"].Value = this.Page.Application["MailServer"].ToString();
}
mail.Configuration.Fields.Update();
mail.Send();

I haven't tried sending mail before installing Office XP, the only reason I thought it might be this, is because I found an article on MS website saying that Office XP replaces the CDO library, and replaces the reference to it in the registry. Any further ideas?

Thys Brits

PS - I should warn everyone - don't post with your real e-mail address -
since posting my original message, I've been spammed with these stupid
"Microsoft Update" virus e-mails - I've received about 30 in the last 18
hours.... MS should find these people and sue them for identity theft, etc, etc, etc....

"Peter Huang [MSFT]" <v-******@online.microsoft.com> wrote in message
news:Pq**************@cpmsftngxa06.phx.gbl...
Hi Thys,

Have you ever sent e-mail successfully with System.Web.Mail class before
you installed the Office XP?
Can you tell me if your smtp server used to send email need client
authentication, which may caused the problem, Since you can not set the
client authentication with the System.Web.Mail class?
Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
From: "Thys Brits" <th**@jtsoftware.co.za>
Subject: Could not access 'CDO.Message' object
Date: Sun, 21 Sep 2003 17:57:41 +0200
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <O1**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: c5-pta-49.dial-up.net 196.33.244.49
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:109325
X-Tomcat-NG: microsoft.public.dotnet.general

Hi,

I'm using the System.Web.Mail class to send an e-mail from my ASP.Net
application, but when sending the e-mail, I'm getting the above error. Itseems to be because I have Office XP installed, and the version of CDO isreplaced by this installation. I haven't been able to find this error
anywhere on any MS site. Anyone have a clue on how to then actually
send the
e-mail?

Thanks

Thys Brits
MCSD/MCAD


Jul 21 '05 #4

P: 1
Hi , can somebody tell me the solution for VB.NET
Jul 3 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.