Bug #9848 | Application does not start | ||
---|---|---|---|
Submitted: | 12 Apr 2005 14:58 | Modified: | 3 Aug 2005 8:17 |
Reporter: | Guillaume Patry | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.0.3 alpha | OS: | Windows (windows XP) |
Assigned to: | CPU Architecture: | Any |
[12 Apr 2005 14:58]
Guillaume Patry
[12 Apr 2005 16:03]
MySQL Verification Team
I wasn't able to repeat this issue on my XP box.
[20 Apr 2005 23:09]
Saleh Jamal
I am having the same problem here. version: 1.0.5-beta OS: Windows XP SP 1 the only difference I see in the error message is: Error Nr. 10008 instead of 10003 I use MySQL Administrator, MySQL Query Browser, MySQL server 4.1.2-alpha and they all work fine except for the migration suit
[21 Apr 2005 6:51]
Guillaume Patry
I fixed this issue by completely uninstalling both MySQL Migration Toolkit, all the instance of JRE. Once made, I install the JRE 1.4, install the MySQLMigration Toolkit 1.0.2 and it's worked fine. After that, I install the JRE 1.5 and it was still running. Hope this will work for you. Guillaume.
[3 Aug 2005 3:47]
Carlos Martinez
I have the error only the number changes Exception Exception in module MySQLMigrationTool.exe at 001A129C. The GRT environment could not be initialized. The call of Migration:init Migration() failed. The function did not rerturn an object. Error Nr.10003
[3 Aug 2005 8:17]
Michael G. Zinner
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Additional info: Please uninstall 1.0.3 and try with 1.0.12. This should solve the issue. If this still does not work, please start the tool from the command line with the -verbose argument. If you have Java 1.4 uninstalled and 5.0 installed, please make sure that your registry entry HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.4 does not contain an invalid path. You can also override this from the command line with the -jvm pathToJvm argument.