My virtual machines are my playground and I do install/uninstall a lot of stuff there (of course related to SQL Server learning). When things break, I get to learn something new. In this blog we would talk about how to troubleshoot and fix Could not load file or assembly error. This particular error can come in many flavors. Here is another form of the same error.
SQL SERVER – Fix Error: Invalid object name STRING_SPLIT
Just the other day one of the readers sent me following email after reading my earlier blog post: STRING_SPLIT Function Performance Comparison. He really liked the new feature of SQL Server 2016 and decided to start using this new feature. However, as soon as he started to use this feature, he received following error. He was very much confused why he was not able to use the STRING_SPLIT function even though he had SQL Server 2016.
SQL SERVER – Installation Error – Unable to Open Windows Installer File – 2147286960
SQL installation and parching are the processes which every DBA has to do. Some smart DBAs do this via script and some go with a manual approach. When it fails, it is fun to debug it because you have to take help from internet to find possible causes and solution. In this blog, we would learn about how to fix error Unable to open Windows Installer file -2147286960.
SQL SERVER – Service Pack Failure: MissingRegistryKeyException. The Registry Key is Missing
One of my blog readers contacted me and informed that he is getting the same error as mentioned in below blog SQL SERVER – Service Pack Failure: MissingRegistryKeyException. Note that it had the same error message, but that did not help him here. In this blog, we would learn how to fix MissingRegistryKeyException while installing SQL Server service pack. Let us fix the error registry key is missing.Â
SQL SERVER – SharePoint not Working After Failover to Another Node
Anything that can go wrong will go wrong while Murphy is out of town. While I was onsite to help a client, one such issue had cropped up in their SharePoint environment where SQL Server was used as backend and was a part of Windows failover cluster. When SQL Server was failed over from Active to the Passive node, users were not able to connect to SharePoint site and they were not able to open any SharePoint page. Since it was critical for their business, I got engaged to provide suggestions.
SQL SERVER – FIX – Error 1402 – Could not Open Key: UNKNOWN\Components – System Error 5 (Another Solution)
I encountered this error while installing KB3045311. In fact, you might get such errors when installing any patch for one of my customers. The error was the very popular system error 5.Â
SQL SERVER – FIX: Unable to Create Distribution Database on a UNC Share – Configure Distribution
Whenever we try to use Configure Distribution option in SSMS in a SQL Server instance which is configured on a UNC Path, the wizard will not allow us to configure the Distribution database and we will get the below error: