MySQL Bugs: #60369: Cannot open saved work bench file

Bug #60369	Cannot open saved work bench file
Submitted:	7 Mar 2011 11:31	Modified:	24 Mar 2011 16:00
Reporter:	Gareth Watson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S1 (Critical)
Version:	5.2.32	OS:	Any (Windows XP SP3, Mac OS X)
Assigned to:		CPU Architecture:	Any
Tags:	Cannot, error, open, Unserializing

Description:
I have saved a model and now when I come to open it I cannot.  I get the error:

Error unserializing GRT Data.  Expected Type db.mysql.Column, but got db.mysql.Table.

How to repeat:
I have an MWB that demonstrates the problem but I am not sure what I have done to cause it.

I've got the same error message when I tried to open the .mwb file you uploaded with 5.2.32 on Mac OS X.

Bug #60372 was marked as a duplicate of this one.

bug #60377 is a duplicate

bug #60357 is a duplicate

Are there any workaround for this? Thanks.

I was trying to get a previous version without this issue, but seemed that they are not available. Sign~~~

The only work-around I know is to keep syncing the model with a database.  Then when MSB chews up the file at least you only need to reverse engineer the existing database and re-layout the model.

Of course all your notes, layers and captions are lost :(  But it is the best I have been able to come up with until the problem is fixed.

Investigating a little on my own, it looks like the ID's in the file are duplicated across multiple objects.  I had some success creating my own ID's for each object but it was time consuming to say the least.

Hope this helps someone,

Gareth.

Thanks. I am doing that. I got a 5.2.31 version. Seems there is no this issue.

Please try version 5.2.33, which solves the issue and also attempts to auto-restore damaged models.

This problem was fixed in 2.33 but introduced some other problems. It got crashed very often. Workbench crashes everytime when I try to sync the module with MySQL database. I am worried about the quality of MySQL database now.

This problem was fixed in 2.33 but introduced some other problems. It got crashed very often. Workbench crashes everytime when I try to sync the module with MySQL database. I am worried about the quality of MySQL database now.

T Cui: Can you upload your model to see what's wrong?

@T C: can you open a separate report about that crash problem?
If possible provide your model file (can be marked private) and describe when the problem appears (step-by-step description on how to reproduce, if possible).
thanks

Using Version 5.2.33
Windows XP SP 3

I generated a model by reverse engineering an existing database with over 110 tables.  I then updated the model to the point where I'm down to 70 tables with a lot of modifications.  The model saved fine last night but opening this morning I get the serialization error as described above.  I have not synchronized my model with the database as these are major changes and I wasn't ready to do that yet.

What are my options?  Did I lose all my work?  I saw it stated that version 5.2.33 had a fix for this issue and that it would even attempt to repair broken models.  This occurred for me in version 5.2.33 and I have not seen any mechanism to repair a broken model.

This is a major issue if people can't be comfortable saving models if they don't know if they'll be able to open them again.  Makes the tool un-usable.

I just lost 6h of work with this bug. Thanks, mysql workbench team!!!

If your model cannot be opened anymore, upload it here or email it to me and I'll send you back a fixed version.

Meanwhile, please try using the packages from:
ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-5.2.33a-win32.msi
ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-5.2.33a-win32-noinsta...

because we're unable to repeat the problem, we'd appreciate for feedback telling whether the problem happens again or not.

Hello Alfredo,

I have uploaded the file, can you please send me back the working file?
I have tried the versions suggested by you, but i still get the unserializing grt error.

Thank you!

Hello Alfredo,

I have uploaded the file, can you please send me back the working file?
I have tried the versions suggested by you, but i still get the unserializing grt error.

Thank you!

The packages I linked may or may not open damaged models, but it should prevent the models from getting damaged in the first place. Please use them instead of .33 and report back if you can work normally, ie: making changes, saving and reopening the model.

having the exact same issue. lost a good deal of work.

version 5.2.33

I have had the same issue with 2.33 - I did see a link to 2.33a but that ftp link doesn't finish downloading. I have uploaded my file that I was working on yesterday but won't open today.

I created a database and saved it.  When I went to open it the following day I received an error message that states: 
Cannot open, Error unserializing GRT data, type mismatch: expected object of type. db.mysql.column but got workbench.physical.tablebench

Hi,

I have the same problem, i cant open it.

With the version "5.2.33b" i can open the file without any problem!

Thanks a lot!

I had the same problem with "5.2.33",
tryed "5.2.33a" with no success
tryed "5.2.33b" with success, yay ! 'problem solved'

anyone with the same problem, get it there :
ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-5.2.33b-win32.msi
or
ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-5.2.33b-win32-noinsta...

Hello.
I Have this problem, update with this version and i can restore the information¡¡¡
Many thanks¡¡¡
Regards
Victor

I have the same problem not solved.
Please, restore my EER model.

Type mismatch: expected object of type db.mysql.Column, but got db.mysql.IndexColumn

Attachment: pokerloucoModel.mwb (application/octet-stream, text), 25.52 KiB.

Thanks!
Version "5.2.33b" helped to solve bug described in start.

Hello,

I got the same problem with the message "Error unserializing GRT data. Type mismatch: expected object of type db.ForeignKey, but got db.mysql.Column."

I tried the recommended version 5.2.33b, but it did not work.

Any help is very appreciated!

Jens

Jens, upload your model here and I'll email you back with a fixed one, if I'm able to manually fix it.

An entry has been added to the 5.2.33b changelog: 

It was not possible to open a saved model. The following error was generated: 

Error unserializing GRT Data.  Expected Type db.mysql.Column, but got 
db.mysql.Table.

Hi Alfredo,

thanks for your help in advance! Could you please send me an email so I can mail the file to you?

Jens

I have de same problem!!! There are 2.33b version for windows64?

Hi Alfredo,

thanks for your first email! I tried to answer you but did not get through. All emails to you came back. Please contact me again so I can send you my file!

Jens

Corrupted 5.2.33 .mwb file

Attachment: training.mwb (application/octet-stream, text), 15.35 KiB.

Alfredo, I experienced the same problem.  If at all possible, can you fix it?  I've uploaded the corrupted file.  Thanks!

Nevermind.  I installed 5.2.33b and was able to open the file without a problem. Thanks!