| Bug #50050 | Unable to register a new server instance | ||
|---|---|---|---|
| Submitted: | 4 Jan 2010 13:25 | Modified: | 15 Feb 2010 15:11 |
| Reporter: | Jose Carlos Santos | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
| Version: | 5.2.11 OSS Beta Revision 4842 | OS: | Any |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
| Tags: | Instance Manager, MySQL Workbench | ||
[4 Jan 2010 14:59]
Peter Laursen
A remark: This will have to be reproduced with 2K/XP/2003 as there is a significant difference between Windows up to and including XP/2003 and later Windows. XP-- : Localized file paths for system folders (as for *everything localized* - window titlebars and whatever) are hard-coded into Windows binaries and shared libraries (.exe/.dll). Vista++ : Here localization of the GUI is achieved with language files (what you can actually replace if you are using a ULTIMATE edition of WIndows) and in the command interface everything is English. But I agree that %ProgramFiles% should be used - what will then be resolved by the OS. And also the *resolved* path will be returned in (error) messages. Peter (not a MySQL person)
[6 Jan 2010 14:39]
Mike Lischke
The given path to the configuration file is only an example. You can easily change that at a later state in the wizard. It will not at all prevent you from creating a new server profile. If it later works is completely up to you, as anything can be changed by the user.
[8 Feb 2010 21:20]
Alfredo Kojima
Added expansion of %ProgramFiles% and %ProgramFiles(x86)% for config file paths. Also added new templates for 64bit windows running 32bit mysql
[10 Feb 2010 18:10]
Louis Breda van
Hello, I have the same problem over here on my vista64 bit system running 5.5 64 bit server. Even creating a C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS\mysql.profiles\Windows_(MySQL_5.5_x64_Installer_Package).xml did not help. So I did work arround the problem using a hardlink (yes, windows can do that :> a bit late and not as good as my commodore amiga could 20 years ago) I took the following: - start a cmdshell as operator - C:\Windows\system32>cd c:\ - create the workbench expected "Program Files"\mysql\"MySQL Server 5.1" dir - c:\>cd "Program Files"\mysql\"MySQL Server 5.5" (use of course your own path) - c:\Program Files\MySQL\MySQL Server 5.1>mklink /H my.ini "../MySQL Server 5.5/my.ini" (to create the hardlink) - Harde koppeling gemaakt voor my.ini <<===>> ../MySQL Server 5.5/my.ini Now you can define your server with the workbench. Note that during this proces the location of the ini file is asked (a bit late). Assume this helps as work around Sincerely, Louis
[12 Feb 2010 23:29]
Johannes Taxacher
fixed in repository
[15 Feb 2010 15:11]
Tony Bedford
An entry has been added to the 5.2.16 changelog: In the Create a new server instance wizard, if an operating system of type Windows (MySQL 5.1 Installer Package) was selected, then the following error was generated on the Test Settings page: Error: File C:\Program Files\MySQL\MySQL Server 5.1\my.ini doesn't exist This was because the file was actually stored in C:\Programas\MySQL\MySQL Server 5.1\my.ini.
Description: If I do: New Server Instance -> Localhost -> Next -> Select "Windows (MySQL 5.1 Installer Package)" -> Next then I get the error message: Error: File C:\Program Files\MySQL\MySQL Server 5.1\my.ini Indeed, the file does not exist. I use the Portuguese version of Windows and therefore software is installed at a folder called "Programas", not "Program Files". How to repeat: Do: New Server Instance -> Localhost -> Next -> Select "Windows (MySQL 5.1 Installer Package)" -> Next Suggested fix: Where the file my.ini should be looked for is at %ProgramFiles%\MySQL\MySQL Server 5.1\my.ini This is, I think an universal solution.