CDO.Message.1 error '80070005' (Full Version)

All Forums >> [Web Development] >> Server Issues



Message


CraigBFG -> CDO.Message.1 error '80070005' (7/28/2004 5:03:27)

Does anyone know how I get around this error?

Since we moved over to SBS 2003, I get this error everytime I try to email from my ASP page. I do not get this error on our Win2003 web server.

I believe it has something to do with Exchange permissions or port settings, but I can't find how to resolve it.

Any ideas?

Thanks
Craig




CraigBFG -> RE: CDO.Message.1 error '80070005' (8/4/2004 10:55:40)

Ok, solved it!
It's all down to a setting within IIS for the website. The default application ise set to "default application pool", whereas I have changed this is "Exchange Application" and it now works fine.

Incase anyone else has received this error.




priyanke -> RE: CDO.Message.1 error '80070005' (9/1/2005 1:19:58)

Dear Craig,

Thank you. God Bless.

SBS2003 is quite diferent to others.

Priyanke.




mltsy -> RE: CDO.Message.1 error '80070005' (6/28/2006 16:12:32)

Thank you so much! I can't believe how hard it is to find this answer! :)

I kept getting access is denied for CDO.Message and now it is solved.

Thanks!
http://media.breezyandjoe.com/




mltsy -> RE: CDO.Message.1 error '80070005' (7/19/2006 12:25:04)

After fixing this issue, somehow it reappeared and I checked everything I knew how to check and couldn't figure it out until I found a post than mentioned using Filemon to figure out where the denied access was happening, so I thought I would post how I fixed it incase other people are still having problems:

1) Download Filemon from http://www.sysinternals.com/Utilities/Filemon.html to your server. Unzip and run it.

3) Press Ctrl+L or click the "Filter" button in the menu bar (it looks like a funnel).

4) Uncheck "Log Reads" and "Log Successes" so you don't have hundreds of entries coming up every second. Click OK.

5) Press Ctrl+X or click on the "Clear" button to clear the list.

6) Try your ASP script again and voila, you should have an entry whose result is "ACCESS DENIED" in your list along with the file path and user.

7) Now you can find and right-click on the folder, go to properties->security and grant that user write permission in that directory.

In my case the folder was the "pickup" folder NOT in Intepub (as so many message boards suggest), but in Program Files->Exchsrv directory, and the user was not IUSR_COMPUTERNAME (as so many boards suggest), but NETWORK SERVICE as the exchange application pool on my server is running under the "network service" identity.

Whatever your unusual configuration, you should be able to pinpoint the problem using Filemon. [:)]





Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.1572266