update error 912 with more info and steps

Author: PiJoCoder

docs/relational-databases/errors-events/mssqlserver-912-database-engine-error.md

@@ -2,7 +2,7 @@
 title: "MSSQLSERVER_912"
 description: The database script level could not be upgraded to the latest required by the server.
 ms.custom: ""
-ms.date: "08/16/2021"
+ms.date: "10/25/2022"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: supportability
@@ -34,18 +34,32 @@ When [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is upgraded or a
 
 If the upgrade process encounters script-level upgrade errors (Error 912), other errors may be raised. For example, these errors may accompany error 912 and help further explain the failure:
 
-`Error: 1101, Severity: 17, State: 1.` </br>
-`Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.`
+```output
+Error: 1101, Severity: 17, State: 1.
+Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
 
-`Error: 912, Severity: 21, State: 2.` </br>
-`Script level upgrade for database 'master' failed because upgrade step 'xxx.sql' encountered error <Error Number>, state <Error State>, severity <Error Severity>. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.`
+Error: 912, Severity: 21, State: 2.
+Script level upgrade for database 'master' failed because upgrade step 'xxx.sql' encountered error <Error Number>, state <Error State>, severity <Error Severity>. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
 
-`Error: 3417, Severity: 21, State: 3.` </br>
-`Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.`
+Error: 3417, Severity: 21, State: 3.
+Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
+```
+
+Commonly when the installation process fails, the user may see the following error in the GUI, assuming the installation is done manually using the Wizard. Keep in mind that this error may be raised with a wide variety of installation issues. But in all cases it directs you to check the SQL Server error log for more information.
+
+```output
+Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
+```
+
+:::image type="content" source="../media/upgrade-errors-check-errorlog.png" alt-text="upgrade failure in the GUI":::
 
 ## User action  
 
-To find the cause of the issue, you need to look at the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [error log](../../tools/configuration-manager/viewing-the-sql-server-error-log.md). Examine the log for errors that occurred before error 912 and troubleshoot the error referenced in the messaging of Error 912. In some cases, as part of the process, you may need to start the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service with [trace flag 902](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf902).  This step allows the SQL service to skip the upgrade scripts execution during startup so that you get a chance to investigate and fix the issue. Be sure to remove the trace flag once you have resolved the issue so the setup process can restart the upgrade script execution.
+To find the cause of the issue, follow these steps:
+1. Locate and open the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [Errorlog](../../tools/configuration-manager/viewing-the-sql-server-error-log.md). 
+1. Examine the log for errors that occurred immediately before error 912 and focus on troubleshooting the error referenced in the messaging of Error 912. 
+1. In some cases, as part of the process, you may need to start the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service with [trace flag 902](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf902) (see steps below). Starting the service with T902 allows the service to skip execution of the upgrade scripts during startup. That way, you get a chance to investigate and fix the underlying issue.
+1. Be sure to remove the trace flag once you have resolved the issue so the setup process can restart the upgrade script execution phase.
 
 ### Steps to start [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] with trace flag 902