I do realize that there is still an issue, however for us, upgrading to the 4.0.0.4 version and changing the provider to use config files has resolved our problem. I do not know if it will resolve yours or which of the two changes fixed the problem, however it was noticed as a "happy by-product" of the changes we implemented. Just wanted to pass the information along.