I'm running ColdFusion 9 Trial Version (no hotfixes), SQL Express 2005, Windows XP SP3, IIS.
Using ColdFusion Administrator, when I try to create a datasource to SQLExpress 2005 (SQL Server Express), using the SQL Server driver, I get the following error:
Connection verification failed for data source: AMT
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
The "instance", which I take to mean the database instance, is "machinename\SQLExpress" (This is a so-called "named instance".) This is what I enter into the "Server" field of the form (Data & Services -> Datasources -> Microsoft SQL Server).
On the other hand, I am able to create an ODBC datasource name in Windows using the Microsoft SQL Server Native Client Version 09.00.3042 driver and using the same instance, "machinename\SQLExpress".
Does anybody have any ideas as to what's wrong?
Try using the TCP/IP domain name (or IP address) & port instead of the Windows-styled connectivity info. You might need to enable TCP/IP as a network protocol on the DB server though (I think it's off by default on SQL Express Ed).
Well, I solved the problem. The error message said it might not be running. I discovered that SQLExpress is not configured by default to accept TCP/IP connections. Using the SQL Server Configuration Manager, I enabled TCP/IP. Problem solved.
Things to check:
1. Are TCP/IP connections enabled for the SQL instance?
2. Is a firewall blocking the port SQL server is listening on?
3. Is SQL authentication enabled in SQL the instance?
See this blog entry, it may be helpful.
One other thing to try. Make sure that SQL Server Browser service is running. You can find it through the Window Services panel. I tried all other suggestions multiple times for hours to no avail. As soon as I started this service, all worked great. Good Luck!
Wow. After an all-nighter and much consternation, simply activating the SQL Server Browser service enabled me to get this working on Windows 8.
HUGE props and much thanks for taking the time to post your solution.