Error code 1108 and 2302

I have discovered that some, but not all, customers' combination stepper memory is completely erased.
This sympton occurs very intermittently and cannot be predicted, but when it occurred, the error codes and messages seen in the Hauptwerk activity log are as follows:

"ERR 1108: XML parsing error at line 1, column 1 ['error occurred while parsing element', ","] when processing the XML file Config.Config_Hauptwerk_xml. Please request assistance from the supplier of the file"

"ERR 2302: the main configuration file 'Config.Config_Hauptwerk_xml' couldn't be loaded"

Even though the user terminated Hauptwerk normally and turned off their PC, when they later turned on the computer and ran Hauptwerk, error messages like that appeared.

They have not seen any error messages or codes when powering off their computers, and they say that after running Hauptwerk, the combination stepper memory disappears 'without any warning message'.

According to reading the posts on the User forum, Martin Dyde recommends using HW after updating PC's drivers and operating system to the latest, and he said to be careful not to turn off the PC incorrectly when exiting Hauptwerk. He also said that Hauptwerk just displays the computer's error code in the activity log.

However, according to what I asked two customers who experienced this error, they said there was no problem at all when they turned on or off Hauptwerk .

Should this be viewed as a temporary, intermittent issue with the SSD?

How can I reliably preserve combination stepper memory of Hauptwerk program?

When other customers have experienced this issue in the past, I found that it was because they turned off their PC before the computer shut down normally, but in this case, there is no way to guess.

If I purchase a support ticket and make an inquiry, will you be able to fix this properly? The advice to keep PC's drivers and operating system updated does not seem to help in this situation at all. I do not allow my customers' computers to connect to the Internet, and I usually install the latest version of Windows, an SSD, and the latest version of Hauptwerk (I installed Hauptwerk 7.0 at that time ).

Instead of doing 'shut down PC' every time you quit Hauptwerk, should you first do 'unload organ' and then send the 'shut down PC' command?

[mdyde]

Hello John,

