Pages

Wednesday, February 26, 2014

Install and configure workflow Manager1.0 for SharePoint server 2013

Install and configure workflow Manager1.0 for SharePoint server 2013

Download the Workflow Manager 1.0 and Workflow Manager Client from the Microsoft Site. Once you downloaded run the Workflow Manager 1.0 on one of the Application SharePoint Server.

NOTE: install Workflow Manager Client all the SharePoint Web Front Servers.

1. Run the setup file and click continue to finish the installation.

clip_image002

clip_image004

clip_image006

clip_image008

2. Run the Workflow Manager configuration Wizard using Recommended setup once you installed and Provide the below information and click Next

2a. Provide SQL Instance

2b. Provide Workflow Service Account

2c. enable “Allow Workflow Management over HTTP on this computer”

2d. Provide “Certification key”

clip_image010

3. Click Apply to finish the workflow configuration.

clip_image012

4. Register Workflow with SharePoint using HTTP over communication.

Register-SPWorkflowService –SPSite http://yoursharepointsite –WorkflowHostUri http://workflowhosturl:12291 –AllowOAuthHttp

Or

5. Register Workflow with SharePoint using HTTPS over communication

Register-SPWorkflowService –SPSite http://yoursharepointsite –WorkflowHostUri http://workflowhosturl:12290 –AllowOAuthHttp

Create and deploy AlwaysOn in SQL server 2012

Creating AlwaysOn in SQL server 2012

I would like to share one of the main feature of SQL server 2012 AlwaysOn Availability Group.I have implemented in SharePoint 2013 production environment for disaster recovery which works awesome.

Using AlwaysOn High Availability you can keep multiple copies of your databases in different location for disaster recovery and also it’s allows take backup in Secondary replication location as well.

There are two level fail over options available such as manual failover and Automatic failover which we can achieve if primary Server is down.

To configure AlwaysOn availability Group, follow the below steps

  • · Install and configure windows failover clustering
  • · Install same version of SQL Instance on Primary and Secondary Servers
  • · Enable Always On Availability Group in SQL
  • · Create Always on Availability Group for your databases

1. Install and configure windows failover clustering

    image

    image

    image

     image

      image

      image

     image

      image

        image

         image

         image

         image

         image

2. Enable “Always On Availability Groups” in SQL the instance on all the Servers(Primary and Secondary)

image

3. Create new availability Group on the Primary Sql Server after you enable availability Group.

   image

     image

       image

      image

        image

         image

         image

       image 

          image

            image

4. Once you created and configured the AAG group, Now you could see the database available in the Secondary Server as synchronized

image

Thursday, February 6, 2014

New Switch Plan in office 365 without Migration

Microsoft Announced new switching plan which is very good for all business people who wants to change the Office 365 plan from Small business to Mid-Size or Enterprise Plans based on their requirement without migration from old tenant to new tenant.


Plans Eligible table is below

From plan
To plan
Office 365 Small Business
Office 365 Small Business Premium
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Small Business Premium
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise K1
Office 365 Enterprise K2
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise E3
Office 365 Enterprise E4
Lync Online (Plan 1)
Lync Online (Plan 2)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Lync Online (Plan 3)
Office 365 Enterprise E4
SharePoint Online (Plan 1)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
SharePoint Online (Plan 2)
Office 365 Enterprise E3
Office 365 Enterprise E4
Exchange Online (Plan 1)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Exchange Online (Plan 2)
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Education A1
Office 365 Education A2
Office 365 Education A3
Office 365 Education A2
Office 365 Education A3
Office Web Apps with SharePoint Online Plan 1 or Plan 2
Office 365 Education A1
Office 365 Education A2
Office 365 Education A3
Office 365 Education A4
Exchange Online Kiosk
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise K1
Exchange Online Plan 1
Exchange Online Plan 2

Wednesday, February 5, 2014

Operations Started by an earlier run of the farm configuration Wizard are still in progress

I ran the configuration Wizard to configure SharePoint workflow service in sharepoint 2013 and finally got some request time out. so again I was tried to reran the configuration and got the following error message in the central admin site page "Operations Started by an earlier run of the farm configuration Wizard are still in progress. you must wait for those operations to complete before running the wizard again. you can monitor the status of these operations by looking at the "Farm configuration Wizard" timer job on the timer job status page in the monitoring section of central administration"

For the above error message I was tried the below steps to solve this issue.
1. go to monitoring-> timer job definitions
2. find "Farm configuration Wizard" and delete that timer job
 

Friday, December 27, 2013

Enable Sharepoint 2013 workflow in Office 365 Sharepoint


I was unable to find and create the SharePoint 2013 workflow using SharePoint designer for office 365 SharePoint site and I got the following message that “The option for the SharePoint 2013 workflow platform is not available because the workflow service is not configured on the server. Please contact your server administrator”


 

Finally found that reference link and it says that have to enable “Preview features” in SharePoint online Admin center setting page and it worked for me J

Wednesday, December 25, 2013

Email Address not mapped in SharePoint 2013 user profile Service


I was configured the user profile service with user profile synchronization service in SharePoint 2013. I was unable to find users Email address after done the user profile Synchronization with Active Directory. So whenever tried to set an email alert in the SharePoint site got “you don’t have email address”.

Cause:
Finally found the cause for the issue that Work Email address user property not mapped with AD mail property.

Resolution:
So I have mapped the user profile property of Work Email with Mail AD attribute in the User profile property. Below is the steps to configure

