Microsoft.SharePoint.Administration.SPUsageImportJobDefinition.. An update conflict has occurred, and you must re-try this action. The object SPUsageServiceInstance was updated by....

To resolve this issue, clear the SharePoint Config Cache on all servers in the server farm. To do this, follow these steps:

1. Stop the Timer service. To do this, follow these steps:
   1. Click Start, point to Administrative Tools, and then click Services.
   2. Right-click SharePoint 2010 Timer, and then click Stop.
   3. Close the Services console.
2. On the computer that is running SharePoint 2010 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder:
   Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
4. Back up the Cache.ini file.
5. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
   
   Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All.
8. On the Edit menu, click Delete.
9. Type 1, and then click Save on the File menu.
10. On the File menu, click Exit.
11. Start the Timer service. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Right-click SharePoint 2010 Timer, and then click Start.
    3. Close the Services console.
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

One or more field types are not installed properly. Go to the list settings page to delete these fields.

This errors occurs when using CAML query with display names rather than internal names.

Solution is to use the internal name in the query. You can find out the internal names of the list columns using SharePoint Manager (http://spm.codeplex.com/releases/view/51438)

Happy coding!

An update conflict has occured, you must re-try this action again.The object SPProcessIdentity was ...

Error :

An update conflict has occured, you must re-try this action again.The object SPProcessIdentity was ...

This error occurs when any timer job task is underway and it is preventing another task. For example when you are configuring service accounts I got this error.

The solution is to clear and reset the SharePoint timer job 'Cache' by doing following steps: 

1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
2. Navigate to the cache folder
   In Windows Server 2008, the configuration cache is in the following location:
   Drive:\ProgramData\Microsoft\SharePoint\Config
   In Windows Server 2003, the configuration cache is in the following location:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
   Locate the folder that has the file "Cache.ini"
   (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
3. Back up the Cache.ini file.
4. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
5. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
8. Start the Windows SharePoint Services Timer service
9. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
10. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

Move-SPUser : The parameterless Read method can only be used when this instance was initialized with an SPUser object.

Correct way of doing it-

$user = Get-SPUser -web http://my.website.url -Identity DomainA\UserA

Move-SPUser -IgnoreSID -Identity $user -NewAlias 'DomainB\UserA'

Stsadm to Windows PowerShell mapping in SharePoint 2013

http://technet.microsoft.com/en-us/library/ff621084.aspx

Lists Stsadm operations and their equivalent Windows PowerShell cmdlets.

PowerShell command to disable the loop-back check

When you use a custom host header to create web application in SharePoint and  browse it from a local machine that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:

HTTP 401.1 - Unauthorized: Logon Failed


To resolve this issue execute the following PowerShell command to disable the loop-back check

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -value "1" -PropertyType dword

Session state has been disabled for ASP.NET. The Report Viewer control requires that session state be enabled in local mode

You might have seen error when you try to add Report Viewer web part in SharePoint 2010. 

Solution: Open 'SharePoint 2010 Management Shell' and run this command. It should resolve this issue.

Enable-SPSessionStateService –Defaultprovision

Options to refresh the content in Staging with Production environment

1. Use STSADM -o backup/restore
2. Use STSADM -o export/import
3. Use Content Deployment Wizard, you can download it from CodePlex SharePoint Content Deployment Wizard 

When you use backup/restore, you get everything - including recycle bin content, running workflows, alerts etc. This may or may not be what you want. Such 'environment-specific' things are not captured in 2 and 3 - the principle difference between 2 and 3 is that you can specify you wish all the objects (e.g. lists) to keep the same IDs. Any customizations made in the 12 or 14 hive  folder, none of these options would capture these. Such customization would need to be deployed  using WSP packages separately.