First of all, provided that your customers do regular backups (either by using "File | Backup ..." within Hauptwerk manually, or by leaving Hauptwerk's automatic weekly backups turned on) then they can always get their settings/combinations back to the point in time of their last backup by restoring that backup ("File | Restore ..." within Hauptwerk). See the "Backing up and restoring your settings and data" section in the main Hauptwerk user guide for more details (pages 31-34 in the current v8.0 version).

The following are the common causes of files getting corrupted (with the settings/combinations/XML files being the most likely ones to get corrupted simply because they're saved more frequently than other types of files):

- Computer not being shut down cleanly. You can usually see whether that was the culprit by looking in the user's log file (get them to send you a diagnostic file and extract it with"Help | View/extract contents of a backup or diagnostic file") after the corruption problem has occurred: if Hauptwerk exited cleanly then an "INF:0403 Hauptwerk has finished shutting down" line should precede each "INF:4165 Welcome to Hauptwerk" line.

- A RAM board fault (which may be erratic). Test the RAM thoroughly. RAM board faults are a very common cause of file corruption.

- A drive fault (with also may be erratic). Test the drive as thoroughly as you can.

- Accidentally having two instances of Hauptwerk running at the same time, resulting in them both trying to write to the same file simultaneously. Hauptwerk tries to prevent the user from launching two instances, but if he/she launches them both within a very small amount of time (e.g. by double-clicking on the Hauptwerk desktop icon several times rapidly in succession) Hauptwerk might not be able to prevent it. Be careful only to launch one instance. Examining the user's log/diagnostic file after the problem has occurred should also allow you to see whether that was the problem (e.g. two "INF:4165 Welcome to Hauptwerk" lines without "INF:0403 Hauptwerk has finished shutting down" preceding them).

- A virus scanner (or similar) trying to scan the file as it's being written, and preventing it from being saved properly, or which subsequently scans it and incorrectly thinks it has a virus and 'cleans' (corrupts) it.

However, according to what I asked two customers who experienced this error, they said there was no problem at all when they turned on or off Hauptwerk .
...
When other customers have experienced this issue in the past, I found that it was because they turned off their PC before the computer shut down normally, but in this case, there is no way to guess.

Get them to send you diagnostic files and extract/check them as above. Sometimes it may not be obvious to the user that the computer didn't shut down cleanly, e.g. because of an OS/driver crash during shut-down, or a power-cut.

How can I reliably preserve combination stepper memory of Hauptwerk program?

Make regular backups and keep them somewhere safe.

Instead of doing 'shut down PC' every time you quit Hauptwerk, should you first do 'unload organ' and then send the 'shut down PC' command?

It should be safe just to use "File | Shut computer down" within Hauptwerk, or simply to exit Hauptwerk, wait until it has exited, then shut the computer down (no need separately to unload an organ first -- Hauptwerk will always do that automatically). The one exception was Hauptwerk v5.0.0, which had the following bug, which was fixed in v5.0.1:

Bug-fix: a crash occurred on a few computers when exiting Hauptwerk after successfully performing any of the following: restoring a backup, reverting all settings to factory defaults, cancelling launching Hauptwerk if any audio/MIDI devices were missing, or via 'Exit', 'Shut computer down' or 'Re-start computer' from the File menu.

Hence do make sure that your customers aren't still running v5.0.0. Their log/diagnostic file would show the Hauptwerk version in the latest "INF:4165 Welcome to Hauptwerk" line.

If I purchase a support ticket and make an inquiry, will you be able to fix this properly?

All we would potentially be able to do would be to look in your customer's log (diagnostic file) if sent, to see whether it gave any clues as to the cause of the problem (especially not shutting down cleanly, or having two instances of Hauptwerk running). However, you could do that yourself as above.

Hello, thank you for the reply.

First of all, provided that your customers do regular backups (either by using "File | Backup ..." within Hauptwerk manually, or by leaving Hauptwerk's automatic weekly backups turned on) then they can always get their settings/combinations back to the point in time of their last backup by restoring that backup ("File | Restore ..." within Hauptwerk). See the "Backing up and restoring your settings and data" section in the main Hauptwerk user guide for more details (pages 31-34 in the current v8.0 version).

Unfortunately, most of my clients don't know how to operate even basic computer operations. I also know how to restore a backup file. The problem is that every time this happens, I have to go directly to the customer and restore the backup file.

- Computer not being shut down cleanly. You can usually see whether that was the culprit by looking in the user's log file (get them to send you a diagnostic file and extract it with"Help | View/extract contents of a backup or diagnostic file") after the corruption problem has occurred: if Hauptwerk exited cleanly then an "INF:0403 Hauptwerk has finished shutting down" line should precede each "INF:4165 Welcome to Hauptwerk" line.

Following your advice, I checked the customer's activity log file.



1) INF 0403 -> 4165 -> 1108

2023-09-02-09-20-59: INF:0403 Hauptwerk has finished shutting down.

2023-09-02-09-40-50: INF:4165 Welcome to Hauptwerk.

........

2023-09-02-09-41-49: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-09-02-09-41-49: INF:2202 Combinations saved to file 'Combs01.OrganCombinationSet_Hauptwerk_xml'.

2023-09-02-09-41-49: INF:2157 The organ Goerlitz Sonnenorgel Surround, full edition.Organ_Hauptwerk_xml has been loaded. Metrics:


------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

2) INF 0403 -> 4165 -> 1108

2023-09-03-07-59-57: INF:4104 An automatic backup will be made. (Total number of existing backups found: 11. Most recent existing backup: 2023-08-26-17-29-18. Automatic backup frequency preference: 'Weekly (recommended)'.)

2023-09-03-07-59-57: INF:1009 Starting to create backup 'C:/Users/USER/Hauptwerk/AutomaticBackups/Hauptwerk Backup (2023-09-03-07-59-57).Backup_Hauptwerk_gz'. [Mem. usage stats. MB: Approx. est. of tot. usable phys. mem. remaining: 29667, Approx. est. Hauptwerk sample/obj. mem. (excl. other data): 256 (0 pageable). Approx. pct. phys. mem. used: 0, OS tot. 'available' phys.: 29667, OS commit tot.: 0, OS tot. page file: 4864, OS tot. virtual: 37445, OS mem. load pct: 8, OS sys. cache: 2, OS process commit: 425, OS process page faults: 11, OS process work. set: 436, OS process min. work. set: 4241, OS process max. work. set: 30533.]

2023-09-03-08-00-38: INF:1012 Backup 'C:/Users/USER/Hauptwerk/AutomaticBackups/Hauptwerk Backup (2023-09-03-07-59-57).Backup_Hauptwerk_gz' created (size: 28.59 MB).

2023-09-03-08-00-38: INF:0403 Hauptwerk has finished shutting down.

2023-09-03-08-41-53: INF:4165 Welcome to Hauptwerk.
......
2023-09-03-10-19-53: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file OrganID000891Config.OrganConfig_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-09-03-10-19-53: INF:2125 The organ settings file could not be loaded and may have been corrupt or have contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some previous settings changes may have been lost as a result.

2023-09-03-10-20-15: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-09-03-10-20-15: INF:2202 Combinations saved to file 'Combs01.OrganCombinationSet_Hauptwerk_xml'.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

3) INF 0403 -> 4165 -> 1108

