The SQL database may not be running correctly You applied a Hotfix or Service Pack and did not reboot.
The Firewall is blocking the communication The Share Point Installation Account does not have the required permissions to the SQL Server database. Additional exception information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
However, the team build fails when trying to build these projects.
This is the world of mystery errors you find in Share Point Server, any version, and until this very moment several of the solutions are not always from Microsoft.Now we breathe some air of relief with Share Point 2010 configurations made easy in one simple Wizard screen. I figured rather than looking for the problem, yank it off and reinstall after a proper backup. So, I fired up the Share Point 2010 Products Configuration Wizard of Oz, and got this along the way, just the very first steps really: Familiar it seems. SOLUTION: Create an alias on the server for the SQL client. SQL Alias is something which you may have to create when you’re moving your database servers around. And that is after you have battled the infamous install check which returned like 80 language packs problem, 120 missing locally problem and the rest of the evil minions from Share Pain hell. When done, re-run the Configuration Wizard again, and you should be fine. We can only hope 20 years up to the line from now that Share Point will stop giving us hair-tearing problems for no apparent known reason. This entry is for those environments with the June 2012 CU for Share Point 2012.When run Sharepoint 2013 configuration wizard, I get an error at step 3-Failed to create the configuration database: An exception of type System. Additional exception information: Value cannot be null.In this scribble, I am going to reveal 5 mysterious errors in Share Point and how to go about resolving them. Do this if you have a multilingual environment where you have to present the sites in the different user’s languages.Subsequently, this can be the first of a series of topics among error resolutions in all versions of Share Point, specifically 2010. So, here we were trying to expand the Share Point 2010 farm a bit.
Note, we've tried adding the registry setting in various places but none have helped.