• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 784
  • Last Modified:

Urgent help needed - Cold Fusion Cold Fusion Admin - Data Source - to SQL Server 2005 named instance

I get the following error when connecting to SQL Server from Cold Fusion Admin - Data Source -


Connection verification failed for data source: mmsi_update
[]java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][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][Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
0
dteshome
Asked:
dteshome
  • 3
  • 2
1 Solution
 
erikTsomikSystem Architect, CF programmer Commented:
make sure that the datasource exist. And you can test the connection. To test that log into the cfAdmin and go to datasource and click on the test connection
0
 
JohnHowlettCommented:
Just a quick suggestion to double check the port number for the instance / datasource.

http://decipherinfosys.wordpress.com/2008/01/02/finding-the-port-number-for-a-particular-sql-server-instance/
0
 
dteshomeAuthor Commented:

* Yes the Data Source exists
* Yes, the error I am getting is when I do a verify on the DS
* SQl Server is using the default port 1422 and the DS states that

Any help will be appreciated
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
dteshomeAuthor Commented:
CORRECTION!

PLEASE READ 1422 AS 1433 - IT WAS A TYPO

* SQl Server is using the default port 1433 and the DS states that

Any help will be appreciated
0
 
erikTsomikSystem Architect, CF programmer Commented:
try recreating the datasource . amke sure you can test the connection inide the CFAdmin
0
 
dteshomeAuthor Commented:
Thank you, everyone.  It turned out that the DS in  Cold Fusion was using the wrong port.  Once I figured out what port SQL was listening on and changed that it worked - I also had to use the IP of the SQL server the instance is running on, does not work with FQDM  only.  

JohnHowlett, thanks for the link, it was very helpful!
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now