kwizcom banner advertisement

SharePoint 2013 Composed Look Feature

December 30, 2014    , , , ,
Themes are the quick and easiest way to apply branding to SharePoint sites. Themes got changed over time in SharePoint's history. Now in SharePoint 2013, Themes are redesigned as "Composed Look" feature. As it sounds "Composed" look, it simply defines theming by combining design elements: Master page - AKA site layout, Color theme, Font schemes and background images. No more thmx - PowerPoint themes which was introduced in SharePoint 2010, these themes can't be used in SharePoint 2013. How to Apply composed look in SharePoint 2013? : You can get the option to change SharePoint 2013 themes via "Change the Look" link from the Site Settings menu. Same is available under Look and Feel group of Site settings page.  Change the look wizard and shows a thumbnail view of available designs. These designs are defined in a special list: "Composed Looks".   SharePoint 2013 Apply composed look: To apply a composed look, Click on: Site Set
SharePoint 2013 Composed Look Feature SharePoint 2013 Composed Look Feature Reviewed by Salaudeen Rajack on December 30, 2014 Rating: 5

Delete Unique Permissions (Reset Broken Inheritance) in SharePoint 2013 using PowerShell

December 27, 2014    , , , , ,
Got a requirement to reset customized permissions of a large set of SharePoint libraries and documents.You can reset the permission inheritance and delete unique permissions for a site/web/folder/item level where the inheritance was previously broken. E.g. for a library: Go to your library, Click on Library settings. In the settings page, under users and permissions, click on "Permissions for this document library" Click on "Delete Unique permissions" button in ribbon from Inheritance group. For site level, You have to do this from: Site settings >> Site Permissions Link. And for folder/list item/file level, You can do the same by: Click on "Shared with" button from the ribbon (you can get the same from items context menu) >> Click on Advanced >> and click on "Delete unique permissions". The permission levels are set to Inherited from the parent and the permission level is updated to reflect the changes.Alright! Need
Delete Unique Permissions (Reset Broken Inheritance) in SharePoint 2013 using PowerShell Delete Unique Permissions (Reset Broken Inheritance) in SharePoint 2013 using PowerShell Reviewed by Salaudeen Rajack on December 27, 2014 Rating: 5

How to Create Federated Search Results in SharePoint 2013?

December 24, 2014    , , ,
What is Federated Search in SharePoint 2013: As its name suggests, Federated search combines search results from multiple search engines. Federated search allows you to consume search indexes created by search engines outside of SharePoint. How Federated Search works in SharePoint 2013? Federated Search basically uses the index created by an another search engine. When a search query  triggered from SharePoint, it is forwarded to an external search engine and SharePoint gets the result from that index, displays the results from all configured federated sources in a single page to allow users to view results from different sources. E.g. you can set up federated search to return content indexed by an external search engine like Bing, twitter, etc.   When to use Federated search? Federation comes to play when you can not crawl the data source. Federated Search only works with indexes compatible with OpenSearch 1.0/1.1. So, its compatible with other SharePoint farms - You can fede
How to Create Federated Search Results in SharePoint 2013? How to Create Federated Search Results in SharePoint 2013? Reviewed by Salaudeen Rajack on December 24, 2014 Rating: 5

Sorry, something went wrong - The file FILENAME is locked for exclusive use by USER

December 24, 2014    , , ,
Problem:  End-Users receives error when trying to edit a file. "Sorry, something went wrong - The file FILE-URL is locked for exclusive use by USER-NAME" Root Cause: When users edit the document in client applications such as Microsoft Office, SharePoint places a locks and renews it for every 10 minutes to prevent other users from modifying it. This lock is released automatically when the client application is closed, or after 10 minutes. Solution:   But in some scenarios, lock retains due to reasons like: Client application crash, Network connectivity issues, etc.  So, the simplest solution would be wait for 10 minutes for the lock to expire. But if you want the lock to be released immediately, You can unlock it programmatically! There is no UI to unlock the locked files - as we do have for Check-in Checked-out files. So, Here is my solution to unlock the locked files using PowerShell. Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue
Sorry, something went wrong - The file FILENAME is locked for exclusive use by USER Sorry, something went wrong - The file FILENAME is locked for exclusive use by USER Reviewed by Salaudeen Rajack on December 24, 2014 Rating: 5

Reset to Site Definition via PowerShell in SharePoint

