This post describes how to add Chapters to break up YouTube videos into sections. To add chapters to a YouTube video, you simply need to edit the video and add timestamps to the video description like this: 0:00 Introduction 0:27 Chapter 1 1:13 Chapter 2 3:30 End credits Once added, simple save the video, then view it on YouTube to see the chapter markers in the progress scrubbing bar and the chapter name in the video control area. As of 10th February 2021, this feature now also works for embedded YouTube videos.

This post describes how to fix the error: MSX enlist failed for JobServer An exception occurred while executing a Transact-SQL statement or batch. The enlist operation failed (reason: SQLServerAgent Error: The EXECUTE permission was denied on the object 'sp_enlist_tsx', database 'msdb', schema 'dbo'. [SQLSTATE 42000] (Error 229).) (Microsoft SQL Server, Error: 22026) Cause This error can occur when the target server machine account does not have sufficient privileges on the master server. Resolution Check the server roles of the target server machine account on the master server. On my test environment, I resolved the issue by assigning the account the sysadmin server role: Related Posts The enlist operation failed (SQLServerAgent: Unable to connect to MSX) (Error: 22026) The target server cannot establish an encrypted connection to the master server

This post describes how to fix the error: MSX enlist failed for JobServer. An exception occurred while executing a Transact-SQL statement or batch. The enlist operation failed (reason: SQLServerAgentError: The target server cannot establish an encrypted connection to the master server) (Microsoft SQL Server, Error: 22026) Cause This error can occur if the MsxEncrypyChannelOptions registry subkey is not set correctly on the target server. Resolution Go to the registry on the target server and modify the value of the registry subkey. The possible values are defined here: https://docs.microsoft.com/en-us/sql/ssms/agent/set-encryption-options-on-target-servers?view=sql-server-ver15 For my test environment, I set it to 0, which disables the encryption. Related Posts The enlist operation failed (SQLServerAgent: Unable to connect to MSX) (Error: 22026) The EXECUTE permission was denied on the object 'sp_enlist_tsx', database 'msdb',

This post describes how to fix the error: MSX enlist failed for JobServer. An exception occurred while executing a Transact-SQL statement or batch. The enlist operation failed (reason SQLServerAgent Error: Unable to connect to MSX.) (Microsoft SQL Server, Error: 22026) Cause This error can occur when setting up Multi Server Administration > Make this a Master...  Check the log file on the master server (by default located here: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log) 2020-07-21 11:59:19.82 Logon       Login failed for user 'TEST2019\SQL2017-2K19-1$'. Reason: Could not find a login matching the name provided. [CLIENT: 192.168.131.227] The target server machine account (in this case 'TEST2019\SQL2017-2K19-1$') does not have permission to login on the master server. Resolution This error can be resolved by adding the target server machine account as a login on the mas

This post describes how to fix the error: Database cannot be opened. It is in the middle of a restore. (Microsoft SQL Server, Error: 927) Cause This error can occur when you try to configure mirroring using the Configure Database Mirroring Security Wizard. The endpoints are created successfully: However, when you try to Start Mirroring: The error occurs. Resolution To resolve the error, I had to start mirroring in SQL directly. I set the partner to the Principal network address on the mirror SQL instance: ALTER DATABASE AdventureWorksLT2019  SET PARTNER = 'TCP://SQL2019-2K19-1.test2019.net:5022' I then set the partner to the Mirror network address on the principal SQL instance: ALTER DATABASE   AdventureWorksLT2019   SET PARTNER = 'TCP://SQL2019-2K19-1.test2019.net:5023' And set the witness to the Witness network address on the principal SQL instance: ALTER DATABASE   AdventureWorksLT2019

This post describes how to fix the error: An error occurred while starting mirroring. The server network address can not be reached or does not exist. (Microsoft SQL Server, Error: 1418) Cause This error appears to be related to network connectivity however the cause in this case was that I had entered incorrect accounts in the Service Accounts step of the Configure Database Mirroring Security Wizard. I verified this by checking the SQL ERRORLOG (by default located here: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log).  This contained the following: 2020-07-03 10:39:31.76 Logon       Database Mirroring login attempt by user 'TEST2019\SQL2019-2K19-1$.' failed with error: 'Connection handshake failed. The login 'NT Service\MSSQL$MIRRORINSTANCE' does not have CONNECT permission on the endpoint. State 84.'. Resolution To resolve the issue, first delete the previously created endpoints

This post describes how to fix the error: An error occurred while starting mirroring. Database is not configured for database mirroring. (Microsoft SQL Server, Error: 1416) Cause This error can occur if RESTORE WITH NORECOVERY was not used when restoring either the database or the transaction log on the mirror SQL instance. Resolution When you restore the database, ensure RESTORE WITH NORECOVERY is selected: When you restore the transaction log, ensure RESTORE WITH NORECOVERY is selected: The database on the instance you want to mirror with should be in a (Restoring...) state: Related Posts - The client and server cannot communicate, because they do not possess a common algorithm -  Database cannot be opened. It is in the middle of a restore. (Error 927) -  Cannot alter the role 'db_owner', because it does not exist or you do not have permission. - The client and server cannot communicate, because they do not possess a common algorithm

This post describes how to fix the error: An error occurred whilst starting mirroring. Database might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. (Microsoft SQL Server, Error: 1475) Cause This error can occur when you attempt to start mirroring but the database you are trying to mirror from (the principal database) has not had a Transaction Log backup. Resolution On the database that you wish to mirror (the principal database), perform a Transaction Log backup: Then restore this backup on the mirror database, ensuring you use  RESTORE WITH NORECOVERY.  Failure to do this will result in the error: Database is not configured for database mirroring. (Microsoft SQL Server, Error: 1416)