Monday, February 13, 2012

Can not activate Sharepoint Server Publishing

I recently upgraded from SP2007 to SP2010 thru DB attached.  I noticed one of my site collection's Sharepoint Server Publishing Infrastructure and Sharepoint Server Publishing were not activated. I went ahead and activate the infrastructure on the site collection but when I try to activate the publishing on the site level it failed. I try to activate using command line:

stsadm -o activatefeature -name PublishingWeb -url http://mydomain.com/test
but got the following....

Provisioning did not succeed. Details: Failed to initialize some site properties for Web at Url: 'http://mydomain.com/test' OriginalException: List does not exist.
The page you selected contains a list that does not exist. It may have been deleted by another user.

After some further research, it looks like the hidden "Quick Deploy Item" and a host of other key list were not there.  Now sure how this happened but I have tried various suggestions to no avail. 

SOLUTION:  Okay... I open a support ticket with MS Support. We ended up solving the issue by issuing by following comannds:

stsadm -o activatefeature -filename publishing\feature.xml -url http://...-force
stsadm -o activatefeature -filename publishingresources\feature.xml -url http://...- -force
stsadm -o activatefeature -filename publishingSite\feature.xml -url http://...- -force
stsadm -o activatefeature -filename publishingweb\feature.xml -url http://...- -force
stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://...- -force
stsadm -o activatefeature -filename navigation\feature.xml -url http://...- -force

NOTE: You need to execute the aboe on all subsites that are affected. Hope this help someone.

Wednesday, February 8, 2012

Search not returning result for other domain users


I have a strange situation when users from other domain does not get any results when they perform a search. Here's the scenerio:
  1. I recently upgraded the farm from Sp2007 to Sp2010.
  2. Crawl jobs all completed successfully
  3. Our domains:
    - myco.com
    - eu.myco.com
  4. User from myco.com can search fine.
  5. Search performed by user from eu.myco.com return nothing... envon on simple search where I am sure they have access to. Also, they didn't have this problem in SP2007.
  6. These eu.myco.com users does have access to the sharepoint sites.
  7. It is similar to the issues describe in this discussion: http://social.microsoft.com/Forums/en-US/partnerofficesharepoint/thread/b547461a-e47b-4b54-980d-d6b36e244bae.  The fix was to add the search/servcie account to the Windows Authorization Access group.
  8. In my case, I need to add the service account to the Windows Authorization Access group on ALL the domains.

Missing Some Basic Webparts After SP2010 Upgrade

I have recently upgraded from SP2007 to SP2010 (enterprise). Now, when I try to add a webpart, I don't see the Content Editor webpart under the media category. I am a farm admin and I can see it. This is what I have done so far:
  • Checked the permission to webpart gallary. They all looked fine
  • Checked the site collection's publsihing infrastructure feature and site level publishing feature. They are both enabled already. I went and disable and re-eanble any way.
  • Went to Central Admin -> Upgrade and Migration and ran the "Enable features on Existing Sites".
  • Checked the webpart gallery but didn't see the MSContentEditor.dwp on the list. Click new but still see it from the list.
What what else am I missing.    I seem to be missing some basic webparts... webparts like RSS Feed is not showing up when I add webpart. 

Okay... after some more digging into his. I was able to resovle by running the following script to disable and re-enable the: 1) Basic Web Part; 2) Standard Site Collection Feature; and 3) Enteprise Site Colleciton Feature. The script traverse thru the web, locate the site collections, and disable/enable the features:

$webApp = Get-SPWebApplication -Identity http://yourwebapp
$webApp | Get-SPSite -limit all | ForEach-Object {Disable-SPFeature -Identity "BaseSite" -Url $_.Url -Confirm:$False}
$webApp | Get-SPSite -limit all | ForEach-Object {Enable-SPFeature -Identity "BaseSite" -Url $_.Url}
$webApp | Get-SPSite -limit all | ForEach-Object {Disable-SPFeature -Identity "PremiumSite" -Url $_.Url -Confirm:$False}
$webApp | Get-SPSite -limit all | ForEach-Object {Enable-SPFeature -Identity "PremiumSite" -Url $_.Url}

Note that manually deactivate and activate these features thru the Site Collection Feature page does not help. For some reason, it needs to be done thru the command line.