Well, I can't fully say what's up, but I've gotten similar HTTP-500 errors before when I was testing my day's work.

I don't know why CF doesn't give you the debug information.  Maybe someone the knows more about the internal workings of CF might do that (Ray, Sean or Dave?).

However, I can tell you why I was getting this error.  I noticed that it happend mostly with syntax of code within cfscript.  Usually something stupid like missing a ; at the end of a line of code, a missing curly brace in some conditional logic or even a missing open or close () when using a function in a conditional logic block.

Also, make sure that the syntax of how your component is being invoked is correct.

When in doubt start commenting out lines of code and run.  If it works, then add another until it doesn't.  But that is only helpful if you know the template that is making this happen.  If you don't know, you could always use CFabort at the end of your Application.cfm to check if its that.  If it is, then start moving that Cfabort arounds.

HTH,
.Peter
MaePub
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to