My first gMSA test: SQL Service was not started automatically after server reboot, even with automatic startup set. Here is what the event log showed.
SQL SERVER – Error: 18456, State 149 – Login-based Server Access Validation Failed With an Infrastructure Error. Login Lacks Connect Endpoint Permission
Connecting to the DAC with SQLCMD, I got Error 18456, State 149: Login lacks connect endpoint permission. Here is what the ERRORLOG showed and how to fix it.
Fix Error 3637: Backup Fails on a DAC Connection
To fix error 3637, find out why your backup runs on a dedicated administrator connection. This post reproduces the message with sqlcmd and its -A switch, shows the same backup working on a normal connection, and lists where a DAC hides in scripts and scheduled tasks.
ISSERVER Assembly Upgrade Error: Cannot Drop the Assembly (Msg 15151 and 6528)
An ISSERVER assembly error during a SQL Server upgrade needs the surrounding SSISDB messages before you choose a repair. The tests here trigger both errors in a throwaway database, show how they differ and run the catalog checks safely when SSISDB is missing or unreadable.
Error 18210: New Parallel Operation Cannot Be Started During Backups
Error 18210 showed up in a client’s ERRORLOG beside a message that a new parallel operation could not be started. The client’s third-party tool backed up more than 1,000 databases at the same time. Staggering the backups stopped the error.
SQL SERVER – Cannot Drop the Assembly ‘ISSERVER’, Because it Does not Exist or You do not Have Permission
An upgrade could not start SQL Server: Cannot drop the assembly ‘ISSERVER’, because it does not exist or you do not have permission. Here is another way to fix it.
Visual Studio – FIX: The ‘SqlStudio Profile Package’ Package Did Not Load Correctly
Launching Visual Studio on my VM failed with: The ‘SqlStudio Profile Package’ package did not load correctly. I gathered a list of fixes that can solve it.