The installation of workflow manager for development environment can be done on single server SharePoint 2013 farm, but it is highly recommended to install it on separate server for UAT and production environments.
You need local admin rights on the server where you will install the Workflow manager.
Please make sure that Visual studio 2012 Instance is not running and all devenv.exe processes are closed.
Make sure that you have Visual studio Update 2 installed
Navigate to http://www.microsoft.com/web/downloads/platform.aspx and download and download Microsoft Web Platform installer 4.5 (If you don’t have already installed)
Install Microsoft Web Platform installer 4.5
Launch the Microsoft Web Platform installer 4.5
In the top right corner search box, enter “workflow manager”, you will see the following results
Click “Add” button to the following items
Workflow Manager 1.0 Cumulative Update 1
Workflow Manager Tools 1.o for Visual Studio 2012
Workflow Manager 1.0
You can view the” Item to be installed” to make sure that you have added the right items
Click “Close” , it will take you ro the previous screen
Click “Install” button
Press “I Accept” button and the workflow manager instalaltion process will start
After some time you will see the following screen
Fill the below information according to your environment and press Click next arrow button.
You will see the summary page, Press “Check” button and workflow manager configuration wizard will be started
Once the Configuration process is completed, you will see the last screen
Once the installation completes go to IIS 7 manager and start the “Worklfow Management Site”, if not started.
Create a site colleciton in sharpoint and register Wrokflow service with it using powershell command
Register-SPWorkflowService -SPSite “SharePoint site collection url” -workflowHostUri “workflow host site url with port” –AllowOAuthHttp
Workflow Manager communicates by using TCP/IP or Named Pipes. Make sure that the appropriate communication protocol is enabled on the SQL Server instance that hosts the Workflow Manager databases.
The SQL Browser Service must be running on the SQL Server instance that hosts the Workflow Manager databases.
Welcome to SharePoint 2013, the new way of building workflows
I have just enabled SSL on our live intranet site and run the full crawl to index everything to https rather than http. Everything works fine apart from default page. It shows error, when I checked the log file it shows the following error details.
GetFileFromUrl: ArgumentException when attempting get file Url http://site url/_catalogs/masterpage/ PageLayoutName.aspx Value does not fall within the expected range.
During further investigation I found that the default page “Page layout” was still referencing to http address. The below script will update default page “page layout” URL.
$spWeb = Get-SPWeb("https://site collection URL") $spFile = $spWeb.GetFile("https://site collection URL/Pages/default.aspx") $spFile.CheckOut("Online",$null) $spFile.Properties["PublishingPageLayout"] = "/_catalogs/masterpage/SCI_HomePage.aspx, Block" $spFile.Update() $spFile.CheckIn("Update page layout via PowerShell",[Microsoft.SharePoint.SPCheckinType]::MajorCheckIn) $spWeb.Dispose()
In one of my previous post I mentioned how to clean the SharePoint 2010 web application before upgrade to SharePoint 2013.
In this post, I will explain what Information in required from SharePoint 2010 Farm during the SharePoint 2013 upgrade planning.
The following information need to be capture from your existing SharePoint 2010 Farm.
As some of you noticed that in SharePoint 2013 welcome menu options “Sign in as Different User” is not available by default. You need this for various reasons and there is a work around to achieve it.
SP 2010 default Welcome Menu
SP 2013 default Welcome menu (missing “Sign in as Different User” option)
Go to the “C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES”
Locate the following file welcome.ascx and open in Notepad.
Add the below code to the welcome.ascx as appear in image. In my case I have added at the start to appears as first option in welcome menu
<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser" Text="<%$Resources:wss,personalactions_loginasdifferentuser%>" Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>" MenuGroupId="100" Sequence="100" UseShortId="true" />
Navigate to the site and click on Welcome menu, the Sign in as Different User option is now available as appear below
Imagine you have created two SharePoint 2013 web applications. They are hosted on same web front end server with default post 80.The web applications URL’s are something like web1.eblogin.com and web2.eblogin.com. You want to enable SSL on both web applications and have wildcard SSL certificate (*.eblogin.com).
I came across this scenario during a project where I need to do SSL binding for Intranet site and my sites web applications. I have tried it with normal process. I opened the IIS 7 manager, clicked on the web1.eblogin.com web site and then under the actions menu “bindings” option, provided the binding details and clicked OK. I then repeated the same steps for web2.eblogin.com. As a result it eventually drops the SSL certificate binding for the web1.eblogin.com. I tried again on web1.eblogin.com which then drops the binding for web2.eblogin.com
Option 1: Always create SharePoint 2013 Web applications with SSL enabled and provide host header at the first place. It will do the SSL certificate binding automatically for the web application.
Option 2: The first workaround is not always applicable. For example, what if the business provide SSL certificate after you set up site structure or may be after site goes live. In this case you might end up re-creating the web applications with SSL enabled and reattach content database to them. So the resolution to this is
Go to front end web server where the web applications are hosted
Open command prompt
Navigate to the AppCmd.exe physical directory
Run the following command for each web application to do SSL binding
//command to run appcmd set site /site.name:" Site name as appear in IIS" /+bindings.[protocol='https',bindingInformation='*:443:web1.eblogin.com]
After this you can run the following Windows PowerShell command to get the binding details for a particular web application
Get-WebBinding ‘Site Name as appear in IIS '
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
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.
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
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.
You can find the OOTB onet.xml of blog site template at the following location
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\SiteTemplates\Blog
I was surprised that there is not any default.aspx page for this blog template which was available in SharePoint 2010. The OOTB SharePoint 2013 blog site template folder has missing default home page.
I have imported the Onet.xml file in visual studio; it contains the following web features.
<WebFeatures> <!-- TeamCollab Feature --> <FeatureID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5" /> <!-- MobilityRedirect --> <FeatureID="F41CC668-37E5-4743-B4A8-74D1DB3FD8A4" /> <!-- Blog feature --> <FeatureID="FAF00902-6BAB-4583-BD02-84DB191801D8" /> <!-- MDS --> <FeatureID="87294C72-F260-42f3-A41B-981A2FFCE37A" /> </WebFeatures>
After few minutes I realised that there is a feature in 15 hive which called “Blog Home Page”.
You can find the “Blog home page” feature.xml at the following location
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES
You need to reference this feature in blog site definition to make sure that when a user create site based on your custom blog template, it activates this feature which create home page for blog site.
The resulting Web feature node in blog onet.xml will look like this
<WebFeatures> <!-- TeamCollab Feature --> <FeatureID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5" /> <!-- MobilityRedirect --> <FeatureID="F41CC668-37E5-4743-B4A8-74D1DB3FD8A4" /> <!-- Blog feature --> <FeatureID="FAF00902-6BAB-4583-BD02-84DB191801D8" /> <!-- MDS --> <FeatureID="87294C72-F260-42f3-A41B-981A2FFCE37A" /> <!-- Blog Home Page feature --> <FeatureID="E4639BB7-6E95-4E2F-B562-03B832DD4793"/> </WebFeatures>
Some time when writing a custom solution in SharePoint which takes some time to process, it is nice to show end user some message screen saying something like “Please wait we are dealing with your request”.
In SharePoint 2010 this functionality is available out of the box, we can call SPLongOperation class in code and display the below screen with custom message and also can redirect to a different page after completion.
// Initialise SPLongOperation object and specify message you want end users to see. SPLongOperation lp = new SPLongOperation(this.Page); lp.LeadingHTML = "<div><h2>Processing Request</h2></div>"; lp.TrailingHTML = "<div><h3>Please wait, your request is being processed</h3></div>"; lp.Begin(); // long running code start // long running code end lp.End(Customers.DefaultViewUrl, Microsoft.SharePoint.Utilities.SPRedirectFlags.Default, this.Context, "");
I hope this will help.