Sounds like the same issue that was reported here:
The workaround is to delete a certain certificate.