December 23, 2014    , ,
To Re-ghost customized SharePoint sites and pages, We use "Revert to Site definition" via Site Settings >> under Site Actions section, click on Reset to site definition  Choose a specific page or entire site. Click on Reset! . Reset to site definition - what does it do? Reset to Site Definition removes any customizations and reverts the file back to the version originally deployed via the Site Definition. Customized pages are stored in the Content Database (a copy with changes) and are called unghosted. When you reset, the customized copy gets deleted and the version on the file system (the Site Definition version) is used. Reset to Site Definition via PowerShell When you have to reset a Site or List to its definition in bulk, PowerShell can be utilized. Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue $WebURL ="https://intranet.crescent.com/sites/operations/us" $web = Get-SPWeb $SiteURL $web.RevertAllDocumentContentSt
Reset to Site Definition via PowerShell in SharePoint Reset to Site Definition via PowerShell in SharePoint Reviewed by Salaudeen Rajack on December 23, 2014 Rating: 5

Configure SharePoint 2013 Object Cache Super User, Super Reader Accounts

December 18, 2014    , , , ,
SharePoint 2013 object cache stores metadata about SharePoint Server objects like SPSite, SPWeb, SPList, etc. on the Web Front Ends. SharePoint features such as publishing, content query web part, navigation, search query box , metadata navigation, etc fetches data from object cache, instead of hitting SQL Server when data needs to be retrieved from SharePoint objects to optimize page rendering. For the object caching to work properly in SharePoint, We need to perform below tasks: Create user accounts for "Portal Super Reader" and "Portal Super User" in your active directory Grant web application policy on these user accounts on web applications. Associate super user and super reader user accounts to web applications These accounts simulates a reader and high-privileged users. If these accounts are not configured, you’ll see entries in the Windows event log with ids: 7362, 7363: Object Cache: The super user account utilized by the cache is not configured.
Configure SharePoint 2013 Object Cache Super User, Super Reader Accounts Configure SharePoint 2013 Object Cache Super User, Super Reader Accounts Reviewed by Salaudeen Rajack on December 18, 2014 Rating: 5

The document could not be opened for editing. A Microsoft SharePoint foundation compatible application could not be found to edit the document

December 17, 2014    
Problem:  When trying to edit an Excel sheet from SharePoint 2010 document library, user received this error message - "The document could not be opened for editing. A Microsoft SharePoint foundation compatible application could not be found to edit the document" Troubleshooting Check List: As the error message says, You must have Microsoft Excel installed in your client machine first! Follow this check list if you still getting this issue: Download and install the Hotfix as in Microsoft KB: https://support.microsoft.com/en-us/kb/2823322 , applicable when SharePoint 2010 with Office 2013 installed in client machines. Make sure you are using 32 bit of "Internet Explorer" (c:\Program Files (x86)\Internet Explorer\iexplore.exe) browser (not Google chrome or Firefox!) Make sure "SharePoint OpenDocuments Class" add-on is enabled in Internet Explorer's manage Addons page! Also under the "SharePoint open document class", click on "Mor
The document could not be opened for editing. A Microsoft SharePoint foundation compatible application could not be found to edit the document The document could not be opened for editing. A Microsoft SharePoint foundation compatible application could not be found to edit the document Reviewed by Salaudeen Rajack on December 17, 2014 Rating: 5

Migrate SharePoint Users from One Domain To Another using Move-SPUser

December 16, 2014    , , , , , , ,
Requirement: During a acquisition, Our company decided to merge with an acquired company's AD by re-creating their user Ids in our AD. Also, the acquired company had a bunch SharePoint sites and we wanted to migrate them to our SharePoint environment. That brought an another challenge of re-mapping user Ids with permission between domains. How do we migrate SharePoint users from one domain to another domain? Solution:  Well, In SharePoint 2007 days, I used STSADM to migrate users between domains: Stsadm -o migrateuser -oldlogin domain\OldUserID -newlogin domain\NewUserID -ignoresidhistory  Now with SharePoint 2013, Its replaced with the PowerShell cmdlet: Move-SPUser . $WebURL="http://intranet.crescent.com" $Web = Get-SPWeb $WebURL $OldID="i:0#.w|Crescent\Opera1" $NewID="i:0#.w|Crescent\Opera2" $OldUser = $Web.EnsureUser($OldID) Move-SPUser –Identity $OldUser -NewAlias $NewID -ignoresid -Confirm:$false Rather moving users one by one, we p
Migrate SharePoint Users from One Domain To Another using Move-SPUser Migrate SharePoint Users from One Domain To Another using Move-SPUser Reviewed by Salaudeen Rajack on December 16, 2014 Rating: 5

Fix "This workbook cannot be opened because it is not stored in an excel services application trusted location" Error in SharePoint 2010