2023-11-07-15-51-38: INF:0403 Hauptwerk has finished shutting down.

2023-11-07-15-52-50: INF:4165 Welcome to Hauptwerk.
.......
2023-11-07-16-02-20: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file OrganID000933Config.OrganConfig_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-11-07-16-02-20: INF:2125 The organ settings file could not be loaded and may have been corrupt or have contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some previous settings changes may have been lost as a result.

2023-11-07-16-02-43: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-11-07-16-02-43: INF:2202 Combinations saved to file 'Combs01.OrganCombinationSet_Hauptwerk_xml'.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

4) INF 0403 -> 4165 -> 1108

2023-11-17-17-48-54: INF:0403 Hauptwerk has finished shutting down.

2023-11-17-18-25-05: INF:4165 Welcome to Hauptwerk.
.......
2023-11-17-18-25-14: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file OrganID000933Config.OrganConfig_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-11-17-18-25-14: INF:2125 The organ settings file could not be loaded and may have been corrupt or have contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some previous settings changes may have been lost as a result.

2023-11-17-18-25-37: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

2023-11-17-18-25-37: INF:2202 Combinations saved to file 'Combs01.OrganCombinationSet_Hauptwerk_xml'.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

5) INF 0402(!) -> 1108 -> 2302 -> 4165

2024-03-20-10-25-23: INF:0402 Hauptwerk is shutting down.

2024-03-20-10-25-23: INF:2507 Stopping audio and MIDI. [Mem. usage stats. MB: Approx. est. of tot. usable phys. mem. remaining: 20440, Approx. est. Hauptwerk sample/obj. mem. (excl. other data): 8022 (0 pageable). Approx. pct. phys. mem. used: 28, OS tot. 'available' phys.: 20440, OS commit tot.: 3, OS tot. page file: 4864, OS tot. virtual: 37445, OS mem. load pct: 37, OS sys. cache: 2, OS process commit: 9640, OS process page faults: 13, OS process work. set: 9630, OS process min. work. set: 13460, OS process max. work. set: 30533.]

2024-03-20-10-25-23: INF:5097 Stopping audio. Priorities: plug-in link: --, Win DS: --.

2024-03-20-10-25-23: INF:5122 Stopping audio output device 'ASIO: ASIO Fireface USB'. (Pri: 15[32:18], smallest buffer fill: 256 frames, largest: 256 frames.)

