Bug #11097 | Migration Toolkit crashes on startup - fails to run | ||
---|---|---|---|
Submitted: | 4 Jun 2005 16:05 | Modified: | 6 Jul 2005 19:35 |
Reporter: | Jorge del Conde | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.0.7 | OS: | Windows (WinXP) |
Assigned to: | CPU Architecture: | Any |
[4 Jun 2005 16:05]
Jorge del Conde
[4 Jun 2005 16:06]
Jorge del Conde
bug
Attachment: Image1.png (image/x-png, text), 15.12 KiB.
[4 Jun 2005 16:06]
Jorge del Conde
bug2
Attachment: Image2.png (image/x-png, text), 13.05 KiB.
[5 Jun 2005 0:40]
Jorge del Conde
I'm not sure what the problem is. I just tested MT on another computer and it executed fine. The computer that I had a problem with, has the following specs: AMD 64 bits WinXP Pro (32 bits) (recently formatted & reinstalled) The computer that it ran well on is an intel P4.
[6 Jun 2005 19:35]
Michael G. Zinner
Could you try to run the grtsh.exe shell that is located in the installation directory and tell if you are able to use it?
[7 Jun 2005 13:09]
Nikolai Saoukh
Looks like the installer rather naive one. It assume that installation directiory is always C:\..... In my case it was G:\.... The cure is simple -- just edit 'startup directory in shortcut.
[8 Jun 2005 1:58]
Markus Popp
I've got the same problem. When I start the fresh installed MySQL Migration Toolkit on my (German) Windows XP SP1 I get the error message Die Ausnahme "Unbekannter Softwarefehler" (0x0eedfade) ist in der Anwendung an der Stelle 0x77e53887 aufgetreten. After confirming this dialog box I get another one saying Application Error Exception Exception in module MySQLMigrationTool.exe at 001A129C. The GRT environment could not be initialized. The call of Migration:initMigration() failed. The function did not return an object. Error Nr. 10003.
[6 Jul 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".