We also have the exact same issue.

We opened a case. MS says this is a known issue:

https://support.microsoft.com/en-us/kb/3095156

The issue was first fixed in the following cumulative update of...