As you know one of the first things you should do on a production ColdFusion server is disable robust exception information (this includes things like source code, and file path disclosures in error messages), in the ColdFusion Administrator.

Error handling in SQL Server T-SQL scripts is not always the most graceful thing to deal with. With the release of Microsoft SQL Server 2005 you can now use TRY / CATCH statements.

I have been racking my brain trying to figure out why I kept getting this error:

"Element CACHE is undefined in APPPLICATION."

My first thought was that somehow the CACHE variable was being deleted from the application structure, somewhere in the code.

While working today I had to write an error message that a user would see if their session had timed out. I was tempted to write something like:

Sorry your session has expired please login again.

When using GMail I sometimes get the following error message:

Arrgh! The page has been corrupted. If you are running security or firewall software, you may have to disable it

This is a bad error message for a number of reasons.

I recently did this:

<cfoutput query="#queryName#"> ... </cfoutput>

Can you spot the error?

I think that is probably a very common mistake - here's the error message you get in ColdFusion MX 6.