This is not really an error but it is also most definitely not the behaviour you want. If you get the following error message:
This content cannot be displayed in a frame
To help protect the security of information you enter onto this website the publisher of this content does not allow it to be displayed in a frame….
Fortunately it is relatively easy to solve:
• Delete temporary internet files – Internet Options > General> Delete…
• Add *.live, *.sharepoint.com, *.dynamics.com in trusted sites – Internet Options > Security > Trusted Sites > Sites
• Reset to Custom settings to Medium – Low – Internet Options > Security > Trusted Sites > Custom Level – Reset to Medium – Low
• Enable mixed mode – Internet Options > Security > Trusted Sites > Custom Level
• Enable programs and files in an iframe – Internet Options > Security > Trusted Sites > Custom Level
• Make sure you close and restart Internet Explorer, refreshing is not enough
This posting is provided “AS IS” with no warranties, and confers no rights.
Mark Margolis's Blog 
Hi, we have experienced this issue, but have resolved it when the users logon to sharepoint BEFORE opening the documents menju from the navigation pane. However we still have an issue with some users, as they are shown SharePoint in an iFrame, instead of viewing the Component List (as expected). Any ideas?
Regards, Ariel
If you have followed all the steps in the article and you are you using the latest/correct list component (it was recently updated) then you have a different issue than the one I have been able to resolve. Sorry I can’t provide more help at this time, perhaps others have suggestions?
We are seeing a similar issue, it seems like as soon as you add metadata taxonomy lookup to the sharepoint default form, the CRM component no longer works and it renders the view in an iFrame…
Colin, we have the same issue. I’m sure it are the columns for metadata in the (standard) list view.
As soon as we remove the metadata columns from the list view CRM works fine. We added all columns (without our 2 metadata columns) to the list view and CRM still works fine. After adding only one of our 2 metadata columns to the list view the iFrame-error occurs again….
Both ListComponents for SharePoint 2013 and 2010 have Issues. The Issue occurs if the SiteCollection base language is different to Language you use in CRM (SP 2010) or you use in IE (SP 2013). This issue only occurs if documents exists.
mistake: the language for the SharePoint 2010 ListComponent is determined by the user settings in SharePoint and not by the CRM Language.
Colin, Carsten – Did either of you figure out a workaround to this issue with lookup columns in SharePoint. I have the exact same problem. Thanks. Sam