Ok, the issue was identified and we prepared a fix. It should be out in the upcoming release so this error should not occur anymore! Thank you all for your information!
Janek