The feature failed to activate because a list at 'PublishingImages' already exists in this site. Delete or rename the list and try activating the feature again.

The most common issue we may face when we try to activate SharePoint Publishing infrastructure Feature from Manage site features.

Try to activate that feature using Shell command. It will work out with out error:

 Enable-SPFeature -Identity PublishingWeb -URL http://test:1000/ -Force

thank you,

Adding User Permissions using Power shell script in SharePoint 2013

In SharePoint we are having permission level operations. To that SharePoint group we can add users through Site Settings -> Site Permissions.

And also we can give permissions using PowerShell scripts.

For Single User:

new-spuser -UserAlias "User1" -Web "http://test:100/sites/home1" -Group "TestUsers"

For Every One:

new-spuser -UserAlias "Everyone" -Web "http://test:100/sites/home1" -Group "TestUsers"

By executing this PowerShell script we can add users to the SharePoint groups.


thank you,

Change the "SharePoint" text in the top left corner

$webApp = Get-SPWebApplication http://tozit-sp:2015
$webApp.SuiteBarBrandingElementHtml = "New Text Here"
$webApp.Update()

How to enable and disable Quick launch in SharePoint 2013

To display the Quick Launch menu using the SharePoint 2010 web interface, follow these steps:

1. Navigate to Site Actions, Site Settings, Tree View (under Look and Feel).
2. Select the Enable Quick Launch check box and click OK

This will enable and disable the quick launch.

View all Webparts on your SharePoint Page

All you need to do is add this string to the end of your URL "?contents=1" on any of your SharePoint Pages

for example:
http://mysharepoint/default.aspx?contents=1

How to Enable session in your web application

Change settings in your web.config file

change enable session as true

<pages enableSessionState="true">

add the following code with in the  <modules> tag

<add name="Session" type="System.Web.SessionState.SessionStateModule" preCondition="" />

Thats it.. Now you can store values in session.

This content database has a schema version which is not supported in this farm

we usually face this issue when we try to mount content db.

It is because of the database version conflict.

Just go to your local database and open Versions table and check the version of your database.

now open the database which you are trying to mount and open the Versions table and change its version as per your database version.

now try to mount your database again.

Mount Content DB:

Mount-SPContentDatabase -Name WSS_Content_DB_ToAttach 

-WebApplicationhttp://mywebapplication:port

Dismount Content DB:

Dismount-SPContentDatabase -Identity WSS_Content_DB_ToAttach

Remove Content DB:

Remove-SPContentDatabase -Identity WSS_Content_DB_ToAttach