December 15, 2014    , ,
Problem: Got this error when trying to open a Excel Sheet stored in a SharePoint 2010 document library: "This workbook cannot be opened because it is not stored in an excel services application trusted location. To create an Excel Services Application trusted location, contact your system administrator" Solution: By default, Excel Services allows browser rendering on Workbooks that are in "Trusted location". Add your SharePoint library/site/webapp URL to Excel services trusted file location to get rid of this issue. Here is how to create excel services trusted location: Navigate to SharePoint 2010 Central Administration site Under Application Management, Click on Manage Service applications Select "Excel Services Application" and click on "Manage"  Click on "Trusted File Locations" and then Click on "Add Trusted File Location" Enter the URL of your SharePoint web app/site/library and choose "Trust Children&q
Fix "This workbook cannot be opened because it is not stored in an excel services application trusted location" Error in SharePoint 2010 Fix "This workbook cannot be opened because it is not stored in an excel services application trusted location" Error in SharePoint 2010 Reviewed by Salaudeen Rajack on December 15, 2014 Rating: 5

Get All Users of SharePoint Farm-Web Application-Site Collection-Site using PowerShell

December 11, 2014    , , , , , , , ,
Requirement: Get all users of SharePoint Farm. SharePoint PowerShell to Get All Users in Farm PowerShell script to get all SharePoint users at Farm-Web Application-Site Collection-Web levels: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Output Report File $currentLocation = (Get-Location).Path $outputReport = $currentLocation + "\" + "SharePointUsers.csv" #Write CSV File Header #Array to hold user data $UserDataCollection = @() #Get All Web Applications and iterate through $WebAppsColl = Get-SPWebApplication #To Get all Users from specific web application, Use: $WeAppsColl = Get-SPWebApplication "web-app-url" #and remove line #12 foreach($WebApp in $WebAppsColl) { Write-host "Scanning Web Application:"$WebApp.Name #Get All site collections and iterate through $SitesColl = $WebApp.Sites #To Get all Users from site collection, Use: $SitesColl = Get-SPSite "site-collection-url"
Get All Users of SharePoint Farm-Web Application-Site Collection-Site using PowerShell Get All Users of SharePoint Farm-Web Application-Site Collection-Site using PowerShell Reviewed by Salaudeen Rajack on December 11, 2014 Rating: 5

The installation of this package failed - Error in SharePoint 2013 Hotfix Installation

December 08, 2014    , , , ,
During a planned quarterly maintenance window, wanted to patch SharePoint 2013 servers with available hot fixes and cumulative updates (CU). As the first step, From Microsoft site http://technet.microsoft.com/library/dn789211%28v=office.14%29 , requested hot fixes, Received an E-mail with hot fix links, downloaded those hot fixes and extracted to individual folders as in the below screen. When trying to patch SharePoint 2013 servers with those hot fixes, installation failed suddenly with an error "The installation of this package failed". Troubleshooting:  Navigated to "%Tmp%" location and tried catching the root cause of the failure from the log file generated "opatchinstall.txt". Found these lines while scanning through the log file: "Getting the data from file <path location> UBERSRV_2.cab" So, the catch here is, Hot fix installer is looking for "ubersrv_2.cab" file which we extracted into a different folder, and f
The installation of this package failed - Error in SharePoint 2013 Hotfix Installation The installation of this package failed - Error in SharePoint 2013 Hotfix Installation Reviewed by Salaudeen Rajack on December 08, 2014 Rating: 5

Disable UAC in Windows Server 2012 - SharePoint Best Practice

December 07, 2014    , , , ,
In SharePoint 2013 farms on Windows Server 2012, its annoying that we've to choose "Run as Administrator" every time when opening Central Administration, Command Prompt, SharePoint Management Shell, Windows PowerShell,etc. and failing so would introduce some weird issues such as: buttons and links missing in SharePoint Central Admin ribbon, Getting Access denied for Farm administrators, etc. PowerShell too! When launching SharePoint Management shell, it scolds with "The local farm is not accessible. Cmdlets with featuredependencyId are not registered." On running any SharePoint cmdlets, "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again." Although I'm a Domain Administrator and Local Server administrator, I've to pick "Run as Administrator" to get rid of these issues. I hate to do Right Cli
Disable UAC in Windows Server 2012 - SharePoint Best Practice Disable UAC in Windows Server 2012 - SharePoint Best Practice Reviewed by Salaudeen Rajack on December 07, 2014 Rating: 5

Fix Quick Edit Disabled in SharePoint 2013 Issue