Go to central admin-> Manager Service application-> User profile Service Application-> Click Manage User properties-> Find and Edit “Work Email” property under contact information-> Remove the existing mapped AD attribute and Map the AD Attribute of “Mail” for this Work Email property and Save and close.
Finally do the AD synchronization and now you could see the Users Email address J

Monday, December 2, 2013

Sharepoint 2013 cumulative updates takes long time to install


When I was installing cumulative update of March month was taken more than 3 hours but it was not completed and I was stopped the installation of cumulative update and finally found the below script from the following link http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-umulative-update-takes-5-hours-to-install.aspx which saved my time and I want to thanks Russ Maxwell.

Below is the script and save and run it on the server.

###########################

 ##Ensure Patch is Present##

 ###########################

 $patchfile = Get-ChildItem | where{$_.Extension -eq ".exe"}

 if($patchfile -eq $null)

 {

  Write-Host "Unable to retrieve the file.  Exiting Script" -ForegroundColor Red

  Return

 }

########################

 ##Stop Search Services##

 ########################

 ##Checking Search services##

 $srchctr = 1

 $srch4srvctr = 1

 $srch5srvctr = 1

$srv4 = get-service "OSearch15"

 $srv5 = get-service "SPSearchHostController"

If(($srv4.status -eq "Running") -or ($srv5.status-eq "Running"))

  {

    Write-Host "Choose 1 to Pause Search Service Application" -ForegroundColor Cyan

    Write-Host "Choose 2 to leave Search Service Application running" -ForegroundColor Cyan

    $searchappresult = Read-Host "Press 1 or 2 and hit enter" 

    Write-Host
 
   if($searchappresult -eq 1)

    {

        $srchctr = 2

        Write-Host "Pausing the Search Service Application" -foregroundcolor yellow

        Write-Host "This could take a few minutes" -ForegroundColor Yellow

        $ssa = get-spenterprisesearchserviceapplication

        $ssa.pause()

    }
 
    elseif($searchappresult -eq 2)

    {

        Write-Host "Continuing without pausing the Search Service Application"

    }

    else

    {

        Write-Host "Run the script again and choose option 1 or 2" -ForegroundColor Red

        Write-Host "Exiting Script" -ForegroundColor Red

        Return

    }

  }

 Write-Host "Stopping Search Services if they are running" -foregroundcolor yellow

 if($srv4.status -eq "Running")

  {

    $srch4srvctr = 2

    set-service -Name "OSearch15" -startuptype Disabled

    $srv4.stop()

  }


if($srv5.status -eq "Running")

  {

    $srch5srvctr = 2

    Set-service "SPSearchHostController" -startuptype Disabled

    $srv5.stop()

  }


do

  {

    $srv6 = get-service "SPSearchHostController"

    if($srv6.status -eq "Stopped")

    {

        $yes = 1

    }

    Start-Sleep -seconds 10

  }

  until ($yes -eq 1)

 

Write-Host "Search Services are stopped" -foregroundcolor Green

 Write-Host
 

#######################

 ##Stop Other Services##

 #######################

 Set-Service -Name "IISADMIN" -startuptype Disabled

 Set-Service -Name "SPTimerV4" -startuptype Disabled

 Write-Host "Gracefully stopping IIS W3WP Processes" -foregroundcolor yellow

 Write-Host

iisreset -stop -noforce

 Write-Host "Stopping Services" -foregroundcolor yellow

 Write-Host
 

$srv2 = get-service "SPTimerV4"

  if($srv2.status -eq "Running")

  {$srv2.stop()}


Write-Host "Services are Stopped" -ForegroundColor Green

 Write-Host

 Write-Host
 

##################

 ##Start patching##

 ##################

 Write-Host "Patching now keep this PowerShell window open" -ForegroundColor Magenta

 Write-Host

 $starttime = Get-Date
 

$filename = $patchfile.basename

 $arg = "/passive"
 

Start-Process $filename $arg
Start-Sleep -seconds 20
 $proc = get-process $filename

 $proc.WaitForExit()

 

$finishtime = get-date

 Write-Host

 Write-Host "Patch installation complete" -foregroundcolor green

 Write-Host
 

##################

 ##Start Services##

 ##################

 Write-Host "Starting Services Backup" -foregroundcolor yellow

 Set-Service -Name "SPTimerV4" -startuptype Automatic

 Set-Service -Name "IISADMIN" -startuptype Automatic

##Grabbing local server and starting services##

 $servername = hostname

 $server = get-spserver $servername

$srv2 = get-service "SPTimerV4"

 $srv2.start()

 $srv3 = get-service "IISADMIN"

 $srv3.start()

 $srv4 = get-service "OSearch15"

 $srv5 = get-service "SPSearchHostController"

###Ensuring Search Services were stopped by script before Starting"

 if($srch4srvctr -eq 2)

 {

    set-service -Name "OSearch15" -startuptype Automatic

    $srv4.start()

 }

 if($srch5srvctr -eq 2)

 {

    Set-service "SPSearchHostController" -startuptype Automatic

    $srv5.start()

 }

###Resuming Search Service Application if paused###

 if($srchctr -eq 2)

 {

    Write-Host "Resuming the Search Service Application" -foregroundcolor yellow

    $ssa = get-spenterprisesearchserviceapplication

    $ssa.resume()
 }
Write-Host "Services are Started" -foregroundcolor green

 Write-Host

 Write-Host

 Write-Host "Script Duration" -foregroundcolor yellow

 Write-Host "Started: " $starttime -foregroundcolor yellow

 Write-Host "Finished: " $finishtime -foregroundcolor yellow

 Write-Host "Script Complete"