Thursday, January 31, 2013

Adding a Description Column for a folder under Document Library

  • Go to Site Actions, Site Settings
  • Click Site Content Types
  • Click Create
  • Give the new content type a name such as "Description"
  • Set the parent content type group as Folder Content Types
  • Set the parent content type to Folder
  • Add the new content type to a Group. I put it back in the "Folder Content Types" group
  • Click OK
  • Scroll down to the columns section and click Add from new site column
  • Name the column and set all the usual column options
  • Repeat for any additional columns
  • Click OK
  • Go to your document library
  • Click Settings and Library Settings, or in 2010 click the Library ribbon tab and then click Library Settings
  • Click Advanced and set Allow management of content types to Yes and click OK (this may already selected)
  • Scroll down to Content Types and click Add from existing site content types and add your new folder content type
  • Go to your document library and click the New drop down, or the New button in the 2010 Document ribbon, and add your new folder!
  • Go to the View drop down and click Modify this view and add your new folder meta data columns (you will probably want to move them to just after the Name column)

How to hide the Left navigation or Quick launch in SharePoint 2010

To hide the left navigation bar or Quick launch , you can follow the below mentioned steps.
Go to à Site Actions à Edit Page à Add a webpart à Add Content Editor Webpart
Modify shared webpartà Edit the Source Code and paste the below code in Source code .

body #s4-leftpanel
display: none;
margin-left: 0px;

Select Ok. Then from the Appearance Section Hide the webpart à Click Apply Ok. à Exit Edit mode.
Hope this helps

Wednesday, January 30, 2013


FAST Search Server 2010 for SharePoint delivers an exceptional intranet and people search experience and a platform for building custom search-driven applications.

Basics that may Interest you:

FAST is a Norwegian company based in Oslo, On April 24, 2008, Microsoft acquired FAST. FAST is now known as Microsoft Development Center Norway.

FAST uses complementary technologies from BBN Technologies for speech recognition and Stellent (now part of Oracle) for the conversion of different file formats. 

Why do we need FAST with SharePoint 2010

Automatic Metadata – To avoid any confusion or ambiguous Meta tagging, FAST metadata generation occurs while the content is being created. Now you have terms and language that are familiar to your team and often unique to your business.

Relevance Tuning – Relevancy is key. You have a specific topic in mind when you search so why settle for receiving a slew of extra findings? This relevance is subjective among different users and locations in your company so FAST gives you the ability to fine tune your search model to the needs of different applications to benefit each user type or persona.

Contextual Matching – Think comprehensive. FAST highlights the context and intent of the query to give you the best results, all matched with terms and phrases that appear in the context of the matching text. After all, search is only as strong as its context and FAST captures these contextual results with precision to deliver a specific, superior search experience.

Visualizing Search Results – Why not see before you click? This speaks again to the productivity of FAST when you can see a search result before you click. Users can access thumbnails and preview images from search results so they can recognize the correct content quickly and with better context. Admins can add visual banners and apps with Visual Best Bets to pinpoint critical information for their users.

Backbone for Search-Driven Applications – FAST allows you to build search-driven apps for specific roles in your company. The apps gather specific content from defined sources and add structure to unstructured information and, as a result, specific user groups increase their productivity with a more contextual and interactive search experience.


Friday, January 25, 2013

You receive “cannot complete this action” error message whenever you try to do anything on your site

This situation basically occurs when you try to backup restore or migrate the sites between two server farms, usually the biggest problem you may face while migration site between two farms is that the user SID gets Screwed for good and then the hell breaks loose when you cannot get users log in to the site the permissions are messed up,

Check these few things before your land up to a conclusion.

Symptoms Faced:
Cannot backup restore or Delete a site collection, you face “Cannot complete this action” error message from Both GUI and Command prompt (I mean stsadm, of course)

This error message sounds a permission problem to you so there you go … start checking these

Run the command stsadm -o migrateuser with the problem account, if its successful you are done otherwise try

stsadm -o updatefarmcredentials

Remember you will have to hit IIS reset after this

Check if the account is available on WSS_WPG; WSS_ADMIN_WPG; IIS_ADMIN_WPG

If the migrate user command fails because you use the same accounts both times then create a temporary account that you create in AD and run the command as

Stsadm –o migrateuser –oldlogin domain\problem account –new login domain\temporary account –ignoresidhistory
Then run
Stsadm –o migrateuser –oldlogin domain\ temporary account –new login domain\ problem account –ignoresidhistory

Make some other account as a site collection administrator, remove the problem account from site collection admin and re-add it
From the link

When permissions are established by NT/XP network ID, problems can arise when an ID is stopped and restarted. When a network user ID is (re)established and there are pre-existing permissions for that ID in a SharePoint site by virtue of membership in site groups by user name (as opposed to domain group membership) and/or as the owner of a site, the person will not be able to access the site. Instead they will get an error message like “Cannot complete this action. Please try again”.
In this case the ID must be removed from the site. This may be easier said than done.

Change the site owner to somebody else. This is done by the server administrator on page “siteusrs.aspx.”

Remove the ID as a site user by removing it from membership in site groups, including any custom list permissions.

This is complicated because SharePoint does not use the text of the user’s ID but a SID, which is different each time the network ID is re-established.

· Finally when you are convinced that this is not a permission problem run the hot fix 956994, which can be obtained from the Support professional also you can try running a very generic KB 936867, which is included in Service pack 1 for MOSS

This fixes the issue for the site with broken permissions problems

Traces of portal 2003 on my MOSS site

I just ran into an issue yesterday where,we have upgraded the environment from Portal 2003 to MOSS 2007 with Gradual upgrade everything is running just fine, but when we try to go into a sub site which has some lists inside it I try to browse through the lists and i find that the lists contain and interface of portal 2003
Just a little background here, the portal 2003 SharePoint site was heavily customized with banner and bread crumbs and quick launch bar, we took out all the customizations before we run the prescan which was successful. then we run the gradual upgrade and this bought the default pages of the site
The issue is I am running into is that the some document libraries still show the SPS2003 Interface. Initially you might think that this is a result of incorrect upgrade, you can try running the command

stsadm –o –upgrade –inplace –url <url of the site> –forceupgrade

If this does not help try resetting site to site definition from the top level site this works in 90% scenarios
I was able to get over the issue with creating a new view on my document libraries and which helped me get rid of the portal 2003 interface
That means when the upgrade was performed the Views did not get updated and sustained the old SPS 2003 look and feel so in short the default views got corrupt and so we have to work around it by creating a new view and replacing the default view.

SPD workflow Failed on start (retrying)

I have been wrestling with this issue for about 60 days, the issue occurs when you create a simple OOB SPD workflow or even a Nintex workflow.
The solution to this is two parts

The service account should be a part of
1. Looked at the groups in the local machine
· WSS_ Restricted
· WSS_Admin_WPG
2. Checked on the SQL management studio  > security > logins > Service account > properties > server roles were given as dbcreator > security & system admin > public
      Looked in user mappings the service account  was set db owner
3. >> Looked in the application content database in SQL
      service account should be  is a db owner
4. In  Central Admin page  > policy for web application > add service account as full control 
5. CA > operations tab > update farm administrators group > service account is added there
6. looked in the site > site settings > site collection administrator
7. looked in the component services > dcom config > IIS admin service > security > added the service account to launch and activation > access permissions > and Configuration permissions .

After doing all these settings the service account must have all the require permissions

Second part of the solution is change the service account from the central admin page & run an IIS reset
this is the main key and you will have to compulsorily do this to resolve the issue

hope it works for you

Popular Posts


The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.