Home »Windows»CF5 Problems
2009-01-20
Really complex passwords are a brilliant idea, right? Wrong.
2008-08-27
Often, you will see mention of things like System Error 52 or Operating System error 2 has occurred. But what do they mean?
2008-07-30
Don't use Catch-All (or wildcard) email addresses. Just don't.
Your IP address is
38.107.191.82
Warning! The following is an example of how a simple explanation can be overlooked, and much time can be wasted tracking a problem that you probably shouldn't have bothered with.
A recent problem came up with a server running ColdFusion 5. It seemed to be in a poorly state, with CF logfiles completely filling up the disk and resulting in the CF services collapsing.
The interesting errors which filled the log (and the disk) were:
Unexpected error returned from GetQueuedCompletionStatus.
and
Windows NT error number 6 occurred.
A quick check with Dependency Walker shows that the GetQueuedCompletionStatus function lives in the Kernel32.dll file, and MSDN backs this up. I also found a couple of other errors which suggested some of their CFM code was using a deprecated CFINSERT tag - but I quickly discounted this when none of their web content contained such a tag.
So, where does that leave me? Could ColdFusion 5 really have some startling incompatibility with the Windows thread pooling API?
Yes, as it turns out. In all the time I spent scouring the 4Gb of logs, I didn't think to check out the status of CF5 itself. It's been EOL'd (End Of Life), and was never supported on Windows Server 2003 in any case. A quick visit to Adobe's support policy pages could have told me that.
Moral of the story - check the system requirements before troubleshooting!
