I'm unable to connect to database thru cold fusion

[UniquePro]

I'm unable to connect to database thru cold fusion. it sometiems give me an error that your uname is undefined , soemtimes it gives ur index page not found so i created index page also but still im unable to connect to database n update my records..plz help me out..im a fresher in cold fusion

[BKBK]

Your Coldfusion version? Database server version?

[UniquePro]

Cold Fusion Version is 8 and Database Server Version is 2003

[Guest]

I am having a similar problem having CFMX 7.02 verify my SQL Server 2005 Data Sources.

I am using the sa account for CF to access the db's. But i get the following error:

Connection verification failed for data source: myDatabase
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect

Every role in SQL Server has the sa grantor Grant enabled. I can also login to SQL Server with the sa account w/o a hitch.

I don't know what else to do. The server information is set to the ServerName port 1433, datasource name and database name are the same as the database name in sql server, and the username and password are set for the sa account.

Thanks!

[BKBK]

> Database Server Version is 2003
You should say whether it is MS Access, MySQL, Oracle or MS SQL.

[UniquePro]

MS SQL

[BKBK]

Dr. Goomba, in situations like these, it is better to start your own thread. However, here is a previous thread on how to set up the SQL Server 2005 data source in the Coldfusion Administrator

[BKBK]

If MS SQL Server 2005, then follow the link in my last post for a possible solution.

[scooter5791]

Dr. Goomba,

Aside from the other comments, using the built-in 'sa' account is not a good idea in terms of security. You should create a new database user for your site assigning the minimum security rights needed.

[Guest]

Its just a development machine so i am not too worried. But i will keep that in mind. Thanks!

[cheftimo]

Dr. Goomba:

Using the'sa' account/Windows authentication, I was having the exact same problem you described. Creating a new login using the server authentication fixed it.

Carlos

[Guest]

My problem was that i didn't have TCP/IP enabled in SQL Server and i was pointing the datasource to the servername rather than 127.0.0.1. Which shouldn't make a difference, but it won't work if i use the name.