Odbc Error Code Im002 Data Source Not Found And No
Contents |
found and no default driver specified"? Article: 01039 Last Reviewed: 9th January 2015 Revision: 6 The data source you are attempting to connect to odbc driver manager data source name not found and no default driver specified windows 7 does not exist on your machine. On Linux and UNIX, SYSTEM data odbc data source name not found and no default driver specified sources are typically defined in /etc/odbc.ini. USER data sources are defined in ~/.odbc.ini. On Windows, data sources are data source name not found and no default driver specified sql server created in Microsoft ODBC Administrator. The available System data sources are listed in the System DSN tab. The User data sources that are available for the currently logged on user are microsoft odbc administrator listed in the User DSN tab. Refer to your ODBC driver's documentation for information about how to create a data source and the connection details that you need to put in it. You do not have permission to access the location where the data source is stored. On Linux and UNIX, you need read access to the .ini file that contains
Data_source_name_not_found_and_no_default_driver_specified
the data source. On Windows, the user account that is attempting to access the data source needs to have sufficient permissions to read the registry key where the data source is stored. System data sources are stored under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. User data sources are stored under HKEY_CURRENT_USER\Software\ODBC\ODBC.INI. On Linux and UNIX, your SYSTEM data sources and / or drivers are defined in non-standard files or locations and you have not set the relevant environment variable to tell unixODBC where to find them. You may need to set ODBCSYSINI, ODBCINSTINI or ODBCINI. For more information, see Linux/UNIX ODBC. The data source is defined for another user. User data sources are defined for a specific user.The Driver attribute is either missing from the data source or has an invalid value. The ODBC Driver Manager relies on the Driver attribute to know which ODBC driver to load.The ODBC driver that the Driver attribute points to is not installed on your machine. On Linux and UNIX, to display a list of installed drivers, type odbcinst -q -d. On Windows, the Drivers tab in ODBC Administrator li
sophisticated digital experiences Web content & Customer Journey Sitefinity CMS Build engaging websites with intuitive web content management Application Development, Testing & Deployment DevCraft Leverage a complete UI toolbox
Microsoft Odbc Driver Manager
for web, mobile and desktop development OpenEdge Build, protect and deploy microsoft odbc_driver_manager _data_source_name_not_found_and_no_default_driver_specified apps across any platform and mobile device Kendo UI Build rich, smart HTML5 and JavaScript apps for microsoft ole db provider for odbc drivers error '80004005' any platform, browser or device Telerik Platform Build mobile apps for iOS, Android and Windows Phone Nativescript Use Angular, TypeScript or JavaScript to build truly native mobile apps http://www.easysoft.com/support/kb/kb01039.html Rollbase Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud Test Studio Automate UI, load and performance testing for web, desktop and mobile Modulus Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud Data Connectivity DataDirect Connectors Optimize data integration with high-performance connectivity Business Rules Management http://knowledgebase.progress.com/articles/Article/3352 Corticon Automate decision processes with a no-code business rules engine View All Products Solutions Digital Business Transformation Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation. Web Scale Globally scale websites with innovative content management and infrastructure approaches Modernization UX and app modernization to powerfully navigate todays digital landscape Omni-Channel Engagement Content-focused web and mobile solution for empowering marketers aPaaS Fuel agility with ever-ready applications, built in the cloud Enterprise Mobility Faster, tailored mobile experiences for any device and data source New & Trending E-book The Digital Ultimatum: Why Businesses Must Digitally Transform to Survive â€" and Thrive Survey Report The State of Digital Business Support & Learning Support Support Services Knowledge Base Customer Order Management Download Center Services Training Consulting Services Managed Database Offering Learning Documentation Webinars How-To Videos Whitepapers Community Blogs Success Stories Partners Company Login Progress Support Rollbase DataDirect Cloud PartnerLink Telerik Your Account Telerik Platform Global Sites Brazil France Germany Netherlands United States Menu
Read Quick Links Today's Posts View Site Leaders Who's Online Advanced Search Forum Attunity Replicate Attunity CloudBeam Amazon Redshift Topics "Data source name not found and no http://forums.attunity.com/forums/amazon-redshift-topics/data-source-name-not-found-no-3168.html default driver specified" when trying to connect t Results 1 to 1 of http://stackoverflow.com/questions/2137618/why-error-odbc-driver-manager-data-source-name-not-found-works-fine-on 1 Thread: "Data source name not found and no default driver specified" when trying to connect t LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this thread Thread Tools Show Printable Version Email this Page… Search Thread Advanced Search Display data source Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 11-09-2015,02:07 PM #1 stevenguyen Senior Member Join Date May 2014 Posts 202 Rep Power 3 "Data source name not found and no default driver specified" when trying to connect t Facing the following error when testing the connection to MySQL from Replicate: RetCode: SQL_ERROR SqlState: IM002 NativeError: 0 Message: [Microsoft][ODBC Driver Manager] Data not found and source name not found and no default driver specified [122502] ODBC general error. ans: Replicate uses 64 Bit ODBC Client to connect to MySql, and the error means that replicate can’t find the ODBC Client. It can happen if: 1. They don’t have the ODBC client installed (This is for the 64 bit version)- Run C:\Windows\System32\odbcad32.exe Check that the driver is listed under the drivers list: 2. If the user is saying that he/she do have it installed and he/she doesn’t understand how it is not listed – This might be because he/she has the 32bit version of the client. To check that – The process is the same as in (1) but you should open the 32 bit ODBC Data source Administrator: C:\Windows\SysWOW64\odbcad32.exe 3. Another explanation is, that they have a different version of The ODBC Driver (Client) than the one we’re looking for– 5.2. In most cases The ODBC client name is not specifying the Version as a part of the name – MySql is different, and it does specify that – “MySQL ODBC 5.2 Unicode Driver” To overcome that issue, just specify the exact dr
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why Error: “[ODBC Driver Manager] Data source name not found…”? (works fine on dev environment) up vote 2 down vote favorite 1 I'm encountering problems in my ASP page. This is a login page which checks the user's credentials to the database before it allows access to the main page. I created a debugger page to find out what's the error details and this is the error message: Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. That's the error message I' m encountering on the web server when I'm loging in to the site. The weird thing here is when testing the page locally on my machine (desktop) everything works fine (even with IIS and MSSQL server). I'm also using the same connection string when deploying and testing the page. Please help, any suggestions or comments will be greatly accepted. Thanks, Nhoyti sql-server asp-classic odbc ado share|improve this question edited Dec 1 '11 at 15:36 Joel Coehoorn 249k92440662 asked Jan 26 '10 at 5:09 nhoyti 15114 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote accepted The problem is probably with the ODBC configuration on the Server itself. In other words the connection string [to the ODBC source] is ok (since tested on other server), but it makes reference to a source that is not configured on this particular server. To remedy the problem, open the ODBC Data Source Administrator (typically one of the shortcuts in the "Administrative" tools menu), and check if indeed you have a source (typically a "System DSN") with the same name found in the connection string. Such Source is probably inexistant or improperly configured. Aside from performance considerations, one may consider using more direct Data Providers (such as MS SQL Data Provider or Microsoft.Jet.OLEDB) at the level of the connection string; this avoids the extra configuration point (the ODBC config panel) on the server (but then this may require using two distinct connections strings, one for the test environment and one for the production environment...) shar