Post upgrade Issue: SharePoint 2013 custom list "Quick edit" button is disabled

21. March 2013 12:33 by Rashid Aziz in Sharepoint blogs  //  Tags: ,   //   Comments
I am in middle of testing a SharePoint 2010 to SharePoint 2013 project upgrade. I have faced couple of issues, the one is that the List “Quick edit” button is disabled in SharePoint 2013 after upgrade content database from SharePoint 2010 Workaround I have just created a datasheet view in SharePoint 2013 list, clear browser cache and render the list page again. I have switched the view to datasheet view and now I am able to do bulk editing. When switched back to main view I found that “Quick edit” button is now enabled under list tab. You can also create “Access view” which will download the list schema with data into access database. You can make the changes in access and hit save. It will sync the changes to SharePoint list.  You can also get the latest SharePoint 2013 list data by clicking “Refresh all.

Upgrade Web application from SharePoint 2010 Farm to SharePoint 2013 Farm

12. March 2013 03:17 by Rashid Aziz in Sharepoint blogs  //  Tags: ,   //   Comments
The following steps will explain the upgrade process of SharePoint web application from SP 2010 to SP 2013 Farm Backup the Content database from SP2010 server using SQL management studio Move the database to SharePoint 2013 SQL server. Restore the content database on SharePoint 2013 SQL server using SQL management studio Upgrade custom code from visual studio 2010 to VS 2012 and Version 15 of SharePoint (Recommended). Although, you can still deploy the SharePoint 2010 code on SharePoint 2013 Farm under 14 hive) Create new web application and root site collection in SharePoint 2013 Farm using “Central Administration” Deploy custom solutions to the SharePoint 2013 Farm (make sure they are deployed on new web application) Remove the default content database from the newly created web application using “Central Admin” Attach the SharePoint 2010 web application content database to new web application in SP 2013 using PowerShell script Run Test-SPContentDatabase cmdlet to identify missing components along with potential errors and related warnings. Check the upgrade log and deploy any missing components and re run the cmdlet to verify. Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename Attach the content database to the SharePoint 2013 web application using Mount-SPContentDatabase cmdlet. // Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename Navigate to the site and run visual upgrade (To upgrade the site simply click on "Start now" link on the toolbar, you can also go to Site Upgrade page from Site Setting page as well). Once the Upgrade complete, your site collection should now be accessible in SharePoint 15 mode Note: The default authentication type in SharePoint 2013 is “Claim based”. You can still create web application with” Classic authentication” in SharePoint 2013 through PowerShell, but it is recommend using Claim based Authentication in SharePoint 2013 web apps for variety of reasons.  Also, windows Classic mode authentication is deprecated in SharePoint 2013. If your SharePoint 2010 web application is set to classic mode authentication type, then change it to claim based authentication either before or after upgrade web App to SharePoint 2013 Farm. For more info visit: http://technet.microsoft.com/en-us/library/gg251985.aspx  

Clean the SharePoint 2010 Environment before upgrade to SharePoint 2013

12. March 2013 03:12 by Rashid Aziz in Sharepoint blogs  //  Tags: ,   //   Comments
 It is highly recommended to do bit cleaning before you do an upgrade of SharePoint 2010 environment to SharePoint 2013.We need to make sure that environment is running and fully functioning, and should clean up all those contents which doesn’t required upgrade. You should consider the following items to clean up before upgrade. Delete Site collections/Sub sites which are no longer in use You should consider moving site collection into separate content databases for better performance and scalability You need to remove unused custom features, web parts, templates, event receivers, workflows etc Make sure if you have large list (Lists with a lot of data in it), user should not be able to query data which exceed the threshold limit set on Web applications Document versions can slow down an upgrade process. If you do not have to keep multiple versions, use the object model to find old versions and remove them or ask users to delete unnecessary documents version manually The default authentication type in SharePoint 2013 is “Claim based”. You can still create web application with” Classic authentication” in SharePoint 2013 through PowerShell, but it is recommend using Claim based Authentication in SharePoint 2013 web apps for variety of reasons.  Also, windows Classic mode authentication is deprecated in SharePoint 2013. You cannot upgrade “FAST Search Centre” sites to the SharePoint 2013 environment. The current “FAST Search Centre” sites can continue to work in SharePoint 2010 mode after upgrade. If you want the have new SharePoint 2013 functionality, you have to create ” Enterprise Search Centre” sites in SharePoint 2013 mode.  

Upgrade sharepoint 2007 site to sharepoint 2010

