Dec 03, 2018 According to this article, 'To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:windowssysWOW64odbcad32.exe. To manage a data source that connects to a 64-bit driver, use c:windowssystem32odbcad32.exe. 'Hope the above information can be helpful. Regards, Yuki Sun. We’ve updated our limited warranty terms for Surface, Xbox, and accessories. ERROR: (CheckOFSIConnection)40002: IM006 MicrosoftODBC Driver Manager Driver's SQLSetConnectAttr Failed. '(CheckOFSIConnection)40002: IM006 MicrosoftODBC Driver Manager Driver's SQLSetConnectAttr failed.'
Active5 months ago
I am trying to open a program for the first time on Windows XP Pro that uses PostgreSQL 9. I'm getting an error message that says :
A problem was encountered while trying to log into or create the production database. Details: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
In my ODBC manager, I have a list of User DSN's and System DSN's. I tried installing a postgres odbc driver to see if that would help, but it didn't.
There is a connect.dat file in the program file with a line saying 'OLE DB Provider = MSDASQL'. Changing this entry alters the error message I get to 'Provider cannot be found, it may not be properly installed'.
I don't know what provider name to insert to get this to work properly. I have done extensive research on this error to no avail. Any suggestions would be greatly appreciated.
pnuts
51k88 gold badges6565 silver badges105105 bronze badges
user2437443user2437443
62633 gold badges99 silver badges2222 bronze badges
7 Answers
7,26822 gold badges1515 silver badges2929 bronze badges
PRGSTonyPRGSTony
Got this error because I had the Data Source Name in User DSN instead of System DSN
Jan Doggen
5,4231313 gold badges4848 silver badges9494 bronze badges
Nick
Odbc Driver Manager Error In ExcelNick
1,88722 gold badges2222 silver badges3737 bronze badges
The Problem might be from the driver name for example instead of
DRIVER={MySQL ODBC 5.3 Driver} try DRIVER={MySQL ODBC 5.3 Unicode Driver} you can see the name of the driver from administration tool
MeysamMeysam
I got this with data driven tests using:
The problem is the above driver only is 32 bit. I had switched visual studio testsettings file to 64 bit to test a 64-bit-only application.
Switching back to 32 bit in the testsettings file fixed the issue.
N-ateN-ate
Error Im002 Microsoft Odbc Driver Manager
I tried the above but found my issue was I used a | in the name of the DSN (I have multipled ODBC connectors - one for each DB - to make sure I don't comingle data)
I replaced the | (pipe) with a _ and all now works fine.
I was trying to call SQL Server from Alteryx.
calepcalep
Following the instructions here http://help.loftware.com/pages/viewpage.action?pageId=27099554 I had to install the Microsoft Access Database Engine 2010 Redistributable before I had the Excel driver installed to use the DSN-less connection I wanted to use from perl.
Matthew LockMatthew Lock
8,63477 gold badges6868 silver badges113113 bronze badges
if you are using IIS, maybe you should try
'application pools' --> 'DefaultAppPool' --> 'application pools default value'--> '32-Bit-application-activ' --> set false
leslieleslie
Not the answer you're looking for? Browse other questions tagged odbcinstallpostgresql-9.2 or ask your own question.
I’d love to take a look at this.
Can you share the repro steps and the dev version driver?
Thanks
From: Davvid [mailto:[email protected]]
Sent: Monday, July 20, 2015 6:36 AM To: Azure/msphpsql Subject: Re: [msphpsql] SQLSTATE[HY010]: [Microsoft][ODBC Driver Manager] Function sequence error (again) (#49)
I am seeing this error consistently on Drupal 8 - MSSQL integration (and is preventing any further development because it breaks man automated tests..).
Unluckily, the circumstances that lead to the error are so complex that I was unsuccessfull at isolating a test script. I even tried to PROXY all operations on Drupal's database abstraction layer to later reproduce every single operation done against the PDO driver without luck, the error simply won't reproduce.
If you are interested in helping solve this out to get D8 working on MSSQL Server, I can provide the exact steps to reproduce on a clean D8 install. You will need the -dev version of the SQL Server driver for Drupal - that I can only share privately at the moment.
--
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-122886221. Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |