Problem wurde inzwischen beseitigt. Unsere verschwendete Zeit zur Fehlersuche interessiert keinen.
Die Erklärung von Kaspersky - wenn's interessiert:
The reason of the issue is the following:
1) yesterday we updated "system watcher" protection module of Kaspersky security products,
2) this module analyses behavior of the running application in the system to proactively detect new malware,
3) but because this detection is at-runtime, not at-startup some files and registry keys can be already modified/deleted at the moment of detection,
4) this is why system watcher makes backup copies of files/keys before modification by unknown applications run in the system.
5) unfortunately, there was a bug in this functionality related to a rare case when an application tries to open file for writing which does not exist.
System watcher makes a backup copy of this non-existing file but opens file for reading with mistaken attributes (OPEN_ALWAYS instead of OPEN_EXISTING) - this results in creating a new file with 0 bytes size.
6) MS JET (at least 3.5 and 4.0) tries to read SystemDB file and if it simply doesn't exist - continue its work. But if the file exists with unexpected internal structure - JET stops working with an
exception (it's not a right behavior but JET is older than Windows XP). "
Und mit dem MdbFix.exe utility können wir nun die Funktionalität unserer Anwendung(en) wieder herstellen ... so einfach ist das.
Was soll's, ich kann meinen heutigen ersten Urlaubstag nun doch als Urlaub betrachten und muss keinen Supporttag einlegen
