Forum Discussion
Scott_Carlson
Apr 26, 2011Employee
Greetings,
This issue was reported in a support incident by another customer and we have identified the issue.
Since they mentioned this post, I wanted to include the resolution here in devcentral so you will have a fix. If you experience something like this in the future, please don't hesitate to open a support incident with us.
The problem was introduced by Exchange 2010 rollup 2. It didn't occur prior to installation of that.
Here's how to correct it until it's fixed in a cumulative hotfix.
Navigate to Portal Access>Content Processing and you will be under the heading "Preprocessing scripts".
Under "Web Applications Content Processing Scripts, click on "add new favorite".
Then put in the following
Preprocessing Script name: OWA2010_FirefoxFix
URL: match patterns: */uglobal.js*
Content Type: (leave blank)
Allow caching: Check this box
Sed processing script: s@!(a\.tagName&&a\.tagName\.toLowerCase()=="body")&&\(b\.setStartBefore(a);var e=F5_Invoke_createContextualFragment\)@\1@
Processing: Post-process response data (after content patching)
Then click "Update".
This will restore the functionality of the send button.
Best Regards,
Scott