1
Vote

Deployed and activated for site collection web app and doesn't work

description

I deployed this in Development and it worked great for me. In dev we have one server acting as the webapp and front end server. However In our production environment I can see that solution activated however I can't seem to get the iframing to work. In production I have 2 web app servers and 2 front end servers. I have activated it in the central admin web application features. Is there something I am missing? I recompiled the exact wsp from source code untouched.

comments

basenode wrote Apr 6, 2016 at 6:27 PM

This is for SharePoint 2013

basenode wrote Apr 6, 2016 at 6:28 PM

on Prem

vandest wrote Apr 7, 2016 at 4:33 AM

Hi,

The WebApp feature will register a web.config modification (httpModule) that is processed by the timer job on all servers. You can follow up if the jobs have run on the Job Status page in Central Admin, or you can see if the module was added to the web.config which it should have (but due to the nature of the timer it may take several minutes).

Cheers,

basenode wrote Apr 7, 2016 at 1:28 PM

It looks like the ventigrate reference has been added to the modules section of the web application's web.config when I activated it. Is there anything else that has to happen to ensure the feature is propagated throughout the farm?

vandest wrote Apr 8, 2016 at 7:03 AM

Hi, then it probably is active. Do you have any reason to think it is not active?

basenode wrote Apr 8, 2016 at 10:56 AM

When I try to iframe Sharepoint pages like the home page or excel services I get:

"Refused to display '<sitename>' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'."

This does not happen in the dev instance

vandest wrote Apr 10, 2016 at 9:06 AM

Hi basenode,

After the solution is deployed (globally) you have to activate the Web App Feature on the webapp where you want it. Perhaps you have activated it on the wrong web app ?