I am using a 32-bit Windows machine for development enviorment and i am connecting to my database using
adapter: sqlserver mode: ODBC dsn: xxx_development username: sa password: xxxxxxxxx convert_numeric_literals: true
It is working fine in the development mode , Now i want to test the set up before moving to Production system , So i deployed all the required elements( ruby , rails , mongrel , apache .. etc ) to a stagging server which is a 64-bit windows machine, now i am not able to connect to my database using this set up , though the credentials used for connection are the same for both the enviorments.
Is it because i am using a 64-bit machine instead of a 32-bit ..... or something that i am missing....?
It is not possible to tell for sure what is wrong without looking at logs.
Does your DB stayed on old 32-bit machine or moved to 64-bit too?
I'd suggest that you double check:
- If you can connect to your DB from machine with RoR environment using some client (mysql for MySQL db, psql for Postgres, etc.) and the same user credentials used in your database.yml
- Test database connectivity from ODBC source setup dialog
- Make sure that ODBC driver you setup is 64-bit compatible
- Check what is in your RoR log files.
That would be much easier of course if I could look at the setup myself . If that is not possible - please check things I iterated above and tell me about the results.
Thanks for the post Joshi
Below are my reply to your checklist
Does your DB stayed on old 32-bit machine or moved to 64-bit too? ME - No database is still in 32 bit
Iâ€™d suggest that you double check:
Test database connectivity from ODBC source setup dialog Me - We checked this, this is working properly
Make sure that ODBC driver you setup is 64-bit compatible Me - ODBC driver we have currently is 32 bit compatible for SQL Server
Check what is in your RoR log files.
IM002 (0) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
That is strange, if it worked before on old machine and driver is working on new machine too, there is no reason why link "Active Record" -> ODBC should fail. OK, one stupid question - when moving to 64 bit system you configured the ODBC datasource on it too? And check ODBC driver connectivity on 64 bit machine? (just to be on a safe side). Microsoft tends to be not very descriptive with error messages, so this error message can mean something VERY different.