Tag Archives: SharePoint

_controltemplates/TaxonomyPicker.ascx failed in SP2010

Our SharePoint 2010 started crying late last Friday, of course right when I wanted to leave, and first thing this morning I took a look at the server and found the following errors:

Load control template file /_controltemplates/TaxonomyPicker.ascx failed…

Fortunately, I’m not the only one who seems to have had this problem pop out of the blue.  I found a solution fairly quickly here.  To summarize, here’s what you do:

On the server, navigate to C:program filescommon filesmicrosoft sharedweb server extensions14TEMPLATESCONTROLTEMPLATES and open TaxonomyPicker.ascx in notepad.  towards the top you will see the following line:

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker&#44;Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Change the &#44; to a comma (,), so now the element will look like this:

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Save the file.  No need to restart IIS or any web services, app pools, nothing.  Not sure why it did that, but it did, and this fixed it!

Hope this helps someone else!

UPDATE: If this doesn’t help, try renaming the file to TaxonomyPicker.ascx.broken.  Apparently the control isn’t even used and this will force the App Pool to ignore it when refreshing.

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Removing a user from a WSS 2.0 server (not just a site)

Yeah, I know, they’re still running WSS 2.0 at my employer. I’m just here to help, not judge. = )

So I get the request (and I got it before and forgot how I did it) from
a site admin that they can’t add a user to their new website they created. It
says they already exist when clearly they do not in the Manage Users screen.
This is generally because the SID of the existing user account doesn’t match the
SID of the new account you’re trying to add. The solution? Well documented in this Microsoft KB article.

The quick solution? If it’s a WSS site that is hosted on the portal
site, go here:

http://ServerName/Sites/SiteName/_layouts/1033/Siteusrs.aspx

Otherwise go here:

http://ServerName/_layouts/1033/Siteusrs.aspx

Obviously replacing “servername” with your server and “sitename” with the parent site
you’re trying to add the user to. Locate the user in the list, check the box and
at the top click the “Remove Selected Users” link. Once gone you can now safely
add this person to the parent and/or child sites without issue.

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Restore detached content DB list data to another SP 2010 instance

Had quite a scare today, when one of our business users asked why he couldn’t get to his SharePoint 2010 library.  It’s because we blew away that box due to configuration issues, and didn’t realize he was using it.  Oops!

Fortunately, our Sr. Network Admin (also the DBA) was smart enough to detach the DB (not drop it).  I looked at the content in SSMS and sure enough, that was where his data was.  Here’s what I did to restore his libraries:

  • Open Central Admin for the target SP 2010 instance.
  • Click on Backup and Restore
  • Under Granular Backup, choose Recover data from an unattached content database
  • Enter the name of the DB server and the unattached content DB name.  Leave WIA selected and leave Browse content selected.  Click Next.
  • Leave the site collection the way it is, click Site and select the path you want to restore from (it’s reading from the unattached content DB at this point).  Then do the same for the List (select which List or Library you’re restoring).
  • Select Export site or list and click Next.
  • Enter the path to your target SP2010 instance where you want the export to be saved to (ex: C:backupexport.cmp).  Check Export full security if you want to preserve author names, original creation dates, permissions, etc.
  • Click Start Export
  • When it’s finished (assuming there are no errors), open the SP2010 Management Shell and type the following:

[powershell]import-SPWeb http://site/path/path_to_.cmp_file[/powershell]

That’s it. When it’s done your list/library will be restored!  Careful, though, it will overwrite whatever’s in the target location, so be sure to back up or copy anything that’s already there before importing, so you can restore those items afterwards.

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Save Site as Template not available in SharePoint 2010

For some reason or another I’ve been able to creat a new site then save it as a template in both SP2010 and SP Designer 2010…except all of a sudden.  Not sure why, but when I exported an existing site from another farm (identical SP2010 installation), then imported it into another SP2010 farm the option is gone.  This also happened when I tried uninstalling the template from the Solution Gallery then redeploying it into the same farm.  Fortunately, I happened to find a solution that worked for me here.

Basically, navigate to the website in question (the one you want to save as a template) and append the following url (in bold):

http://server/site/_layouts/savetmpl.aspx

Here’s the caveat-DO NOT do this for Publishing sites!  It’ll work with a Publishing site, but when you try to create a new site out of it, it’ll break.  This is because the site template expects a normal URL structure, but the Publishing site puts pages inside of a pages library.

To deactivate, modify or delete other site templates, go to http://server/_catalogs/solutions/Forms/AllItems.aspx

Hope this helps!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Bad webpart causing SharePoint site to break

I ran across a discussion online today (can’t recall where it was, unfortunately) that mentioned what to do when you put a SharePoint web part (2007 or higher) on a site and it breaks, or the web part itself is faulty. You’ll usually get an error page that you can’t get past. The solution is rather easy…append “?Contents=1” to the end of the site url. For example, if your site that you put the web part on is “http://server/path/site/subsite/SitePages/Home.aspx”, your new URL will look like this:

http://server/path/site/subsite/SitePages/Home.aspx?Contents=1

You’ll be taken to the Web Part Page Management page for that site, where you can remove the selected web part and restore the page’s functionality.

Awesome!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube