How to resolve "The site address is available with modification." issue in SharePoint Online?

Scenario: 

While you are creating sites in SharePoint online tenant, you might have created a site with incorrect configuration and you may wanted to delete and recreate the site with same URL. During the recreation of the site, the requested URL may not be available for you. It will provide another URL with numbers in it.

Reason:

You may be deleted the previous site from "Active Sites" section and also deleted from "Deleted Sites" section. But the site will be still in "Redirect" status. 

Solution:

You are required to delete the site using PowerShell with tenant admin privilege.

1. Access the tenant URL with your tenant admin credential in "SharePoint Online Management Shell"

    Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

2. Check if your site is displayed in the list by executing the below command

    Get-SPOSite -Template REDIRECTSITE#0

3. Execute the below command to delete the site.

    Remove-SPOSite -Identity https://<tenant>.sharepoint.com/sites/<sitename>

Now the URL will be available for you to create in the same name.

How to export the ULS log based on Correlation Id?

Scenario:
Sometime we may need to export check the actual error for the Correlation Id which we got in the browser. At that time, we can use the PowerShell command to get all the error details from ULS log which are related to the specific correlation id.


How:
Run the below command in the "PowerShell for SharePoint" window (Run as Administrator".


merge-splogfile -correlation "<Correlation Id>" -path .\desktop\<filename>.csv -starttime "<Time in server time format>" -endtime "<Time in server time format>"


Example:
merge-splogfile -correlation "e2677d9d-eedf-501a-7c9b-a41fc989149d" -path .\desktop\filename5.csv -starttime "5/18/2016 10:43:00 AM" -endtime "5/18/2016 10:45:00 AM"

Process that hosts the writer with name OSearch15 VSS Writer and ID {0ff1ce15-0201-0000-0000-000000000000} does not run under a user with sufficient access rights.

Issue:

Process that hosts the writer with name OSearch15 VSS Writer and ID {0ff1ce15-0201-0000-0000-000000000000} does not run under a user with sufficient access rights.

Reason:
Your "Search Host Controller" may not be started as you expected. Also it will struck to start in the "Services.msc" console.
The reason is the account which is used for Search services does not have access rights to read the specific registry key.

Solution:
1. Make sure that you have added your "Serice Account" in the "Administrator group of SP server.
2. Open "Regedit" in the "Run" window
3. Go to "HKLM\System\CurrentControlSet\Services\VSS\VssAccessControl"
4. Do right click and add one more "DWORD" value for your search service as depicted below and set the value as "1"

5. Also you need to set the "Read" permission to the administrator group as depicted below

6. Now go and check your "Search Host Controller" service and it works fine.

That's it....

Unable to edit SharePoint 2013 web part properties

Issue:
If you are trying to edit the web part properties, you will not have such option to edit the properties.

Reason:
This is a known issue in IE 11.

Solution:
Try to edit the page in Google chrome.

cacheHostInfo is null

Error:

An attempt to start/stop instance  of service Distributed Cache on server did not succeed.  Re-run the action via UI or command line on the specified server. Additional information is below.

cacheHostInfo is null

Reason:
If you are trying to activate the Distributed cache service in Central admin, you will get the "cacheHostInfo is null" error. This is because the Distributed cache is not able to map with the configured "Cache" location.

Solution:

1. Go to "Caonfig Appfabric" window through "Start" menu
2. Check the server name which is configured in the window as I depicted in the below screenshot

3. Get the server name and replace the server name in the below script

$DC = Get-SPServiceInstance | where {$_.TypeName -eq “Distributed Cache”}
$DC
$DC[0].Provision(“\\Servername“)

4. Execute the script in the SharePoint 2013 Powershell window

Note: 
If you are having more than one distributed cache service, you need to replace the above array value for the disabled distributed cache. In my case, i have only one cache service.

That's it...

Error: The tool was unable to install Application Server Role, Web Server (IIS) Role

Error: 
The tool was unable to install Application Server Role, Web Server (IIS) Role

Reason:
You will get this error, if you are trying to install "prerequisiteinstaller.exe" for SharePoint server 2013 in Windows server 2012. Because, the installer is unable to find the required file.

Solution:
If you are getting this error, you can easily find the actual error in the "log" file via the installer. The log file may say,

So what is the actual solution?

• You have to go to "C:\Windows\system32\" in the server that you are install the prerequisites
• Copy and paste the "ServerManager.exe" in the same folder
• Rename the copy of ServerManager.exe as ServerManagerCmd.exe
• Now try to run the prerequisiteinstaller.exe file. You will not get the above said error. 

Thats it...

Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation

Error:
Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation

(Or)

SharePoint 2013 SP1 failed to install.

(Or)

Getting error when you are trying to create a new web application in central admin

Reason:
You will get this error, after you tried to install "SharePoint server 2013 Service Pack 1 (officeserversp2013-kb2880552-fullfile-x64-en-us.exe)

The reason is there would not be enough space in the "C" drive.

Solution:
Keep minimum of 3 GB in C drive and install the SharePoint server 2013 SP1 from http://www.microsoft.com/en-in/download/details.aspx?id=42544

Your Service pack will continue to install now without any issues. Also you will not get the above mentioned issues.

That's it...