13. February 2011 08:48 by Rashid Aziz in Sharepoint blogs  //  Tags: ,   //   Comments
  There are lot of people out there who are really excited about the SharePoint 2010 release. Today I will be providing you with a guide to upgrading your SharePoint 2007 content databases to SharePoint 2010 using database attach upgrade method. To complete this operation, you need to complete the following steps 1.       Pre Upgrade Check This will be our primary analysis and reporting tool  which will provide information regarding your SharePoint 2007 farm and actions that may be required to take prior to upgrading to SharePoint 2010  Launch a Windows command prompt on your SharePoint 2007 Server and go the the stsadm directory path which is given below. C:\PROGRAM FILES \COMMON FILES\Microsoft Shared\Web Server Extensions\12\bin Run the following command stsadm.exe –o preupgradecheck   When the pre-upgrade process completes, you will receive the following message “Operation completed successfully” .It will then launch your web browser displaying the results in HTML format, titled “SharePoint Products and Technologies Pre-Upgrade Check Report”.  These results can also be located under the following location C:\PROGRAM FILES \COMMON FILES\Microsoft Shared\Web Server Extensions\12\Logs   2.       Backup database using PowerShell Below is the PowerShell script to do database backup. You need to change SQL server name, database name and location where you want to save backup file. You can also do database backup using SQL management studio. [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO')|out-null [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMOExtended')|out-null $s = New-Object ('Microsoft.SqlServer.Management.Smo.Server') "localhost" $dbBackup = new-object ("Microsoft.SqlServer.Management.Smo.Backup")  $dbBackup.Database = "WSS_Content_Intranet" $dbBackup.Devices.AddDevice("C:\Test\WSS_Content_Intranet.bak", "File") $dbBackup.Action="Database" $dbBackup.SqlBack Copy the database backup file to your SharePoint 2010 machine. 3.       Restore database using PowerShell Below is the PowerShell script to do database restore. You need to change SQL server name, database name and location of the database you want to restore. You can also restore database using SQL management studio. [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | out-null [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMOExtended') | out-null $s = New-Object ('Microsoft.SqlServer.Management.Smo.Server') "localhost" $dbRestore = new-object ("Microsoft.SqlServer.Management.Smo.Restore") $dbRestore.Database= "WSS_Content_Intranet" $dbRestore.Devices.AddDevice("C:\Test\WSS_Content_Intranet.bak", "File") $dbRestore.Action="Database" $dbRestore.NoRecovery = $false $dbRestore.ReplaceDatabase = $true $dbRestore.SqlRestore($s)    4.       Create your SharePoint 2010 Web Application and Site Collection Go to SharePoint 2010 central admin and under “Application Management” click “Manage Web Applications”      Click “New” under “Web Applications” tab      Fill new web application form and click “Ok”     Fill the required fields and click “Ok” to create site collection    5.       Verifying the Content database The Test-SPContentDatabase is a great reporting tool that will list any missing setup files, web parts and provide you with information on how to remedy any errors.  It will also specify whether these missing features will block the upgrade from succeeding.  Test-SPContentDatabase –Name <database name> -WebApplication <URL> Launch the SharePoint 2010 Management Shell and type the above command, ensuring you have entered your Database Name and URL. e.g. below  Test-SPContentDatabase –Name WSS_Content_Intranet -WebApplication http://testsite     6.       Remove Database from Web Application Ensure that there are currently no databases connected to the web application that we will be attaching to.  You can check this via Central Administration / Application Management / Manage content databases.  Go to SharePoint 2010 central admin and click “Manage Content Database” under “Application Management” Select your newly created web application “testsite” and click on the database which is attached to it.    Check “Remove Content database” and click “Ok” to remove content dataset from web application 7.       Attach database to SharePoint 2010 web Application We can now proceed and attach our restored SharePoint 2007 database via the following stsadm command line  stsadm -o addcontentdb -url <URL> -databasename <database name> In my instance, the command looked as follows; Stsadm –o addcontentdb –url http://testsite –databasename WSS_Content_Intranet     We can now verify that the upgrade was completed successfully by first navigating back to Central Administration / Application Management / Manage content databases, which now displays the upgraded database under my designated Web Application. We can also view the upgrade status page which is located within Central Administration / Upgrade and Migration / Check upgrade status. 8.       Visual Upgrade To perform the Visual upgrade, navigate to Site Actions / Visual Upgrade. You can also user PowerShell script to perform visual upgrade to all sites and sub sites in site collection. Script is given below. You need to change the database in the given script name according to your environment. $db = Get-SPContentDatabase WSS_Content_Intranet  $db.Sites | Get-SPWeb -limit all | ForEach-Object { $_.UIversion = 4; $_.UIVersionConfigurationEnabled = $false; $_.update() }  Go to SharePoint 2010 central admin and click “Create Site Collections” under “Application Management”

Stay connected

SharePoint Links

Month List