How to update Warning Site Count and Maximum Site Count of SPContentDatabase

This seems pretty simple as you can just set the properties of SPContentDatabase and you are good to go. However, this didn’t work atleast in my case.

Unable to remove SharePoint server from Farm – “cacheHostInfo is null”

I was creating a new farm from an existing farm due to project requirements, but I came across a situation wherein I was not able to remove the server from the farm using the SharePoint 2013 UI(server was already removed using the command or you can remove it by using configuration wizard on the server to be removed).

So, the error message which I was getting when I was trying to remove the server from the UI was “cacheHostInfo is null“.

Below is the solution to this problem which I followed and it worked.

MySite – EnsureMySiteUrl: PersonalSiteUrl of page is null

Mysites configuration is pretty simple which has the basic pre-requisites:

1. User Profile Service must be running
2. Mysite host site collection should be created
3. Mysite managed path for users’ site should be created
4. mysites should be configured
5. mysite web application should have self site creation on.
6. Also, the end users who want to create mysites should have permission policy level of “Create Subsites – Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.“

SharePoint : Delete “Scheduling Start Date” and “Scheduling End Date” columns using PowerShell

In general, we can delete the columns using UI from SharePoint pretty easily. But some columns are not allowed to be deleted using UI but are allowed to be deleted using PowerShell. But there are some columns which are not deleted from PowerShell as well without some tweaks.

MOSS 2007: Get Admin Content Database Name

Recently, I ran into trouble in which I couldn’t find a simple way to find the admin database name in MOSS 2007 as its not displayed in Central Admin and there is no PowerShell supported in MOSS 2007 so we have to deal with stsadm tool.

SharePoint 2013 : Orphaned Content Database Removal

Orphaned Content Database – By orphaned content database I mean that the content database is not associated to any web application and is not visible by using Get-SPContentDatabase command.

So, what is the need of removing the Orphaned Database. Recently, I accidentally removed a database and added it back but somehow it was not adding back and displaying the message that database already exist when I was trying to add the database using the UI or using PowerShell.

So, the way to see is the database present in the farm is to run the following command:

Get-SPDatabase | Select  Name, Id

It would display the list of all the databases associated with any service application or web application or any other database present/associated with SharePoint. In this list the orphaned content database would also be listed.

In order to remove just get the database and execute delete method. It would only remove the association with  the farm.

$db = Get-SPDatabase -Identity "<GUID>"

$db.Delete()

Now again, if you run the following command the orphaned content database would not be present anymore.

Get-SPDatabase | Select  Name, Id

I couldn’t find any blog/article anywhere related to this, hope it might help someone.

 

Current Navigation Query String Repeating Issue in SharePoint 2013

There is an issue in SharePoint 2013 site in the version before SP1 that if you enter a URL with query string it keeps on adding the query string multiple times whenever any user clicks on the URL or try to save it.

SharePoint Configuration Exception – An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.

Recently, I encountered a problem while installing SharePoint 2013. I just installed the SharePoint 2013 and when I run configuration wizard the following error was thrown just after the 3rd step of creation of configuration database.

SharePoint CU Installation – An error occurred while running detection

Sometimes when we try to install patches in SharePoint environment we face the error stating

An error occurred while running detection.

This is due to a reason that SharePoint couldn’t recognize whether the version of the patch that is going  to be installed is valid for your environment or not.

SharePoint HRESULT: 0x80131904

Description:

This is quite annoying message from SharePoint. This error would be encountered whenever you want to make any changes or try to add list item, create a site, basically adding anything into SharePoint.