We are currently evaluating this issue for a fix in a future service pack.
Workaround:1. Create a backup of the CRM web.config
2. Delete the following handler from line 499 of the web.config file (Note there are two instances of this handler in the file. Do not delete the second occurrence)
3. Save web.config