Coldfusion can and does throw a IIS 500 internal server error. The problem is that if there is not output to the screen, and an error occurs from CF this is what gets displayed in the browser IIS 500:-)
The only way around this is to do a cftry catch and dump the cfcatch to the screen, forcing CF to display information about the error. Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 -----Original Message----- From: Kevin Aebig [mailto:[EMAIL PROTECTED] Sent: Friday, 8 September 2006 2:56 AM To: CF-Talk Subject: IIS 500 - Internal Server Error Hey all, I just found out today that a specific piece of an application we provide is throwing an internal server error for a specific client. We've tested this same area with other clients and it seems to be working fine. Because we run as an ASP, the fact that this error is tossed for only one client is boggling me. We've check the data for this client and everything is on the up and up. Can anyone think of a reason why this page would choke out and CF would have nothing to say about it? !k ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252471 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