December 07, 2014    , , ,
Datasheet view is now called "Quick Edit" in SharePoint 2013. It provides a nice flexible Excel like editor to bulk edit, copy-paste list items and metadata. Similar to a spreadsheet you can create, change and delete items in the grid. As with the new name, quick edit brought many new features in SharePoint 2013, such as: You can Edit Managed Metadata columns (Still Rich text columns are not editable in Quick Edit! content type change can't be done from quick edit!!) It works just fine in other browsers ( I tested with Firefox and Chrome), where SharePoint 2010 Datasheet view was working ONLY with internet explorer 32 bit version.  No more Active-X control dependencies. Quick edit doesn't need Office access run time engine now! It supports Filters now! Remember the pain of losing filters on datasheet views in those old days? You can launch quick edit mode either from "Quick Edit" button in List Tab, or clicking "Edit" link as in the below sc
Fix Quick Edit Disabled in SharePoint 2013 Issue Fix Quick Edit Disabled in SharePoint 2013 Issue Reviewed by Salaudeen Rajack on December 07, 2014 Rating: 5

SharePoint 2013 Sign in as Different User Missing - Feature Based Solution

December 05, 2014    ,
Sign in as different user menu option is missing in SharePoint server 2013, it has many possible workaround which are explained in my earlier post:  Sign in as Different User in SharePoint 2013 - Workarounds How to add sign in as different user in SharePoint 2013: To enable sign in as different user in SharePoint 2013, Lets build a feature based solution using Visual Studio: Open Visual Studio 2013 (or 2012) >> Click on File >> New >> Project Choose: Office/SharePoint >> SharePoint 2013 - Empty Project. Name your solution and click on "OK" Enter the site for debugging and choose "Farm Solution" (Doesn't matters even its a sandboxed solution too!) and click on "Finish" button. wait for Visual studio to create project structure. Now, in Visual studio, Right click the "Project" node from solution explorer window, choose Add >> New Item menu. Choose "Module"and give it a name. Click on Add.
SharePoint 2013 Sign in as Different User Missing - Feature Based Solution SharePoint 2013 Sign in as Different User Missing -  Feature Based Solution Reviewed by Salaudeen Rajack on December 05, 2014 Rating: 5

SharePoint Online: PowerShell to Create a List

December 04, 2014    , , , ,
Requirement: Create list in SharePoint online using PowerShell SharePoint online PowerShell create list: Here is how to create a list in sharepoint online using PowerShell #Load SharePoint CSOM Assemblies Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.dll" Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.Runtime.dll" #Variables for Processing $SiteURL = "https://Crescent.sharepoint.com/Sites/Sales" $ListName="Parent Project" #Setup Credentials to connect $Cred = Get-Credential $Cred = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($Cred.UserName,$Cred.Password) Try { #Setup the context $Ctx = New-Object Microsoft.SharePoint.Client.ClientContext($SiteURL) $Ctx.Credentials = $Cred #Get All Lists $Lists = $Ctx.Web.Lists $Ctx.Load($Lists) $Ctx
SharePoint Online: PowerShell to Create a List SharePoint Online: PowerShell to Create a List Reviewed by Salaudeen Rajack on December 04, 2014 Rating: 5

Hide "Recent" from SharePoint 2013 Quick Launch Navigation

November 25, 2014    ,
Recent section gets added automatically through a Web Control on SharePoint pages. 'Recent' menu is individual to each user! meaning everyone gets their own recent section with links to their recent activities! If you have a requirement to remove (or hide) the "Recent" menu header from the left navigation of SharePoint 2013, Here are some solutions: In Publishing sites, You can remove "Recent" section manually by going to : Site Settings >> Look and Feel >> Navigation (or Quick launch on Non-publishing sites!) . How to hide recent in SharePoint 2013 using jQuery: Edit the page, Add a script editor web part and place this code in it (or master page html) <script src="http://code.jquery.com/jquery-latest.min.js" type="text/javascript"></script> <script type="text/javascript"> jQuery(document).ready(function() { jQuery(".ms-core-listMenu-item:contains('Recent')").parent()
Hide "Recent" from SharePoint 2013 Quick Launch Navigation Hide "Recent" from SharePoint 2013 Quick Launch Navigation Reviewed by Salaudeen Rajack on November 25, 2014 Rating: 5

Cancel Workflows in SharePoint using PowerShell

November 25, 2014    , , ,
Requirement: There was a large list with workflow attached to it. SharePoint Development team came with a requirement of cancelling multiple workflows running on these list items, nearly 2000! While cancelling workflows on individual item is pretty straight forward, How about cancelling workflows on 1000's of items? Would be a daunting task, isn't it? Terminate Workflow in SharePoint using PowerShell: Well, PowerShell can help to cancel workflows in SharePoint. If you ever have to cancel multiple running workflows on all list items, use this PowerShell script: Cancel all workflows on a list: $web = Get-SPWeb "http://your-sharepoint-site-url" #List Name $list = $web.Lists["Your-List-Name"] # Iterate through all Items and all Workflows on Items foreach ($item in $list.Items) { foreach ($wf in $item.Workflows) { #Cancel Workflows [Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($wf) } } To cancel a
Cancel Workflows in SharePoint using PowerShell Cancel Workflows in SharePoint using PowerShell Reviewed by Salaudeen Rajack on November 25, 2014 Rating: 5
Powered by Blogger.