MySQL Bugs: #22065: unable to install ODBC driver on Win2003 Server AMD 64Bit

Bug #22065	unable to install ODBC driver on Win2003 Server AMD 64Bit
Submitted:	6 Sep 2006 21:14	Modified:	7 Sep 2006 13:06
Reporter:	Peter Reparon	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	5.X & 3.X	OS:	Windows (Windows Svr 2003 Amd 64 bit)
Assigned to:		CPU Architecture:	Any

Description:
Not able to install the msi of version 3.5X, when looking into the Data source there is nothing avail to pic from the list other than the MS SQL.

With bat version 5.X the upgrade.bat 0 does not work and errors out. the "creatBinaryMsi.bat" does not work either and give erros...lots of them.

Hope this probelm can be correct for the version of NOS I am using.

How to repeat:
run the install on 3.5 X on a wind 2003 srv 64 bit AMD. will not install odbc.
have screen shot to show the issue and that the 3.5X is install but nothing in the DataSource.

run the bat files for beta 5.x and you will receive the same errors. see screen cut and pat for this one:

C:\mysqlconnectorodbcnoinstal504alphawin32>createBinaryMsi.bat 504 p
"+-----------------------------------------------------+"
"| BUILD |"
"+-----------------------------------------------------+"
"+-----------------------------------------------------+"
"| CREATING MAKE FILES |"
"+-----------------------------------------------------+"
'qmake' is not recognized as an internal or external command,
operable program or batch file.
dltest...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCC...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCDbg...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCTst...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCIns...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYSQLPlus...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCDriver...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCSetup...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCInstaller...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
MYODBCShell...
'qmake' is not recognized as an internal or external command,
operable program or batch file.
"+-----------------------------------------------------+"
"| CREATE MAKE FILES DONE |"
"+-----------------------------------------------------+"
"| |"
"| Hopefully fresh make files have been created. Any |"
"| changes to the qmake project files should be |"
"| reflected in these new make files. |"
"| |"
"+-----------------------------------------------------+"
Make...
'nmake' is not recognized as an internal or external command,
operable program or batch file.
"+-----------------------------------------------------+"
"| BUILD DONE |"
"+-----------------------------------------------------+"
"| |"
"| Hopefully things went well and you have results in |"
"| lib and bin sub-dirs. Consider running Install.bat |"
"| next. |"
"| |"
"+-----------------------------------------------------+"
bin\*
The system cannot find the file specified.
0 file(s) copied.
lib\*
The system cannot find the file specified.
0 file(s) copied.
doc\*.hlp
The system cannot find the file specified.
0 file(s) copied.
License.html
1 file(s) copied.
The system cannot find the file specified.
'OdbcMakeSetup.bat' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
'OdbcMakeSetup.bat' is not recognized as an internal or external command,
operable program or batch file.

C:\wix-installer>

even doing the update.bat 0 when 3.5X was to be installed is come back with miss error:

C:\mysqlconnectorodbcnoinstal504alphawin32>upgrade.bat 0
"+-----------------------------------------------------+"
"| ERROR |"
"+-----------------------------------------------------+"
"| |"
"| Connector/ODBC does not appear to be installed. |"
"| |"
"+-----------------------------------------------------+"
Press any key to continue . . .
"+-----------------------------------------------------+"
"| ERROR |"
"+-----------------------------------------------------+"
"| |"
"| Connector/ODBC not built. Consider executing |"
"| Build.bat. |"
"| |"
"+-----------------------------------------------------+"
Press any key to continue . . .
C:\mysqlconnectorodbcnoinstal504alphawin32>

Suggested fix:
Await the developers to be kind in providing a fix.

3.51issue

Attachment: ODBCissue35X.bmp (image/bmp, text), 194.96 KiB.

Hi Peter.
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: 
  This is duplicate of BUG#20301. As for MyODBC 5, it is still in alpha and we are aware there are problems with installation. You should only run (from cmd) install.bat file.