Ok, here is what I am seeing...can anyone tell me if this is just me
or a bug? If it's just me, anyone know how to fix it?
- Create an Access DSN called "test".
- Rename DSN to "test.renamed".
- Create SQL Server DSN called "test".
The DSN gets created, but above the list of DSN's I see this error:
Connection verification failed for data source: test
[]java.sql.SQLException: No datasource named test is configured in
jrun-resources.xml
The root cause was that: java.sql.SQLException: No datasource named test is
configured in jrun-resources.xml
- Rename the test DSN to "test2".
The test2 DSN should now validate and work, renaming it back to test
will throw the above error again. I have recreated this with
multiple databases. Whatever is happening it's definitely not
database specific.
Are DSN's in MX one time use only? Seems silly, but that's what it
looks like to me.
--
jon
mailto:[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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