2024-03-20-10-25-24: INF:5099 Audio stopped.

2024-03-20-10-25-24: INF:3828 Stopping MIDI.

2024-03-20-10-25-24: INF:3825 Stopping MIDI IN port 'UCX Midi Port 1'. (Driver pri: 9[32:0]. Engine pri: 11[32:2]. Buff: floods: 0, peak usage: 0 pct, total traffic: 43.8 KB. Event perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: event latency: '0.0 / 1.4 / 3.0 / 14947 / 7943 / 7004 / 0 / 0 / 0 / 0', processing time: '0.0 / 0.1 / 1.5 / 14947 / 14947 / 0 / 0 / 0 / 0 / 0', processing overrun: '0.0 / 0.0 / 0.7 / 14946 / 14946 / 0 / 0 / 0 / 0 / 0')

2024-03-20-10-25-24: INF:3825 Stopping MIDI IN port 'UCX Midi Port 2'. (Driver pri: 9[32:0]. Engine pri: 11[32:2]. Buff: floods: 0, peak usage: 0 pct, total traffic: 0.0 KB. Event perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: event latency: '1.0 / 1.6 / 2.0 / 8 / 3 / 5 / 0 / 0 / 0 / 0', processing time: '0.0 / 0.2 / 0.4 / 8 / 8 / 0 / 0 / 0 / 0 / 0', processing overrun: '0.0 / 0.0 / 0.0 / 7 / 7 / 0 / 0 / 0 / 0 / 0')

2024-03-20-10-25-24: INF:3829 Stopping MIDI OUT port 'UCX Midi Port 1'. (Sending pri: 11[32:2]. Rate limited: Y. Max time waited to send event if rate limited: 14 ms. Buff: floods: 0, peak usage: 0 pct, total traffic: 64.0 KB.)

2024-03-20-10-25-24: INF:3829 Stopping MIDI OUT port 'UCX Midi Port 2'. (Sending pri: 11[32:2]. Rate limited: Y. Max time waited to send event if rate limited: 2 ms. Buff: floods: 0, peak usage: 0 pct, total traffic: 0.1 KB.)

2024-03-20-10-25-24: INF:3826 MIDI stopped.

