I've been trying to install the ODBC extension for PHP onto one of our servers ( Redhat and i think it got it installed correctly but now when i try to test the connection i get the error message about the data source name being too long. It sounds like a simple thing to fix, but i can't work out.how.or where. Basically these are the settings i've got at the moment: odbcinst -j DRIVERS.: /etc/odbcinst.ini SYSTEM DATA SOURCES: /etc/odbc.ini FILE DATA SOURCES.: /etc/ ODBCData Sources USER DATA SOURCES.: /root/.odbc.ini SQLULEN SIze.: 4 SQLSETPOSIROW.: 2 I've got my My SQL driver defined in the odbcinst.ini as such: [ My SQL] Description = ODBC for My SQL Driver = /usr/lib/libmyodbc5.so Setup = /usr/lib/libodbcmy S.so File Usage = 1 I've double checked and the Driver [mytest] ;driver = My SQL ; Database = moodle ; Server = localhost ; Socket = /var/lib/mysql/mysql.sock ;[mynew] ; Description = My SQL ; Driver = My SQL ; SERVER = localhost ; USER = root ; PASSWORD = ; PORT = 3306 ; DATABASE = moodle [ Default] Driver = /usr/lib/libmyodbc5.so Description = Connector/ ODBC 5 Driver DSN SERVER = localhost PORT = USER = root Password = Database = moodle SOCKET = However, whenever i run isql -v to see if there are any problems, i always get: [ IM010][unix ODBC][ Driver Manager] Data source name too long [ ISQL] ERROR: Could not SQLConnect My googling around the error only ever seems to turn up results for people having a connection.
Dev Articles Community Forums Sponsor: May 21st, 2004, 03:20 PM Registered User Join Date: May 2004 Posts: 2 Time spent in forums: Reputation Power: 0 Data source name not found and no default driver specified Help! I can connect fine to my Db from my test server at home but when I move it to my server (my web server and SQL server are on the same machine) I get the following error: Microsoft OLE DB Provider for Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [ Microsoft][ ODBC Driver Manager] Data source name not found and no default driver specified Can someone please lend a hand. Thanks! May 22nd, 2004, 02:23 AM May contain nuts. Join Date: Aug 2002 Posts: 2,056 Time spent in forums: 5 h 44 m 22 sec Reputation Power: 0 How are you connecting to the DB on the production server? DSN, DSN-less? If DSN, is the DSN setup correctly on the live server? If DSN-less, is the driver present? Does the live DB server have the same name, db? May 22nd, 2004, 12:44 PM Registered User Join Date: May 2004 Posts: 2 Time spent in forums: Reputation Power: 0 it's connecting to a server DNS. August 18th, 2004, 07:00 AM Registered User Join Date: Aug 2004 Posts: 1 Time spent in forums: Reputation Power: 0 fix: Delete the USER data source name and define it as a SYSTEM data source name. In Windows 2000: -> Start -> Settings -> Control Panel -> Administrative Tools -> Data Sources ( ODBC - User DSN : delete the specified User DSN - System DSN : create a new System DSN September 21st, 2005, 12:23 PM Registered User Join Date: Sep 2005 Posts: 1 Time spent in forums: 8 m 7 sec Reputation Power: 0 Data source name not found and no default driver specified Hi there. What's the fix when using a non- DSN connection? Thanks in advance, another Newbie October 9th, 2005, 06:38 PM May contain nuts. Join Date: Aug 2002 Posts: 2,056 Time spent in forums: 5 h 44 m 22 sec.
A connection string has the following syntax:connection-string := empty-string[;] | attribute[;] | attribute; connection-stringempty-string :=attribute := attribute-keyword=attribute-value | DRIVER=[ ]attribute-value[ ]attribute-keyword := DSN | UID | PWD | driver-defined-attribute-keywordattribute-value := character-stringdriver-defined-attribute-keyword := identifierwhere character-string has zero or more characters; identifier has one or more characters; attribute-keyword is not case-sensitive; attribute-value may be case-sensitive; and the value of the DSN keyword does not consist solely of blanks. Because of connection string and initialization file grammar, keywords and attribute values that contain the characters []?*=!@ not enclosed with braces should be avoided. The value of the DSN keyword cannot consist only of blanks and should not contain leading blanks. Because of the grammar of the system information, keywords and data source names cannot contain the backslash (\) character. Applications do not have to add braces around the attribute value after the DRIVER keyword unless the attribute contains a semicolon in which case the braces are required. If the attribute value that the driver receives includes braces, the driver should not remove them but they should be part of the returned connection string. A DSN or connection string value enclosed with braces ( ) containing any of the characters []?*=!@ is passed intact to the driver. However, when using these characters in a keyword, the Driver Manager returns an error when working with file DSNs but passes the connection string to the driver for regular connection strings. Avoid using embedded braces in a keyword value. The connection string may include any number of driver-defined keywords. Because the DRIVER keyword does not use information from the system information, the driver must.
Download Now