Health Analyzer does a great job warning you about possible problems on your platform, however it is extremely hard to stay on the good side (meaning it does not reward you with a red bar in Central Administration) without turning off a couple of rules.
I met with the Drives used for SQL databases are running out of free space message a few times and the other day reading the official documentation and feeling a bit confused and disappointed I decided to check out what this is about under the hood.
It happened once that i needed to provision a Sharepoint 2013 farm including MS SQL Server Reporting Services (SRSS). I had some issues – maybe you found this post ‘cos of that – which i would also share and give a hint on the solution.
Recently I tried to install SharePoint 2013 in my test environment based on the multiple servers for a three-tier farm scenario, where my SQL Server is on another machine and I got the following error during SharePoint 2013 Products Configuration Wizard:
Failed to create the configuration database
Exception: Microsoft.SharePoint.SPException: This SQL Server instance does not have the required “max degree of parallelism” setting of 1. Database provisioning operations will continue to fail if “max degree of parallelism” is not set 1 or the current account does not have permissions to change the setting. See documentation for details on manually changing the setting.
I encountered this during farm creation on the first SharePoint server installation.
Although my site did not contain so much information and data Sharepoint told me that i reached the Storage Quota limit had been given to the site ->
Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit. You must save your work to another location. Contact your administrator to change the quota limits for the Web site.
Of course the first step was to go to the “Recycle bin” to empty it. But after this procedure i got the same error. Ohh yes, the secondary Recycle bin for the Site collection – with Site admin right i was able to delet all the contects of that bin also.
But still got this rude error message. What’s up here?
Recently I’ve had to work a lot with SharePoint workflows. During the implementations I am faced a lot of limitations of the SharePoint 2007. There’s a lot of situations when you need to apply workarounds, otherwise you are not able to achieve the goal. I would like to show you one of these limitations and of course I will present the quick and easy solution as well.
So, there was a workflow step when I had to check whether a date field is empty or not. According to the result I wanted to define different actions. Unfortunately in the Designer was no option for that as you can see below.