04 July, 2009

Summary Links Web Part (Error 0x80070002)

Today, We faced one wierd error message regarding Summary Links Webpart.
Due to some requirement, one of the user in my project demanded me the replication of one of the site collections. So, Itried to take the export and imported it one to a new one with blank site template. Export and import both were successfull and replication has been done properly but the problem starts now, when we open the site and we found out one error message related to Summary Link Webpart.

Unable to add selected web part(s). Could not load XSL file. The system cannot find the file specified.(Exception from HRESULT: 0x80070002).
Solution:
This error is usually raised when you try to add a publishing-related web part (such as Summary Links) into a non-publishing site. You have to either add it into a site built with a publishing template (Collaboration Portal or Publishing Portal), or to activate the publishing features manually:

-Activate Office SharePoint Server Publishing Infrastructure feature in site collection features, in Site Collection Administration section of Site Settings page
-Activate Office SharePoint Server Publishing feature in destination site features, located on Site Administration section of Site Settings page

18 comments:

  1. Hi,
    I was searching the Internet and found your awesome blog. I have studies
    many sharepoint books on the market,If read your this site this is very informative, and your site gives planty of knowledge about sharepoint.

    Thank You
    SharePoint Development

    ReplyDelete
  2. Hi Amol,

    I'm facing the problem even after activating both the features. So, I thought of deactivated the feature and activating again. But I faced a new issue. When I deactivate, it redirects to an error page (list not found. might be deleted by another user). and when I open the features page, this specific feature is deactivated.

    Pls. let me know if there is an work around for this issue.

    Jai
    sharepoint108@hotmail.com

    ReplyDelete
  3. Hello Jai,

    Please try to activate the publishing feature by means of stsadm command and check the results:

    here are the commands:

    stsadm -o activatefeature -filename publishing\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingresources\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingSite\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingweb\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename navigation\feature.xml -url http://URL -force

    (Obviously, replace the URL above with the URL of the site collection)

    Please let me know the further result,Thanks for your patience..

    ReplyDelete
  4. hi Amol,

    I activated the features, but still had the same problem. So, I had gone through MSDN to check what xsl files are requried for summary links webpart and uploaded them into style library. after this, I was able to import and add the summary links webpart (http://msdn.microsoft.com/en-us/library/ms551040.aspx). I was able to add the webpart, but it dispalys a bullet infornt of the link. I had set the configure and style for the webpart but no luck in removing the bullet. Please let me know if any specific file has to be uploaded (though activating featues is successful from stsadm, but I feel that the feature is not activated propely there by some of the required files are missing)

    Thanks
    Jai

    ReplyDelete
  5. Hey Amol,

    When I deactivate the feature, I'm getting the error as:
    List does not exist.

    The page you selected contains a list that does not exist. It may have been deleted by another user.

    From the URL, the feature id is PublishingWeb feature incase of Site Feature and PublishingSite in case of Site collection feature. (http://www.thorprojects.com/blog/archive/2007/05/16/list-of-features-with-guids.aspx)

    ReplyDelete
  6. Please execute the following two steps and i am pretty much sure that your issue will be resolved

    1.Go to Site Settings -> Master page Gallery -> Add Authenticated Users group and give Read Restricted Access rights.

    Add the same group in Style Library and give the same permissions.

    2. Please run these commands

    stsadm -o activatefeature -filename publishing\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingresources\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingSite\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishingweb\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://URL -force

    stsadm -o activatefeature -filename navigation\feature.xml -url http://URL -force

    (Replace the URL above with the URL of the site collection)

    Please check and let me know in case of any issues,Thanks for your patience...

    ReplyDelete
  7. one more thing that we can check here-make sure master page gallery and style library are inheriting permissions from the parent...

    I am trying to reproduce the issue and testing every possible cause to resolved your problem...

    ReplyDelete
  8. Hey Amol

    Thanks for your support. I had checked the user permissions. The "NT AUTHORITY\authenticated users" has the read permission and both the masterpage and style library inherit from parent, i.e "This library inherits permissions from its parent. (My Page)" .

    Thank you for your time and support

    ReplyDelete
  9. Amol,

    The site to which I am trying to add is MySite, so do you think MySite template be the reason for it (so does MySite support the all the publishing feature ??).

    Jai

    ReplyDelete
  10. Hello Jai,

    Did you checked the other site collections ?

    Apart from this site which is having the problem of summary link webpart, create one site collection-->activate the publishing infrastructure feature at site collection level and add the summary link webpart...

    If that works then export that webpart to desktop and import to the site gallery where we have the problem...

    Please check and let me know the results.. Thanks for your patience...

    ReplyDelete
  11. Hi Amol,

    It works on other sites. I have the following site collections :
    http://mycompany.com/sites/s1
    http://mycompany.com/sites/s2
    http://mycompany.com/sites/search
    http://mycompanymypage.com/sites/mysite

    only on "mysites", it shows a dot (bullet) infront of the link....

    ReplyDelete
  12. Hello Jai,

    As i mentioned,Please follow th export-import process and import the working webpart to your mysite.

    Please follow these steps:

    EXPORT A WEB PART

    1. On the Site Actions menu , click Edit Page.
    2. Click the Web Part menu of the Web Part that you want to edit, and then click Export.
    3. In the File Download dialog box, click Save.
    4. Select a location to which you want to save the Web Part file.
    5. If you want the file to have a different name, type the name in the File name box.
    6. Click Save.

    Import a webpart

    1. On the Site Actions menu , click Edit Page.
    2. In the Web Part zone that you want to add the Web Part to, click Add a Web Part.
    3. Click Advanced Web Part gallery and options to display the tool pane.
    4. At the top of the tool pane, click the arrow, and then click Import.
    5. Click Browse.
    6. Locate the Web Part file that you want to import, and then click Open.
    7. Click Upload.
    8. Select the Web Part zone that you want to add the Web Part to, and then click Add.

    ReplyDelete
  13. still behaves the same ..... I guess this is due to the publishing features not installed / activated properly

    Jai

    ReplyDelete
  14. Hello Jai,

    Could you please check the publishing infrastructure feature at the mysite web application ?

    As you mentioned that other sites are responding fine and summary links webpart is also working without any issues.. so the problem is only with the mysite...

    if its a dev environment then can we create the mysite again and check the results ?

    Please check and let me know the results

    ReplyDelete
  15. when I try to deactivate, I get an error that feature is missing (as mentioned in my previous post, From the URL, the feature id is PublishingWeb feature incase of Site Feature and PublishingSite in case of Site collection feature. Ref: http://www.thorprojects.com/blog/archive/2007/05/16/list-of-features-with-guids.aspx)
    but when I go back to site, I see the feature is deactivated. When I activate the feature, it activates without any problem.

    ReplyDelete
  16. Hi Amol,

    This looks as an installation issue (I guess the site was not created properly as deactivating the publishing features throws an error). Thanks for your time and guidance for resolving the issue. As of now, we have decided to remove the summary links from the page and create a custom webpart instead of summary links.

    Can you please open a post on Admin for people search. I am having a issue where, I am able to see the profile picture on people search results and on mysite. But, the picture link is broken for images in people and groups. The image link points to default zone in case of people and group ... where as incase of people search result, the image link points to intranet zone.

    Thanks for your kind help :D

    ReplyDelete
  17. Hi Amol,
    I had a problem where I would get this error because some of the XML files were missing from my style library. We upgraded to enterprise from foundation it looks like there was an issue when the site features were enabled. We also encountered errors when trying to enable/disable the publishing feature. Running the stsadm commands above created the files that we needed to resolve the error. Thanks for your post!

    ReplyDelete

Your feedback is always appreciated. I will try to reply to your queries as soon as possible- Amol Ghuge

Note: Only a member of this blog may post a comment.