RE: problem with cferror, trycatch and iis7

2009-03-02 Thread Pat Wenke
CF Admin - Server Settings - Settings - Enable HTTP status codes -Original Message- From: Rick Root [mailto:rick.r...@webworksllc.com] Sent: Monday, March 02, 2009 11:21 AM To: cf-talk Subject: problem with cferror, trycatch and iis7 I have a couple issues with error trapping on our

Re: problem with cferror, trycatch and iis7

2009-03-02 Thread Rick Root
On Mon, Mar 2, 2009 at 12:57 PM, Pat Wenke pwe...@uhlig.com wrote: CF Admin - Server Settings - Settings - Enable HTTP status codes That tells CF to send 500 errors instead of 200s. But that doesn't have anything to do with why my cftry/cfcatch is being ignored. -- Rick Root New Brian

RE: problem with cferror, trycatch and iis7

2009-03-02 Thread Pat Wenke
Either you don't have the tag installed / configured correctly, or it's the fact that you're running 64 bit. The com/allaire/cfx/CustomTag null gives it away. Contact efflare for the 64 bit version of imageCR3 (it now runs as a service). Don't forget to run the service under an account that

Re: problem with cferror, trycatch and iis7

2009-03-02 Thread Rick Root
On Mon, Mar 2, 2009 at 3:40 PM, Pat Wenke pwe...@uhlig.com wrote: Either you don't have the tag installed / configured correctly, or it's the fact that you're running 64 bit.  The com/allaire/cfx/CustomTag null gives it away. You seem to have misunderstood my problem. I'm not asking for

Re: problem with cferror, trycatch and iis7

2009-03-02 Thread Rick Root
It would appear that CF is unable to catch the error generated by the cfx tag. I tried something simpler, like this: cfset source = u:\classcreator\003\00700\1_5.jpg pcfoutputfile exists? #fileExists(source)#/cfoutput/p cftry !-- bar is not defined -- cfset foo = bar

RE: problem with cferror, trycatch and iis7

2009-03-02 Thread Pat Wenke
[mailto:rick.r...@webworksllc.com] Sent: Monday, March 02, 2009 3:17 PM To: cf-talk Subject: Re: problem with cferror, trycatch and iis7 On Mon, Mar 2, 2009 at 3:40 PM, Pat Wenke pwe...@uhlig.com wrote: Either you don't have the tag installed / configured correctly, or it's the fact that you're running