My client contacted me for a quick assistance in a setup trouble. She informed it’s a brand-new install and failing at the end. She was installing SQL Server 2016 on Windows Server 2016. Let us learn about how to fix Installation Error.
To fix something, it should be broken first. I keep playing with my lab and eventually end up breaking stuff. This time, while patching my own lab environment with latest service pack, I ran into below error about MissingRegistryKeyException.
SQL SERVER – Startup Error: 17190, Severity: 16 – Initializing the FallBack Certificate Failed with Error Code: 1, State: 20
I must confess that consulting has taught me much more than what I have learned in my regular job. Freelancing comes with advantages and disadvantages. For me, I am looking at advantages and I am happy with my decision. In this blog post we will learn about error related to FallBack Certificate.
It is not a normal behavior of SQL Server to generate minidumps. It is like a stress signal in SQL. When there is something “unexpected”, SQL Server kills the SPID and generates a dump. There are situations where SQL threads are not yielding (“Non-yielding Scheduler”, “Non-yielding IOCP Listener” or “Non-yielding Resource Monitor”) and there would be data needed to diagnose the problem later, so a dump is generated. These dumps are in the folder which has ERROLROG files. They can be triggered manually also using SQLDumper.exe for SQLDump.
As you might know, SQLCMD is a command line utility which can be used to connect to SQL Server and run scripts/queries. While trying to run SQLCMD, I ran into below SQLCMD error.
SQL SERVER- Msg 22004, Level 16 – xp_readerrorlog – Failed to Open Loopback Connection. Please See Event Log for More Information
Many DBAs use sp_readerrorlog or xp_readerrorlog to read ERRORLOG files in SQL Server. SQL SERVER – Where is ERRORLOG? Various Ways to Find ERRORLOG Location