"Chris Benner" wrote:
I just did a search back on our network drive for Pro-E and found 56 std.out files with this error over the last year and a half or so... not counting any that got deleted over that time period.
Well, it is a generic/cryptic/useless error code, but I have encountered it usually when developing JLink applications.
In most cases the crash was caused by a problem in the text file that includes the messages and the most likely cause was either the lack of the two '#' signs at the end of the file or some garbled text in the middle.
Sometimes a simple editor like notepad might add some unreadable letters into the file, or use CR/NL sequences that JLink doesn't like. Notepad++ is very helpful to prevent these cases though.
It is a shame that PTC hasn't added some more useful explanations to their error messages, but.... well...
Just my 0.02$