Tuesday, February 28, 2017

Uninstal workflow manager 2013

Resolution:
We executed the following steps to resolve the issue. 
  1. Deleted the following registry hives: 
HKLM\Software\Microsoft\Workflow Manager
HKLM\Software\Microsoft\Service Bus
        2.  Deleted the following databases:
SbGatewayDatabase
SbManagementDB
SBMessageContainer01
WFManagementDB
WFResourceManagementDB
WFInstanceManagementDB
       3.  Uninstalled CU1 for Workflow Manager 1.0 and CU1 for Service Bus 1.0 from Control Panel
       4.  Uninstalled Workflow Manager 1.0, Workflow Manager Client 1.0, Service Bus 1.0 and Windows Fabric in the order mentioned (Refer: http://technet.microsoft.com/en-us/library/jj193489.aspx)

       5.  Rebooted the machine hosting WFM 1.0

Monday, February 27, 2017

Timer Jobs latest changes not updating

To clear timer job cache –
Follow below steps when SharePoint 2010 timer job not updating to latest changes:
– Deploy newly updated WSP of timer job
– Stop SharePoint Timer Service
– Go to SharePoint server location –                                                                            “C:\Users\All users\Microsoft\SharePoint\Config\” 
– Backup Cache.ini
– Delete all xml files from GUID folder (GUID – this folder contains xml files with cache.ini)
– Edit Cache.ini and write 1 only
– Restart SharePoint Timer service
– XML files will create automatically
– Timer Job cache is cleared. Continue to test timer job changes

PowerShell - Event Receivers on SharePoint List


There are times when you want to check which event receivers are attached to a SharePoint list.   This can be easily achieved through use of a PowerShell script.
$spWeb = Get-SPWeb Identity http://sharepoint
$spList = $spWeb.Lists["My List"
$spList.EventReceivers | Select Name, Assembly, Type
There are also times when you might want to remove any event receivers from the list
$spWeb = Get-SPWeb Identity http://sharepoint
$spList = $spWeb.Lists["My List"
$spList.EventReceivers | Select Name, Assembly, Type

$eventsCount = $spList.EventReceivers.Count

for ($i = $eventsCount-1; $i -ge 0; $i--)
{
    $spList.EventReceivers[$i].Delete()
}

$spList.Update()

SharePoint 2010 - PowerShell Content Database Backup


“This post details the steps for backing up the content database of a SharePoint site through PowerShell.   view the steps for backing up a content database through Central Administration.”
PowerShell provides a means to backup data within SharePoint through the following command:
Backup-SPFarm -Directory [Path] -BackupMethod [Full|Differential] -Item [BackupItem] -Verbose -Percentage [Percentage]
Further information on each of the parameters in this command are outlined bellow.


Directory

The Directory parameters specifies the path where the backup will be generated.  This can either be a UNC path or a location on the server.   “You don’t need to enter the spbr* folder name as this will be auto generated”
BackupMethod
The backup method parameter details the type of backup that will be performed.  This can either be Full or Differential:
  • Full - backs up the selected content with all history
  • Differential - backs up all changes to the selected content since the last full backup
  • Item

    The item parameter specifies the component within the farm that will be backed up.  If the item has a unique name you can use just that, however, if it doesn’t then you will need to us the path to the item within the farm.In order to get the path to the item you can use the following command:
    Backup-SPFarm -ShowTree
    This will list the tree structure of items within the farm.  In my experience the path to a content database within the farm is in the following format:
    “Farm\Microsoft SharePoint Foundation Web Application\[Site Name]\[Content Database Name]”

    Verbos

    This parameter is optional.  The verbose parameter provides more information about the operation being run.

    Percentage

    This parameter is optional.  The percentage parameter can be used to report progress about the operation at defined percentage intervals.

    SharePoint 2013 - Timer job not updating after re-deployment

    SharePoint 2013 - Timer job not updating after re-deployment

    When deploying a change to an existing timer job you need to restart the SharePoint Timer Job (owstimer.exe) service before the changes will be applied.
    This can be achieved through:
    net stop SPTimerV4
    net start SPTimerV4