CDO Message Object ERROR

[dwa]

We're trying to use the CDO Message object to send an SMTP message with
..NET. Testing the code on a machine with FAT32 file system, everything
works fine. Running under XP or Win2K with NTFS, we receive a message to
the effect: "Unable to access CDO.Message object".

This would seem to be some kind of permissions problem - the same code works
just fine if dropped into a console app. Has anyone solved this problem
before?

Thanks in advance for your input....

-- da

 

[Jeff]

A few things to check:

1) Make sure that the ASPNET account has read access to the CDO Library
(usually CDOSYS.DLL in the System32 directory).
2) Make sure that the ASPNET account has update access to the
c:\inetpub\mailroot directory and its subs.

If either one of these isn't done, you will get the unable to access error.

Jeff

 

[dwa]

Jeff,

Thanks for your reply. This sounded too reasonable to be
true. Unfortunately it doesn't to make any difference.

I Gave *all* users (including ASP.NET) complete
permissions to the CDO files and *all* users complete
permissions to the mailroot and subs - but still get the
error message.

I think maybe it's time to write my own SMTP mail class!

Maybe I have to give complete permissions on all of
system32 to ASP.NET? Any other thoughts?

Thanks,

-- dwa

 

[Jacob Yang [MSFT]]

Hi Dwa,

Based on my research and experience, I agree with you that it should be a
permission issue since the same code works fine in the console application.

Please try to impersonate the same User account of the console application
for All the Requests of an ASP.NET Application. Please refer to the
following article for the detailed information.

INFO: Implementing Impersonation in an ASP.NET Application
http://support.microsoft.com/default.aspx?scid=kb;en-us;306158

I hope it helps.

Best regards,

Jacob Yang
Microsoft Online Partner Support
Get Secure! ¨C www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Jeff]

You can make the aspnet account an administrator temporarily. If that fixes
the problem, you then know it is access related; you just have to figure out
where the error is.

One other thing to check is the version of CDO installed on the system. I
remember having a similiar problem and tracked it back to the system having
an old version of CDO installed (on purpose, as it turned out).

Jeff