2024-03-20-10-25-24: INF:2509 Stopped audio and MIDI. Peak levels since last started: audio: -200.0 dB (>=0 dB indicates clipping), polyphony as pct of limit: 0.0, estimated audio CPU load during first 10 seconds: 0.0 pct, thereafter: 2.2 pct. Ran at real-time priority (Windows only)?: N. Extra time allowed when audio started (Windows only): 0.0 s. Sample rate: 48000 Hz. Mixer preset: 1. Num active stereo reverbs: 4, Max active reverb length: 4.97 s. Expected buffer latency: 512 frames, actual max buffer latency: 512 frames (10.7 ms), max single buffer latency allowed for: 384 frames (8.0 ms).
[Priorities: audio engines: 15[32:15], audio recorders: 15[32:15], mixer convolver FIR preparation/buffer allocator: 9[32:0], convolver engines: --, MIDI player: --, MIDI recorder: 11[32:2], GUI rendering: 9[32:0], default user events: 10[32:1].]
[Event buffer stats: (size in K-events, num floods, peak frac full pct, total traffic in K-events): GUI rendering: (211.5, 0, 0.00, 478., high-pri events: (8.0, 0, 0.00, 0.0), default user events: (8.0, 0, 0.00, 4.7).] [Background models:
relay models: (priority: 11[32:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.1 / 0.2 / 3.5 / 1296602 / 1296579 / 23 / 0 / 0 / 0 / 0, waiting stats: 0.0 / 1.8 / 3.2 / 1296602 / 1275816 / 20786 / 0 / 0 / 0 / 0, interval stats: 1.0 / 2.0 / 3.6 / 1296602 / 1227887 / 68715 / 0 / 0 / 0 / 0),
trem model: (priority: 11[32:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.0 / 1.2 / 1296584 / 1296584 / 0 / 0 / 0 / 0 / 0, waiting stats: 0.7 / 2.0 / 3.6 / 1296584 / 1244185 / 52399 / 0 / 0 / 0 / 0, interval stats: 1.0 / 2.0 / 3.6 / 1296584 / 1224045 / 72539 / 0 / 0 / 0 / 0),
wind supply model: (priority: 11[32:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.0 / 0.9 / 1296242 / 1296242 / 0 / 0 / 0 / 0 / 0, waiting stats: 0.1 / 2.0 / 3.7 / 1296242 / 1294016 / 2226 / 0 / 0 / 0 / 0, interval stats: 0.1 / 2.0 / 3.7 / 1296242 / 1186564 / 109678 / 0 / 0 / 0 / 0),
pipework: (priority: 11[32:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.0 / 1.1 / 1296604 / 1296604 / 0 / 0 / 0 / 0 / 0, waiting stats: 0.1 / 2.0 / 4.9 / 1296604 / 1169819 / 126785 / 0 / 0 / 0 / 0, interval stats: 0.2 / 2.0 / 4.9 / 1296604 / 1022955 / 273649 / 0 / 0 / 0 / 0),
master: (model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.1 / 0.2 / 3.6 / 1296604 / 1296565 / 39 / 0 / 0 / 0 / 0, waiting stats: 0.0 / 1.8 / 3.2 / 1296604 / 1296570 / 34 / 0 / 0 / 0 / 0, interval stats: 1.8 / 2.0 / 3.6 / 1296604 / 1282282 / 14322 / 0 / 0 / 0 / 0).]
Voice generator background model event stats: total num event blocks: 32166454, num event queue underflowed blocks: 19124 (0.06 pct), mean block length for non-underflowed blocks: 4.0 ms.
Voice generator note-on events stats: total num processed: 127485, mean time waited before events: 90 frames (1.9 ms).

2024-03-20-16-07-52: ERR:1108 XML parsing error at line 44339, column 23 ['error occurred while parsing element', '', ''] when processing the XML file Config.Config_Hauptwerk_xml. Please request assistance from the supplier of the file.

2024-03-20-16-07-52: ERR:2302 The main configuration file 'Config.Config_Hauptwerk_xml' couldn't be loaded.

2024-03-20-16-07-53: INF:4116 The main Hauptwerk configuration file Config.Config_Hauptwerk_xml, located in the configuration file folder (C:/Users/USER/Hauptwerk/HauptwerkUserData/Config0-GeneralSettings), could not be loaded and may have been corrupt or contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some or all previous settings changes may have been lost as a result.

2024-03-20-16-08-01: INF:4165 Welcome to Hauptwerk.

Hauptwerk version: 7.0.0.136.
License: Advanced Edition.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

6) INF 0402(!) -> 1108 -> 2302 -> 4165

2024-04-29-18-23-00: INF:0402 Hauptwerk is shutting down.

2024-04-30-09-28-32: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Config.Config_Hauptwerk_xml. Please request assistance from the supplier of the file.

2024-04-30-09-28-32: ERR:2302 The main configuration file 'Config.Config_Hauptwerk_xml' couldn't be loaded.

2024-04-30-09-28-33: INF:4116 The main Hauptwerk configuration file Config.Config_Hauptwerk_xml, located in the configuration file folder (C:/Users/USER/Hauptwerk/HauptwerkUserData/Config0-GeneralSettings), could not be loaded and may have been corrupt or contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some or all previous settings changes may have been lost as a result.

2024-04-30-09-28-41: INF:4165 Welcome to Hauptwerk.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

6) INF 0402(!) -> 4165 -> 1108 -> 1108

2024-04-30-17-27-37: INF:0402 Hauptwerk is shutting down.

2024-05-01-09-40-56: INF:4165 Welcome to Hauptwerk.
....

2024-05-01-09-41-02: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file OrganID000933Config.OrganConfig_Hauptwerk_xml. Please request assistance from the supplier of the file.

2024-05-01-09-41-02: INF:2125 The organ settings file could not be loaded and may have been corrupt or have contained invalid settings or values. Hauptwerk restored and loaded the file automatically from backup. However, some previous settings changes may have been lost as a result.

2024-05-01-09-41-25: INF:2507 Stopping audio and MIDI. [Mem. usage stats. MB: Approx. est. of tot. usable phys. mem. remaining: 20849, Approx. est. Hauptwerk sample/obj. mem. (excl. other data): 7824 (0 pageable). Approx. pct. phys. mem. used: 27, OS tot. 'available' phys.: 20849, OS commit tot.: 2, OS tot. page file: 4864, OS tot. virtual: 37445, OS mem. load pct: 36, OS sys. cache: 2, OS process commit: 9201, OS process page faults: 5, OS process work. set: 9192, OS process min. work. set: 13017, OS process max. work. set: 30533.]
....

2024-05-01-09-41-25: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

2024-05-01-09-41-25: INF:2202 Combinations saved to file 'Combs01.OrganCombinationSet_Hauptwerk_xml'.

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

Looking at the log above, when error 1108 appears, I could check INF 0403 or 0402.

When I built my hauptwerk console, I configured the hardware so that whenever the 'Power Off' button was pressed, the 'Shutting down PC' command was sent to Hauptwerk through a MIDI signal. And when Hauptwerk shuts down the PC, the AC power to my Hauptwerk console is automatically cut off. The AC power is never cut off until the Hauptwerk program is terminated. But why does the Inf code sometimes end in 0402 instead of 0403? This is the first question.

- A RAM board fault (which may be erratic). Test the RAM thoroughly. RAM board faults are a very common cause of file corruption.

- A drive fault (with also may be erratic). Test the drive as thoroughly as you can.

As far as I know, Samsung SSD and DDR memory are quite stable compared to other companies' products, so this part seems unclear to me.

- Accidentally having two instances of Hauptwerk running at the same time, resulting in them both trying to write to the same file simultaneously. Hauptwerk tries to prevent the user from launching two instances, but if he/she launches them both within a very small amount of time (e.g. by double-clicking on the Hauptwerk desktop icon several times rapidly in succession) Hauptwerk might not be able to prevent it. Be careful only to launch one instance. Examining the user's log/diagnostic file after the problem has occurred should also allow you to see whether that was the problem (e.g. two "INF:4165 Welcome to Hauptwerk" lines without "INF:0403 Hauptwerk has finished shutting down" preceding them).

I registered Hauptwerk in the 'startup' folder of Windows, so Hauptwerk runs automatically after Windows is fully booted. In other words, the Hauptwerk app is only clicked once.

- A virus scanner (or similar) trying to scan the file as it's being written, and preventing it from being saved properly, or which subsequently scans it and incorrectly thinks it has a virus and 'cleans' (corrupts) it.

No anti-virus program runs on this computer. Internet connection is blocked and it is not recommended to connect external USB memory etc. Only keyboard and mouse are allowed.

Could the 'shut down pc' command be a clue to this problem? I really doubt it. It is currently not suitable for my Organ console to allow the user to directly turn off Windows by executing 'exit Hauptwerk'.


....................................................

General Error
SQL ERROR [ mysql4 ]

User 'dwywhmjb_hwforumuser' has exceeded the 'max_user_connections' resource (current value: 25) [1226]

An sql error occurred while fetching this page. Please contact an administrator if this problem persists.

----> This is really uncomfortable. It feels like my activities in the forum are quite restricted.

[mdyde]

Hello John,

1) INF 0403 -> 4165 -> 1108

2023-09-02-09-20-59: INF:0403 Hauptwerk has finished shutting down.

2023-09-02-09-40-50: INF:4165 Welcome to Hauptwerk.

........

2023-09-02-09-41-49: ERR:1108 XML parsing error at line 1, column 1 ['error occurred while parsing element', '', ''] when processing the XML file Combs01.OrganCombinationSet_Hauptwerk_xml. Please request assistance from the supplier of the file.

In the four examples you quoted above in which 0403 does correctly precede 4165, the file corruption error (1108) occurred in an organ-specific file (a combination file for that organ, or the organ-configuration file for that organ), rather than in Hauptwerk's general configuration file. Hence if the user didn't happen to have that particular organ loaded when they last exited Hauptwerk the fact that 0403 preceded 4165 the very last time isn't sufficient in itself to rule out a shut-down problem in that case -- the non-clean shut-down could have occurred previously (when that particular organ was last used), so you would need to look further back through the log to when that particular organ was last loaded, and then look forwards from that to the next launch (4165) to check whether that particular exit was clean.

5) INF 0402(!) -> 1108 -> 2302 -> 4165 :cry:

In those cases where an 0402 (starting to exit) occurs without a subsequent 0403 (finished exiting) before the next 4165:

Your log excerpts don't seem to show any evidence of two instances running at once.

When I built my hauptwerk console, I configured the hardware so that whenever the 'Power Off' button was pressed, the 'Shutting down PC' command was sent to Hauptwerk through a MIDI signal. And when Hauptwerk shuts down the PC, the AC power to my Hauptwerk console is automatically cut off. The AC power is never cut off until the Hauptwerk program is terminated.
...
Could the 'shut down pc' command be a clue to this problem? I really doubt it. It is currently not suitable for my Organ console to allow the user to directly turn off Windows by executing 'exit Hauptwerk'.

When Hauptwerk's "File | Shut computer down" function is triggered (whether via MIDI or directly by the user) the 0402 line will be logged. Hauptwerk (v5.01+) will then only ever actually call the operating system command to initiate shutting down the computer as the very last line of code that Hauptwerk itself executes before exiting. I.e. actually telling Windows to shut the PC down will only occur once Hauptwerk has finished everything else (including having finished exiting all threads, having finished writing all of files, and having written the 0403 message to the log).

So the fact that 0402 appears in the logs but not the 0403 either means that somehow:
1. The PC lost power, or:
2. The PC crashed, or:
3. The Hauptwerk process crashed (which should only happen in the case of a driver crash, or RAM board fault)
... *before* Hauptwerk had finished exiting (0403) and before Hauptwerk had actually asked Windows to shut down,

... or:
4. The PC or SSD crashed or lost power *after* Hauptwerk had finished exiting (0403) and after Hauptwerk had then asked Windows to shut down, but that the final logged lines (including the 0403 message) and the final file writes that the Hauptwerk process had made (organ-config/combination files, etc.) didn't actually get flushed to the drive by Windows or by the SSD.

When I built my hauptwerk console, I configured the hardware so that whenever the 'Power Off' button was pressed, the 'Shutting down PC' command was sent to Hauptwerk through a MIDI signal. And when Hauptwerk shuts down the PC, the AC power to my Hauptwerk console is automatically cut off. The AC power is never cut off until the Hauptwerk program is terminated.

N.B. your mechanism *must* wait until Windows itself has completely shut the PC down before any power is cut. It isn't sufficient to wait until the Hauptwerk process has exited because:

a) Modern operating systems and SSDs don't actually write changed files to the drive immediately -- they use file caches which aren't actually flushed to disk until later. Only waiting until the PC has fully finished shutting down guarantees that the operating file caches (and the SSD drive's own file caches) are actually fully written to the drive.

b) Cutting power to the PC before Windows has fully finished shutting down risks corrupting other parts of Windows.

You must wait until the PC itself has fully finished shutting down before cutting power to anything, otherwise you *will* get file corruption sooner or later.