Tag Archives: Web Content Management

‘Content Type is still in use’ woes

Problem

Anyone that is familiar with SharePoint would have come across this error and it can be a painful process trying to determine where the content type is being used. Most articles I have come across highlight several areas that you need to check.

  1. Document libraries / Lists (as a managed content type).
  2. Individual files using the content type.
  3. Running workflows that are based on the content type.
  4. Workflow tasks
  5. Recycle bin (you need to empty your recycle bin).

That is all well and good, but it becomes an extremely tedious task when you have several large document libraries with thousands of items.

Solution

SharePoint Manager to the rescue. You can download the program at: http://spm.codeplex.com/

It basically gives you a tree view of every item in SharePoint and allows you to drill down to the properties of individual items.

Here, you can see where a content type is being used:

  1. Run SharePoint Manager 2010
  2. Drill down to the site where your content type was created.
  3. Select your content type, expand Usages.
  4. You should now see all the locations where your content type is being used.

 

Comments ( 2 )

Change content type for all documents in a library

Requirement

An old migrated library is populated with several thousand documents with the default content type set to ‘Document’. All the documents now need to be assigned a specific content type.

Solution

Found a powershell script that does the trick:

http://get-spscripts.com/2010/10/change-content-type-set-on-files-in.html

 

Comments ( 1 )

Event 7362 – Web Content Management

Problem:

Log Name:      Application
Source:        Microsoft-SharePoint Products-Web Content Management
Date:          <date>
Event ID:      7362
Task Category: Publishing Cache
Level:         Warning
Keywords:
User:          <username>
Computer:      <server>
Description:
Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
 Additional Data:
 Current default super user account: SHAREPOINT\system

Solution

Step 1 – Create AD Domain Accounts

Create domain accounts for the ‘portalsuperuseraccount’ and ‘portalsuperreaderaccount’. I use sp.superuser and sp.superreader but the naming is up to you.

Step 2- Assign Account Permissions

Run SharePoint Management Shell and execute the following commands:

$wcm = Get-SPWebApplication -Identity http://<url of web application>
$wcm.Properties[“portalsuperuseraccount”] = “<domain>\sp.superuser”
$wcm.Properties[“portalsuperreaderaccount”] = “<domain>\sp.superreader”
$wcm.Update()

Step 3- Modify the Web Application User Policy

Central Admin -> Manage Web Application -> User Policy
Add sp.superuser – Full Control
Add sp.superreader – Full Read

Reboot your SharePoint farm

You will need to reboot your SharePoint servers for the changes to take effect.

Note* You have to run the above commands on each Web Application if you have more than one.

Testing

SharePoint Management Shell, type the following command

stsadm -o getproperty -propertyname portalsuperuseraccount -url <url of web application>

The output should be something like this.

<PropertyExist=”Yes” Value=”<domain>\sp.superuser” />

 

Comments ( 0 )