Well, there are no doubt a few things to check here. Get them to check their disk space on the ColdFusion box and ensure the neo-query.xml file is not corrupt. Easiest way to tell us by loading it in IE, if it doesn't load, it's broken.
Is the SQL Server 64-bit? The connection reset could be a network issue as well. "This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant, Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: RobG To: CF-Talk Sent: Thu Mar 22 23:56:15 2007 Subject: Bad DSN causing CF to crash I ran into this problem yesterday and wanted to post about it to see if anybody has ever experienced it. Client running CFMX7.02 on Windows Server 2003 SP1 with all updates. Connecting to MSSQL2000 database on separate shared db server. App is nothing particularly fancy, CF5-compliant with a couple of MX-specific uses of CFFORM and a couple of CFCs. For the last week or so, we've been getting progressively increasing numbers of errors saying "connection reset" when trying to make db calls. I posted about it here and got one response indicating a problem with drivers back on MX6.1. We decided to relocate the db to MSSQL2005 on the webserver and off of the shared environment, because the ISP was unwilling to try to fix the problem since it wasn't consistent. Yesterday, prior to moving the db (it was tentatively scheduled for last night), the db stopped responding. Or rather, what appeared to be the case was CF up and died. It would time and end conclude with a JRun Closed Connection error. Thinking that CF was hosed, I uninstalled it, rebooted, and reinstalled CF. We ended up doing this twice. Nothing worked. Get it back up, recreate the DSN to the shared server, and CF was dead again within a minute or two. Finally, I had an idea... I restarted the CF service and killed the DSN. I recreated it pointing to a copy of the database running on an entirely different server on my own personal network. Now the site ran just fine. So I started suspecting the shared db server. To test my theory, I copied the site's code to our development server at another ISP (this time a Linux box), and pointed it to the shared db server. CF immediately went down. Once more... I did the same thing on my home development machine. CF once again died. So I contacted the ISP and rather than try to explain this to them, I just asked that a backup copy of the db be put on the webserver, which they managed to do within an hour (wow!). I imported it into the local MSSQL2005 and setup the DSN... bingo! Everything was running again. What's odd is that you can talk to the shared db server using MS SQL Management Studio, with RDS, or even with SQL Explorer under Eclipse just fine. But try to get the CF application server to talk to it means certain death. I can't explain it, but everybody is relieved that things are good again. And we're avoiding that shared db server like the plague. Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273485 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
