Just to follow up, restarting the server will allow the SQL Server "test" DSN to verify...
-- jon mailto:[EMAIL PROTECTED] Monday, March 3, 2003, 3:42:31 PM, you wrote: jh> Ok, here is what I am seeing...can anyone tell me if this is just me jh> or a bug? If it's just me, anyone know how to fix it? jh> - Create an Access DSN called "test". jh> - Rename DSN to "test.renamed". jh> - Create SQL Server DSN called "test". jh> The DSN gets created, but above the list of DSN's I see this error: jh> Connection verification failed for data source: test jh> []java.sql.SQLException: No datasource named test is configured in jrun-resources.xml jh> The root cause was that: java.sql.SQLException: No datasource named test is configured in jrun-resources.xml jh> - Rename the test DSN to "test2". jh> The test2 DSN should now validate and work, renaming it back to test jh> will throw the above error again. I have recreated this with jh> multiple databases. Whatever is happening it's definitely not jh> database specific. jh> Are DSN's in MX one time use only? Seems silly, but that's what it jh> looks like to me. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
