So many time it’s useful to color a cell in a table on SharePoint pages. Out of the box we don’t have a solution to impress our visitors. Although we have the table with numbers inside but coloring the cells regarding to their value it’s more informative.
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.
You get the following error during SharePoint 2013 Products Configuration Wizard on the Specify Configuration Database Settings page:
Cannot connect to database master at sql server <Servername>. The database might not exist, or the current user does not have permission to connect to it.
Your first move should be the following: Try it again, but this time mark the time between you press Next > and when the error message pops up.
Based on this:
- if its more than a few seconds, you have network connectivity issue or SQL server configuration problem (start from no 1)
- if it pops up almost instantly, you have permission problems on the SQL server instance (See no. 10 and 9)