Invalid option '7.3' for /langversion; must be ISO-1, ISO-2, Default, Latest or a valid version in range 1 to 7.1.

Solution : 

Select the latest language version in advanced build setting as shown below.

AzureRM.Profile.psm1 cannot be loaded because running scripts is disabled on this system. - Import-Module AzureRM.profile

Set-ExecutionPolicy RemoteSigned

Above powershell command sets the execution policy to run the scripts on the system.

"No records found for given DNS query." (error code 0x0000251D DNS_INFO_NO_RECORDS) The query was for the SRV record for _ldap._tcp.dc._msdcs...

The error was: "No records found for given DNS query." (error code 0x0000251D DNS_INFO_NO_RECORDS)  The query was for the SRV record for _ldap._tcp.dc._msdcs....

To resolve this error-
1. Make sure DC has static IP configured.
2. Run the DCDIAG /test:DNS command to ensure the tests are passed
3. Make sure client computer is using the DC as a DNS server

Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

If there are GPO in place, you should make sure service accounts have Log on as a Batch Job permissions

Because of this STS Token service - SecurityTokenServiceApplicationPool will not run or keeps stopping.
Central Admin site application pool keeps stopping

You will see the following error in the event log -

Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

Internet Explorer cannot display this feed - REST api not working in IE

If IE is responding correctly to REST api calls and you get a message like

Internet Explorer cannot display this feed

To fix the problem we need to disable feeds in IE. Go to the browser settings and select the Content tab, and click on the Feeds Settings button:


Then uncheck the "Turn on feed reading view" (it defaults to on, naturally).

This is for IE10. Other versions might look slightly different.

Cannot access Host Named Site Collection on a local server ( BackConnectionHostNames / DisableLoopbackCheck )

Method 1 (recommended): Create the Local Security Authority host names that can be referenced in an NTLM authentication request

To do this, follow these steps for all the nodes on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. In the Name column, type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
   
   Note Type each host name on a separate line.
   
   Note If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
7. Exit Registry Editor, and then restart the computer.

Method 2: Disable the authentication loopback check

Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry

subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

Using PowerShell:

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

Unexpected response from server. The status code of response is 500. The status text of response is system.servicemodel.serviceactivationexception - When accessing TERM-Driven-page link on Term Store Management

If you encounter this weird error message while accessing TERM-Driven-page link on Term Store Management, don't get panic.. the solution is very simple :-)

'iisreset /noforce' 

Happy Sharepointing!

The workflow could not copy the item. Make sure the source and destination lists have the same columns and column settings

This error occurs when you use 'Copy List Items' Action to copy a list item from one document library to another in SharePoint 2013 Designer using SharePoint 2010 Workflow.

It can be resolved by making sure that the destination document library does not require document to be checked out for editing.

Following setting should be set to No under List Advanced settings
 Require documents to be checked out before they can be edited?

 

How to delete a Published Contnet Type ?

Subscriber site won't allow the content type to be deleted by default. When you click on Advanced Settings, change the Read Only option to No. After you do this you will be able to delete it. Happy Sharepointing!!

The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service

This error occurs when you try to start a custom workflow associated with a list or an item. To fix this error the State Service need to be configured in the farm. Here is the official solution from Microsoft - http://support.microsoft.com/kb/2697977

'DisableLoopbackCheck' to fix - Error: Access is denied. Verify that either the Default Content Access Account has access to this repository .........

Error:

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

Root Cause :

This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.

This is because your operating system(Windows 2008 in my case) include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.

Resolution:

Following instructions would disable the LoopBackRequest in registry. 

1. Run regedit.exe from the command prompt

2. In the registry editor navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"

3. Right click on "Lsa" and create a new 32bit DWORD value called DisableLoopbackCheck

4. Right click  and Modify the value of "DisableLoopbackCheck" as "1"

6. Close the registry editor.

You may now restart the crawl and hopefully it will work.

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.

Get-SPDatabase – How to see the SharePoint content DB size

Get-SPDatabase | ForEach-Object {$db=0} {$db +=$_.disksizerequired; $_.name + " - " + $_.disksizerequired/1024/1024} {Write-Host "`nTotal Storage (in MB) =" ("{0:n0}" -f ($db/1024/1024))}


Get-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name, @{Label ="Size in MB"; Expression = {$_.disksizerequired/1024/1024}}