It appears you're encountering a known issue for which a bug is raised. A full description and workaround is included in KB 302110
If the error in your log file is a match for that in the KB try the workaround.
I'm getting this error as well but the link to the workaround is not longer available. Please help!