MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Audience option disappeared!

  Asked By: Tanya    Date: Oct 10    Category: MOSS    Views: 1207

I have quite a perplexing problem. We have a website we're developing
in SP 2007 beta, for which we were making use of the new expanded
audience feature. Now, all of a sudden, the audience settings are
missing. Previously they had been accessible through "Modify Shared
Web Part", then expand the "Advanced" node, and it was there at the
bottom. Now it's just.... gone.

So what's changed since audiences last worked? Well, we were
struggling to get SSL installed on this site and having a tough time
with it. It's finally working, but I'm not sure what our network
person had to do to get it to work. I just checked IIS, and it looks
very different from when the beta was first installed. When
installed, a number of SharePoint sites on different ports just
appeared, apparently by default. These sites have all been deleted.

Does anyone have any insight into what might be the problem here? We
were hoping to do a pilot test of this site, and the audience feature
was rather critical. Any help would be much appreciated!



6 Answers Found

Answer #1    Answered By: Percy Beach     Answered On: Oct 10

In 2003 there were two causes of this problem – one was a server setting that our IT folks accidentally switched off. The other & most common was that the web part must have the setting “allow close” checked. The audience  web part is really just closing & opening the web part on the user’s view of the page, based on their permissions. So you have to allow the close in order for the functionality to work. Now – this is all in 2003. I’m just getting started in 2007, so none of this may apply.

Answer #2    Answered By: Mary Adams     Answered On: Oct 10

MOSS07 does create some "extra" web sites which perform essential functions.
What sites showed up "by default" and were deleted?

Audiences are built on profiles and both are maintained by the Shared Services
Provider which has its own separate web site. I am just trying to get a picture
of what happened.

Answer #3    Answered By: Laura Walker     Answered On: Oct 10

That's what I was afraid of. I believe
there were three sites in IIS labeled "SharePoint", each with
different ports. One of our IT guys didn't know what they were and
assumed they had been created for testing, so he deleted them.

We've decided to wipe everything out and reinstall - it's a pain, but
having a fresh site is always nice! Do you think you could point me
to documentation or a website where I could read up about
these "extra" sites?

Answer #4    Answered By: Alyssa Butler     Answered On: Oct 10

How many you have will depend upon your implementation, but three that would be
created from a Basic installation would be:
Central Administration: The Admin site is now a SharePoint site and must have a
separate application and AppPool and content database.
Web Services has its own application, AppPool and Content Database but users do
not directly access it.
Shared Services has its own application, AppPool and Content Database.
You may also manually create a separate application and content Database for
your MySites Host (recommended).

Also, stay out of IIS management. SharePoint sites are managed from within CA or
SSP admin, not IIS. The IIS configuration is stored in the Config database when
configured from these locations. When changed in IIS Manager, it is not and your
sites are now broken. Do not change port numbers in IIS, Do not rename in IIS,
etc. You may add additional host headers in IIS and then configure SharePoint to
use them in Alternate Name Mappings. Do not remove the original host header from
within IIS.

Answer #5    Answered By: Katy Patton     Answered On: Oct 10

On the issue of application pools...
Is it still recommended practice to share an AppPool between sites
created by me?

Answer #6    Answered By: Ana Payne     Answered On: Oct 10

An app pool is to separate out codes, threads and security in iis

Each new app pool needs ~ 150 Mb of RAM so the fewer you use the less resources you need

However, the more you use you can separate out security plus, if one site is using one set of code that crashes that virtual server, it is in a separate app pool so doesn’t bring down the sites running on the other virtual servers.

So, as far as recommending sharing app pools – I guess the recommendation is that you do if you don’t have too many free server resources but if you have some less than reliable code running somewhere then you should segregate it to its own app pool until you know that its stable and then share an app pool

Didn't find what you were looking for? Find more on Audience option disappeared! Or get search suggestion and latest updates.