Windows Server Version 2012 R2 64bit
CPU: Intel XEON X5650
RAM: 4GB

Hi Sven,

which version of ODBC driver do you use? 32-bit or 64-bit?

/Georg

Hi Georg,

Im using 64 bit.
Sorry forgot that detail.

Hi,

I just installed the 32bit and 64bit versions of the ODBC v1 drivers to finally get rid of the remaining parts of MySQL on my Windows 2012 R2 server, and like Sven I am having issues.

The 32bit driver using the 32bit ODBC control panel allows me to choose the driver, but when I try to test the connection it's succesful but then crashes:

Faulting application name: odbcad32.exe, version: 6.3.9600.17415, time stamp: 0x5450470f

Faulting module name: ntdll.dll, version: 6.3.9600.17668, time stamp: 0x54c846bb

Exception code: 0xc0000374

Fault offset: 0x000e5934

Faulting process id: 0x5e00

Faulting application start time: 0x01d067dd0af6c555

Faulting application path: C:\Windows\syswow64\odbcad32.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 5c90a291-d3d0-11e4-94a4-08606e694917

Faulting package full name: 

Faulting package-relative application ID: 

The 64bit driver using the 64bit ODBC control panel crashes the moment I choose the driver and click next:

Faulting application name: odbcad32.exe, version: 6.3.9600.17415, time stamp: 0x545050b9

Faulting module name: maodbcs.dll, version: 0.0.0.0, time stamp: 0x54c8d6c0

Exception code: 0xc0000005

Fault offset: 0x0000000000009a0c

Faulting process id: 0x6510

Faulting application start time: 0x01d067db30274457

Faulting application path: C:\Windows\system32\odbcad32.exe

Faulting module path: C:\Program Files\MariaDB\MariaDB ODBC Driver 64-bit\maodbcs.dll

Report Id: 7c7de12e-d3ce-11e4-94a4-08606e694917

Faulting package full name: 

Faulting package-relative application ID: 

For now I have reverted back to using the MySQL ODBC drivers as they still work

Really sorry for problems like these.
The bug with test button is fixed in the repoditory.
Here is diff fixing 64bit setup library problem

diff --git a/dsn/odbc_dsn.c b/dsn/odbc_dsn.c
index e4096d1..13d97b8 100644
— a/dsn/odbc_dsn.c
+++ b/dsn/odbc_dsn.c
@@ -666,7 +666,7 @@ my_bool DSNDialog(HWND hwndParent,

notCanceled= TRUE;
hwndMain= CreateDialogParam(hInstance, MAKEINTRESOURCE(IDD_DIALOG1), 0, DialogProc, 0);

• SetWindowLongPtr(hwndMain, DWLP_USER, (LONG)Dsn);
  + SetWindowLongPtr(hwndMain, DWLP_USER, (LONG_PTR)Dsn);

/* Setting first not disabled page */
CurrentPage= -1;

I will push it later today.

Hi,

Installed mariadb-connector-odbc-1.0.0-win64 and when trying to create new data source for Maria DB it shows the error "ODBC Administrator has stopped working" and the issue is due to "Fault module name : maodbcs.dll".

@Rajamani, did you not read any of the above thread?

When will this make production?

@ Taomun I have read the above comments and my comments yesterday is to Novitsky to know when the bug fix will come to production since he mentioned he will push the fixes two days ago.

@Rajamani, no your comment made no such request about when the bug fix will be made, it simply repeated the problem which is already mentioned in the previous messages and a waste of time.

Well, preparing release is time consuming process, as well as updating connector on user machines.
There is already enough stuff to release. I need to finish ODBC-21(it affects 1.0.x as well and is pretty bad), and verify, and fix if needed, one more issue. Then will release-time. Hopefully till and of this week, otherwise next week.
Lawrin

For all those suffering from this problem. There is a temporary workaround.
[https://social.technet.microsoft.com/Forums/windows/en-US/4cea8098-fa08-489f-99ca-ee3ab5592dc0/odbc-data-source-administrator-64bit-crashes-when-i-try-to-invoke-postgresql-ansix64-or?forum=w8itprogeneral
]
It is for PostgreSQL but also works for MariaDB ODBC.

I'm having the same problem (on Win7-x64). I got MariaDb recommended by others but it seems they have egg on their face as I'm not even able to connect in the first place. I expected MariaDb to be a better MySQL!
It seems we'll be sticking with MS SQL Server for the time being.

 Is there any progress on this problem?

This issue has been fixed in the latest Connector/ODBC 1.0.5 release