Cannot connect to database master at SQL Server at server_name. The database might not exist, or the current user does not have permission to connect to it Error SharePoint 2016

Cannot connect to database master at SQL Server at server_name. The database might not exist, or the current user does not have permission to connect to

Error:

“Cannot connect to database master at SQL Server at server_name. The database might not exist, or the current user does not have permission to connect to it” 

cannot-connect-to-database-master-at-server_sharepoint2016

Solution:

Open the Windows Firewall with Advanced Services and add an inbound rule to allow traffic over port 1433.

amazon   amazonsp2016  amazonsp2016_2

Advertisements

Failed to create configuration database exception SharePoint 2016

Error :

There was an error while running Install Prerequisite (prerequisiteinstaller.exe)  “Failed to create configuration database. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.

psconfigsharepoint2016

Solution:

you may face this issue while installing manually instead of using the prerequisiteinstaller.exe

Uninstall WcfDataServices and then reinstalling the WcfDataServices using the prequisiteinstaller.exe automatically or using command with the appropriate parameter.

prerequisiteinstaller.exe /wcfdataservices56: WcfDataServices.exe location

Then delete two databases from SQL Server which are created by previous psconfiguration and run Products Configuration Wizard again, it will be successful.

amazon  amazonsp2016  amazonsp2016_2

Program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing SharePoint2016

This program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing from your computer.” error while running SharePoint Products Configuration Wizard.

api-ms-win-crt-heap-l1-1-0

*Missing update patches “Windows 10 Universal Runtime update” for Windows Server 2012 R2.

  • Installation of Windows Server 2012 R2 patch KB299926 is required so as to resolve this issue.

But  “The update is not applicable to your computer.” error came after that as below.

kb2919355

This is because Windows 10 Universal C Runtime KB2999226 is dependent on a Windows Server 2012 R2 Cumulative Update package in KB2919355.

Check windows updates, install patch KB2919355 and “The update is not applicable to your computer.”error will be resolved and after which there will be no error in installation of  the Windows 10 Universal C Runtime.

Have a look into my previous post Install Prerequisite (prerequisiteinstaller.exe) SharePoint 2016.

Unable to install Microsoft Information Protection and control Client 2.1 error SharePoint 2016

“The license state for the current server doesn’t match the farm’s license state”– SharePoint PSConfig Error

Recently I have involved in an interesting troubleshooting issue. There are many blog posts and TechNet discussions about this error. Thought that to post it here about my experience.

Here is the scenario. Customer has two Windows 2008 R2 Std machines (lets call it as srvsp1 & srvsp2) installed and configured with the following products.

  1. SharePoint Server 2010 Enterprise Edition
  2. Office Web Apps

Recently we have patched those two servers , for some troubleshooting one of the servers (srvsp2) was disconnected from the farm. After completing the installation while trying to add the server back to the farm by running the PSConfig we got the below error,

The license state for the current server doesn’t match the farm’s license state.
System.InvalidOperationException: The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm.

The license state for the current server doesn’t match the farm’s license state.
at Microsoft.SharePoint.Administration.SPFarm.Join()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Here are the troubleshooting steps.

# Step 1

Verify the configuration database has correct entries of all installed products. For that , we ran the following query against the “Objects” table of SharePoint configuration database.

Select * from Objects with (nolock) where properties like ‘%icrosoft.SharePoint.Administration.SPInstallState%’

From the result copy the “Properties” column value to notepad or any xml editor tool, in my case I have used Visual Studio.

2577.image_3AD92119

Values that we are interested the ones highlighted in the below screenshot. Same is given below.

beed1f75-c398-4447-aef1-e66e1f0df91e
d5595f62-449b-4061-b0b2-0cbad410bb51

4774.image_1834E29E

# Step 2

Once we get those GUIDs, next step is make sure that any difference in the actual Physical SharePoint server’s installed products and configuration database.

To do that, check the below registry location in both the SharePoint Servers (srvsp1 & srvsp2).

HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0WSSInstalledProducts

6837.image_75FCD717

{90140000-1014-0000-1000-0000000FF1CE} REG_SZ BEED1F75-C398-4447-AEF1-E66E1F0DF91E
{90140000-110D-0000-1000-0000000FF1CE} REG_SZ D5595F62-449B-4061-B0B2-0CBAD410BB51
{90140000-112D-0000-1000-0000000FF1CE} REG_SZ 926E4E17-087B-47D1-8BD7-91A394BC6196

Here we can clearly see that the physical box has 3 entries whereas the configuration database has only 2 of them.

More details of the GUIDs are given below.

BEED1F75-C398-4447-AEF1-E66E1F0DF91E is for “SharePoint Foundation 2010”,

D5595F62-449B-4061-B0B2-0CBAD410BB51 is for “SharePoint Server 2010 Enterprise”

926E4E17-087B-47D1-8BD7-91A394BC6196 is for “Office Web Companions 2010″ (Office Web Apps)

(Just FYI, for more information all different product SKUs and it’s GUIDs please refer this article http://msdn.microsoft.com/en-us/library/ff721969.aspx )

In our case, the Configuration database should have had 3 entries to match the registry in a normal farm. For some reason it was not updated with the office web apps production installation , it may caused by an installation issue.

Resolution:

Run the following Power Shell commandlet on any working server in the farm. In our case it was srvsp1, the reason we would need to run from this server is because the problem server – srvsp2 is still not in the farm.

Set-SPFarmConfig –InstalledProductsRefresh

This will pick the entries from the server and reset the entries in the Config DB. 

To double-check, you can run the same SQL query mentioned above and confirm the values.

Hope this will helpful while troubleshooting this specific issue related to SharePoint. There are different scenarios as well, eg: configuration database may have the values but it was not there in the physical server’s registry. To fix that you may end up with uninstall and install the product to update it correctly.