Corrupt Configuration File after update to v4.0.5.17
Corrupt Configuration File after update to v4.0.5.17
updated to the latest version. unfortunately something went wrong. I could solve it myself.
- Attachments
-
- Knipsel3.PNG (10.81 KiB) Viewed 4197 times
Re: Corrupt Configuration File after update to v4.0.5.17
Normally this can only happen, if there was either a disk or I/O write error happening or if the GPIO client was terminated abnormally (which wouldn't happen with a regular update) - so I am more guess, that it was related to an issue in the I/O sub-system of the OS or even a hardeware issue.
Do you happen to have the corrupt GPIOClient.config file available to look at where/how it got corrupted?
Do you happen to have the corrupt GPIOClient.config file available to look at where/how it got corrupted?
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Corrupt Configuration File after update to v4.0.5.17
Hello, updating was normal like other times. I don't have the corrupt GPIOClient.config file because I chose YES, delete the file. After a restart everything worked fine again. I only had to enable the GPIO-Client at startup.