ASP CDO & Excahnge 2007 / IIS 2007 on SBS 20087

I upgraded from SBS 2003 to SBS 2008 on a 64-bit machine. The upgrade broke all of my Classic ASP apps that use CDO to send emails. I was able to regster the CDOSYS.dll (regsvr32 C:\Windows\SysWOW64\cdosys.dll) which eliminated my initial ASP 0177 error. The ASP pages are now producing this error:

CDO.Message.1 error '80070005'

Access is denied.

This happens on the cdoMailObject.Send line in my code. Obviously, the IIS_USR account doesn't have permission to send email from CDO, but I can't figure out where/why.

I've tried adding IIS_USRS to Exchange 2007 so that it has it's own mailbox. That didn't seem to work. I tried giving IIS_USR permissions to WRITE on the mailroot and wwwroot folders, and that didn't seem to work. Any other suggestions?

Thank you,
J
LVL 4
brownmetalsAsked:
Who is Participating?
 
brownmetalsAuthor Commented:
Thanks for your input. I actually had to contact Microsoft to get a direct answer (I posted that here on the original question which I'm trying to close).

http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/ASP/Q_25018094.html#a26192034

Microsoft recommends that SMTP not even be installed on an Exchange 2007 server (Exchange uses the Transport service to route mail in Exchange 2007). Their support engineers suggested removing the SMTP service all together. I believe IIS would use the SMTP service, but as Microsoft has suggested, using the Exchange Transport service instead is prefered. The complete explanation and further details are at that post above. I'm going to suggest this question be closed.

Thanks agian for your input.
J
0
 
Tray896Commented:
Yeah my initial answer was going to be make sure that your anonymous user (IIS_IUSR) has write permissions to C:\inetpub\mailroot\pickup.  You should also ensure that the 'Network Service' account has access to this location.

If you are still getting Access Denied errors, then you should be able to easily track down the source by enabling auditing and using something like Filemon.  Here is a step by step guide on setting that up which will help you resolve nearly all permissions issues:

http://weblogs.asp.net/steveschofield/archive/2008/03/07/detecting-permission-issues-using-auditing-and-process-monitor.aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.