MySQL Bugs: #80017: Error unseralising GRT data when opening a .mwb file

Bug #80017	Error unseralising GRT data when opening a .mwb file
Submitted:	17 Jan 2016 11:48	Modified:	25 Jan 2017 23:21
Reporter:	Will B	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	6.3.4, 6.3.7	OS:	Windows (7)
Assigned to:		CPU Architecture:	Any

Description:
Whenever I try to open a .mwb Ive created previously, I get the error message "Cannot open <filename>. Error unserializing GRT data string too long. 

Ive seen this looks to have been resolved in earlier versions, but I still have it. Very occasionally the file will open, but 99% of the time it fails with the above message. 

How to repeat:
Continue to try to open the file.

Hello Will B,

Thank you for the report.
I could not repeat the issue with sample .mwb file, could you please upload your .wmb file to reproduce the issue at our end? You may want to mark it as private after uploading here. Also, WB 6.3.4 is old and many bugs were fixed since then. Could you please try latest WB 6.3.6 GA and see if it works?

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Umesh

Can you tell us the status, because I have now the same problem!
Installed the latets commutity version(MySQL 5.7.11) complete and can not load the sample databasis beloniging to this version ??

Hi,

Unfortunately I didnt get anywhere with it as I cant upload my .mwb file as its too commercially sensitive.

Kind regards,

Will

Observed this today 2/10 times when opening Skila WB file from 6.3.1 using WB 6.3.7

[Window Title]
MySQL Workbench

[Main Instruction]
Cannot open document 'D:\Workbench\MySQL Workbench 6.3.1 CE (winx64)/extras\sakila_full.mwb'.

[Content]
Error unserializing GRT data
string too long

Screenshot..

Attachment: 80017_6.3.7.png (image/png, text), 160.62 KiB.

Had the same problems, happens only occasionally. On second attempt, I get the message 'Opening another model will close the currently open model' and yet there is no model visibly open. running sql Workbench 6.3.6

Hoping that this additional info helps someone: - Closing the open 'local Instance' database tab allows me then to open the model as normal. It's not great but its better than closing everything down and restarting SQL Workbench

same problem to me, version 6.3.8 (Win10x64)

Has happened here a few times. Build 6.3.8 (Community). Happened after using Database \ Synchronise Model, selecting some "update model" items where foreign keys were involved.

Still happens in 6.3.8 after creating a new file with this version.
Any idea how to work around this bug?

http://bugs.mysql.com/bug.php?id=84387 marked as duplicate of this one.

Hi,

I go the same issue, but the following workaround seemed to fix it:

1) shut down Workbench (6.3)
2) find the mwb file in explorer.
3) double click it ... opens Workbench and the model file loads ok.
4) subequent 'clicking' on the mwb in Workbench loads the model i.e. the problem seems to have been fixed.

Hope this helps.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry:

Opening a saved .mwb model file with MySQL Workbench generated the
following error intermittently: Error unserializing GRT data string too
long. The same file, when opened directly from the file system, started
MySQL Workbench and displayed the model correctly.

Thank you for the bug report.

not fixed in 6.3.9. I just upgraded to workbench 6.3.9 (community) on the strength of developer comment.(Running window 7 64bit). After running some queries via workbench I try and open the MWB and get the 'error unserializing data string too long'. I also notice that if I close the error message and try to open again, Workbench is under the impression that its already open! giving me the 'Opening another model will close the currently open model. Do you wish to proceed opening it?
If I than navigate to the actual file location and double click - mysql workbench reverts to the  default screen. Without shutting down Workbench but just closing the local instance tab and then repeating the above process - the error does not occur. I'm hoping that this helps isolate and fix this annoying bug.

Not fixed. On 6.3.9 build 10690321 it still occcurs.
Workaround as suggested by Lather is :

"Closing the open 'local Instance' database tab allows me then to open the model as normal. "

That Works, removing a lot of anxiety.

I'm running MySQL Workbench version 8.0 and trying to complete a college assignment. This bug is ridiculous, who said it was fixed??? It is still present almost 2.5 years later. Opening the .mwb file from Windows Explorer loads it perfectly, any other way and it autodeletes tables.

still got this bug on 8.0

Had same issue on 8.0.15 (win 10 pro x64).

Please reopen, the same bug is still present with the 8.0.15 version on Windows 10 x64

I can confirm - happens to me as well (8.0.15 on Windows 10 x64). Closing all connections before is still a valid workaround.

I don't know if this helps, but my last change before the issue appeared was to increase a VARCHAR column size to 1000.

This error is still occurring when I try to open a model from within Workbench. Double-clicking on the model file to open it still works.

I also just had this same error ( I see this has been a recurring problem for years now ) The above fix of just opening the file directly by Allan Masson on Jan 2017 did indeed work. What I noticed though when I tried to open it from history was it showed C:\Program Files\MySQL\MySQL Workbench 8.0 CE/extras\sakila_full.mwb
To the best of my knowledge the / in between CE and extras is creating a bad file location of sort and that may be why it is not opening. For whatever reason it saves a recent history with the wrong slash is beyond me but it may the the root of the problem and would explain why it works normally when just finding the file and double clicking to open it.

I just had the error occur as well. If I double-click the .mwb file in File Explorer, it opens fine.

Workbench Version 8.0.20 Build 16114288 (64 bits) Community

Windows 10 Pro Version 1909 OS Build 18363.900

Thx Allan Masson, did it and it worked. Was using sakila for studying purposes.