$ 0 0 We've got the same errors non periodically on VSA 5.1.1. (several times a month) Is there now a solution for this?