Forum Discussion
SharePoint 2010 : access denied on javascript
I tested SharePoint 2010 with success. Now i configured it to work with the Big-Ip F5 with the same F5 configuration i have for SharePoint 2007.
Then, when i try to show the contextual menu of a document in a document list, i have javascript error with "access denied", for instance on "core.js" and "inplview.js" files.
I noticed that this problem is only valid for SSL.
Any idea ?
Thanks,
- hooleylistCirrostratusHi Raphael,
- Joe_Nagle_10637NimbostratusWe are getting the exact same issue but on SharePoint 2010. As soon as we put the SharePoint servers behind the F5 using SSL we started getting the Access is denied core.js and inplview.js message when we use the drop down menu on items in the main page we get this error. Yes we have checked the deployment guides.
- Helen_Johnson_1Historic F5 AccountHi folks,
- hooleylistCirrostratusPer this post that Raphaël replied to, it looks like there is a hard coded reference to http: in the Javascript:
- Joe_Nagle_10637NimbostratusWe are only using the Local Traffic Manager. We are not using any accelerators.
- Raphaël_Guisol1NimbostratusHello,
- Joe_Nagle_10637Nimbostratus
I finally got this resolved after opening a support call with Microsoft. Our settings on the F5 were fine, and no iRule was needed. We ended up going in SharePoint 2010 and removing all AAM's (alternate access mappings) including the internet zone. Then we just created 2 internal mappings and that fixed our problem. I hope this helps further users as i'm sure other's will run into this.Please change your AAMs to this and testInternal URL Zone Public URL for Zonehttp://externalsite.domain.com Default https://externalsite.domain.comhttps://externalsite.domain.com Default https://externalsite.domain.com--Remove the internet zone - Raphaël_Guisol1NimbostratusHi Joe,
- mschofield_5900NimbostratusI experienced similar problems and despite having AAM setup correctly as per the above posts and the solutions guide, the problem was related to the use of non-standard ports for HTTP and HTTPS. I didn't get to the bottom of the problem but was able to switch to 80 and 443 anyway. A word of warning to those grappling with AAM's try reverting to the standard ports if possible.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com