error odbc mss dataserver

por | 2 marzo, 2015

http://knowledgebase.progress.com/articles/Article/P132010

Progress Software

Company Info
Contact Us
Worldwide
Try Now

Products
Products Overview
Corticon
DataDirect
DataDirect Connect
Data Integration Suite
Data Source
OpenAccess SDK
Other
Modulus
OpenEdge
Pacific
DataDirect Cloud
Easyl
Rollbase
Solutions
Solutions Overview
Solution By Category
Application Deployment
Application Development
Business Rules Management
Data Connectivity
Platform as a Service
Self-Service Data Integration and Collaboration
Solutions By Role
CFO,COO,Finance or Operations Employee
CIO or IT Employee
CMO or Marketing Employe
Developer or Data Architect
ISV or Business Manager
Resources
Book Club
Case Studies
Documentation
Infographics
Papers
Tech Tips
Tutorials
Videos
Webinars
Partners
Partners Overview
Progress Partner Progress – Progress Partner+
Powered by Progress
Growth Strategies
Our Partners
Global Solutions & Partner Directory
Support & Services
Support and Services Overview
Support Services
Evalution Services
Professional Services
Progress Education
Customer Order Management
Community
Progress Community
Progress User Groups
Progress Blogs

[Email a link to this article]
< Back to search results Artículo Error 6142 when connecting to MS SQL Server via the SQL Server DataServer on Windows 64 bit Versión para imprimir Información Article Number 000012201 Environment OpenEdge 10.0B OpenEdge 10.1x Windows 64-bit Progress 9.1E Windows 64-bit MS SQL 2000 MS SQL 2005 Question/Problem Description Error 6142 when connecting to MS SQL Server via the SQL Server DataServer on Windows 64 bit IM002: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Failed to connect to the database. (6142)
Could not load the setup or translator library
Microsoft SQL Server installed is 32-bit not 64-bit
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
When the 64-bit version of Windows is running, the Progress install properly registers all ODBC drivers – they are just in a different place on x64.
Instead of registry keys added under:
HKLM\SOFTWARE\ODBC\ODBCINST.INI
HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers,
they are added under:
HKLM\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI
HKLM\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers

When configuring the ODBC drivers from the usual executable:
%SystemRoot%\system32\odbcad32.exe or %WINDIR%\System32\odbcad32.exe
These drivers cannot be found as they are created on the 32-bit side of the x64 system. There are currently no 64-bit drivers available for Progress on Windows 64-bit.
Resolution
In order to configure the 32-bit DataDirect Driver, a different DSN Administrator executable needs to be run in order to configure the 32-bit ODBC Drivers.

Create a desktop icon pointing to the following location:
%WINDIR%\SysWow64\odbcad32.exe

This will start the ODBC Data Source Administrator and from here, you will now be able to configure the drivers provided with the license installed.
Workaround
Notes
Attachment
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an «AS IS» basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.
Feedback

Was this article helpful?

Contact Us Careers News & Events Sitemap Privacy Terms of Use Trademarks Pacific Cloud Service Agreement
Copyright © 1993-2014. Progress Software Corporation. All Rights Reserved. See the next generation of application development and data connectivity software, try now!