Thanks for all the ideas.
However none of the ideas is sufficient to reproduce the loss of the settings.
I tried re-installing MM meanwhile and this "touched" the wmproperties.lst located under
%APPDATA% and it also changed a few lines (e.g. a line containing the date),
but it did NOT wipe out all settings to defaults :-(
Another idea that I have since a long time:
Modify the Java Code of MM to throw an error instead of silently re-writing the wmproperties.lst
I see currently no better idea to come closer to the root cause.
As Max suggested I changed the java code not to recreate the wmproperties file but instead pop up a dialog asking to retry or to reset. We installed this at some customers an this looks good.
The retry tries to read the wmproperties.lst file again as normal.
The reset creates a copy of the wmproperties.lst file and does a reset as now silently occurs.
The fix is a additional lines of java code in the WMProperties.java.
When you ar interested in the code please let me know.
I am interested in this piece of code.
Could basically write it by myself, but there is no reason to re-invent the wheel.
I guess we at INNEO will make this a Standard customization since our customers are also suffering from sporadic loss of all settings in wmproperties.lst
I am also interested in this piece of code.
Would you please send me an email or contact me at PTC Community in order to submit the code?
Thanks a lot!
I am interested in seeing a copy of your code as well, it may be helpful to some issues we have run into here as well.
Unfortunately the code piece does not completely resolves the problem.
My conclusion after investigating possible causes is the problem lies in the ptc implementation of saving the ModelManager settings to the wmproperties file.
May I ask everyone who experiences the problem contacts PTC support and ask for a proper solution?