| Bug #57639 | MsSQL Workbench encountered problem synchronizing database to model | ||
|---|---|---|---|
| Submitted: | 21 Oct 2010 21:10 | Modified: | 28 Oct 2010 21:28 |
| Reporter: | Howard Dolginoff | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 5.2.29 CE Revision 6756 | OS: | Windows (XP Pro) |
| Assigned to: | CPU Architecture: | Any | |
[22 Oct 2010 9:55]
MySQL Verification Team
Thank you for the bug report. Are you able to provide the model file (private if you wish)?. Thanks in advance.
[22 Oct 2010 18:00]
Howard Dolginoff
I deleted the Workbench model and re-reverse engineered it from the database. It's working fine now.
[28 Oct 2010 21:28]
Alfredo Kojima
As it seems the issue was with this specific model, it will be hard or impossible to find out the problem without it. I will close this bug as Can't repeat, but if you find it again, please reopen with a copy of the model attached.
Description: Synchronizing database to model. Completed "Retrieve Object Information" step successfully. Received error when I pressed next button. Error message said "Attempt to read or write protected memory. This is often an indication that other memory is corrupt." The log file reports: Fetching table list. 17 items from pbcregistry 17 items from information_schema OK Fetching view list. 0 items from pbcregistry 0 items from information_schema OK Fetching routine list. 0 items from pbcregistry 0 items from information_schema OK Fetching trigger list. 0 items from pbcregistry 0 items from information_schema OK How to repeat: I have successfully performed this synchronization before. I experienced this problem after adding a new table.