Charlie,
I found the same article earlier this afternoon. Your guidance added
confirmation that this may lead to the solution. Since we are running MX7 and
SQL Server 2008 Express, I updated the drivers. I restarted the server and
configured an Other type data source where I specified:
JDBC
Well, I wouldn't have tried the other type first, but I see that in that
technote I shared it does say you may need to do it because of some other
bug. Did you at least try it as a normal SQL Server DSN? I see you say
later, I also tried the value of the JDBC URL in the Connection String
value
Thanks for the continued support, Charlie. Comments below:
From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Charlie Arehart
Sent: Tuesday, February 22, 2011 10:57 AM
To: discussion@acfug.org
Subject: RE: [ACFUG Discuss] ColdFusion system account access to database
Well, I wouldn't
Woah, well that's different, Rob. You say in your second comment that you
get No suitable driver. You'd not indicated that before. That's a very
different problem (of either CF not finding the class, or there being a
class loading issue, or a conflict with other drivers. More on that in a
moment.)
Charlie,
You're amazing! With your help, I found the problem. When I archived the old
macromedia_drivers, I kept the copy of the jar in the same directory with a
different file name. Apparently, these collided. Now that I moved the archive
elsewhere, it works as a straight SQL Server data
Ta da. :-) Really glad to see it finally resolved.
And yes, you do have to be careful to not ever (with drivers or hotfixes)
just rename a jar file to just somethingelse.jar. The JVM doesn't really
care about filenames: if there's a jar file in the classpath, it will look
in them all to find any
