Import DB Schema from ODBC source - Crashes

[Nick B]

Have submitted the following bug report - posting here in case anyone else has come across this or has any ideas:

Get message:
"Enterprise Architect - UML Development Tool has stopped working" with option to Debug or Close.

Importing very simple schema (two tables) from a SQLServer 2012 DB. I've also tried this on a different (still Windows machine with one test table, no special data types, basically as simple as I could make it - still fails.

Note that the import DOES seem to work; I just have to restart EA each time I run an import. Of course, I can't be sure that it isn't missing something from the end of the import.

[Nick B]

Brief update on this:

Current theory is that it is a Windows 8 incompatibility, but hard to believe I am the only person in the world importing DB schemas on a Windows 8 machine (8.1 enterprise to be exact).

Anyone else?

Nick.

[smendonc]

I have the same issue on a specific machine running Windows 8.1 x64 enterprise.  The issue started after I had the machine wiped and a clean OS installed.  I did not have the problem before the machine was rebuilt, it was running the same OS but had been upgraded to 8.1 from 8.0.  A debugger trace indicated that EA was making a call to the .net 4 runtime that result in a kernel memory violation and the OS shut down EA as soon as this happened - same information as gets logged in the Windows application event log.  Investigating a bit further I discovered that the .net 4 runtime has been replaced with 4.5.2 which should be completely backward compatible.

I mention all this because I installed Server 2014 on a different machine which also has the newest runtime and have had no issues so far.

[Nick B]

Looks like I am on 4.5.1, so perhaps that is is. Thanks.