0

We have 3 content editor webparts on Wiki Page.

All the 3 webparts are added using SharePoint Designer. All the webparts have target audience.

We are facing an issues when we deploy the wsp: All 3 content editor webparts are getting visible (target audience isn't working).

What could be the potential problem for audience tageting not working ? But in our stage environment i tried IIS reset , redeploying webparts it worked . But in production i am still having issues .

  • Is it working before? – Waqas Sarwar MVP May 19 '15 at 19:16
  • Hi Waqas , IIS reset works sometimes in stage . But issues pops up after some days . – Nikhil J May 19 '15 at 19:19
  • the reason i am asking this, in 2010 farmw e had the same issue when target Audience stop working and we figured out that UPA pool stuck ...after recycleing the app pool for UPA service everything works. – Waqas Sarwar MVP May 19 '15 at 19:20
  • 1
    central admin> application management > manager services Application > click on UPA> on this page your will see manage audience – Waqas Sarwar MVP May 19 '15 at 19:26
0

If they are audiences and not AD groups or Sharepoint groups, then it is probably an underlying GUID mismatch and it can't be resolved. While named the same, they have unique GUIDs under the hood on the Devs machine and the QA/Prod environment. This is most likely where the problem is.

At a previous employer, they had news which was heavily reliant on audiences. It became problematic and they decided (before I got there) to go into the DB and manually update the audiences so things would work across all environments.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.