Merge pull request #18070 from cobibi/sql-docs-pr-cobibi2

Add 9 sqlserver errors-events articles on 12/10

Author: ShannonLeavitt

docs/relational-databases/errors-events/database-engine-events-and-errors.md

@@ -912,7 +912,7 @@ ORDER BY message_id
 |    1779    |    16    |    No    |    Table '%.*ls' already has a primary key defined on it.    |
 |    1781    |    16    |    No    |    Column already has a DEFAULT bound to it.    |
 |    1784    |    16    |    No    |    Cannot create the foreign key '%.*ls' because the referenced column '%.*ls.%.*ls' is a non-persisted computed column.    |
-|    1785    |    16    |    No    |    Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.    |
+|    [1785](mssqlserver-1785-database-engine-error.md)    |    16    |    No    |    Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.    |
 |    1786    |    16    |    No    |    Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with cascading referential integrity constraints.    |
 |    1787    |    16    |    No    |    Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIGGER defined on it.    |
 |    1788    |    16    |    No    |    Cascading foreign key '%.*ls' cannot be created where the referencing column '%.*ls.%.*ls' is an identity column.    |
@@ -1842,8 +1842,8 @@ ORDER BY message_id
 |    3985    |    16    |    No    |    An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.    |
 |    3986    |    19    |    No    |    The transaction timestamps ran out. Restart the server.    |
 |    3987    |    10    |    No    |    SNAPSHOT ISOLATION is always enabled in this database.    |
-|    3988    |    16    |    No    |    New transaction is not allowed because there are other threads running in the session.    |
-|    3989    |    16    |    No    |    New request is not allowed to start because it should come with valid transaction descriptor.    |
+|    [3988](mssqlserver-3988-database-engine-error.md)    |    16    |    No    |    New transaction is not allowed because there are other threads running in the session.    |
+|    [3989](mssqlserver-3989-database-engine-error.md)   |    16    |    No    |    New request is not allowed to start because it should come with valid transaction descriptor.    |
 |    3990    |    16    |    No    |    Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.    |
 |    3991    |    16    |    No    |    The context transaction which was active before entering user defined routine, trigger or aggregate "%.*ls" has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.    |
 |    3992    |    16    |    No    |    Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate "%.*ls". This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.    |
@@ -2903,7 +2903,7 @@ ORDER BY message_id
 |    6519    |    16    |    No    |    Type '%.*ls' is not yet supported for CLR operations.    |
 |    6520    |    16    |    No    |    A .NET Framework error occurred during statement execution.    |
 |    6521    |    16    |    No    |    A .NET Framework error occurred during statement execution: %.*ls.    |
-|    6522    |    16    |    No    |    A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls.    |
+|    [6522](mssqlserver-6522-database-engine-error.md)    |    16    |    No    |    A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls.    |
 |    6523    |    16    |    No    |    Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is static.    |
 |    6524    |    16    |    No    |    Cannot use computed column in the result table of a streaming user-defined function (column '%.*ls').    |
 |    6525    |    16    |    No    |    Cannot use '%s' constraint in the result table of a streaming user-defined function.    |
@@ -2983,7 +2983,7 @@ ORDER BY message_id
 |    6599    |    16    |    No    |    Found an empty native serialization class '%.*ls'. Empty native serialization classes are not allowed.    |
 |    6600    |    16    |    No    |    XML error: %.*ls    |
 |    6601    |    10    |    No    |    The XML parse error 0x%x occurred on line number %d, near the XML text "%.*ls".    |
-|    6602    |    16    |    No    |    The error description is '%.*ls'.    |
+|    [6602](mssqlserver-6602-database-engine-error.md)    |    16    |    No    |    The error description is '%.*ls'.    |
 |    6603    |    16    |    No    |    XML parsing error: %.*ls    |
 |    6605    |    16    |    No    |    %.*ls: Failed to obtain an IPersistStream interface on the XML text.    |
 |    6607    |    16    |    No    |    %.*ls: The value supplied for parameter number %d is invalid.    |
@@ -6275,7 +6275,7 @@ ORDER BY message_id
 |    15397    |    16    |    No    |    The %S_MSG is not protected by a password. A decryption password cannot be used for this operation.    |
 |    15398    |    11    |    No    |    Only objects in the master database owned by dbo can have the startup setting changed.    |
 |    15399    |    11    |    No    |    Could not change startup option because this option is restricted to objects that have no parameters.    |
-|    15401    |    11    |    No    |    Windows NT user or group '%s' not found. Check the name again.    |
+|    [15401](mssqlserver-15401-database-engine-error.md)    |    11    |    No    |    Windows NT user or group '%s' not found. Check the name again.    |
 |    15402    |    11    |    No    |    '%s' is not a fixed server role.    |
 |    15403    |    16    |    No    |    The server principal "%.*ls" does not exist, does not have server access, or you do not have permission.    |
 |    [15404](mssqlserver-15404-database-engine-error.md)    |    16    |    No    |    Could not obtain information about Windows NT group/user '%ls', error code %#lx.    |
@@ -6692,7 +6692,7 @@ ORDER BY message_id
 |    [17887](mssqlserver-17887-database-engine-error.md)    |    10    |    Yes    |    IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.    |
 |    17888    |    10    |    Yes    |    All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.    |
 |    17889    |    16    |    Yes    |    A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls    |
-|    17890    |    10    |    Yes    |    A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.    |
+|    [17890](mssqlserver-17890-database-engine-error.md)    |    10    |    Yes    |    A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.    |
 |    17891    |    10    |    Yes    |    Resource Monitor (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Memory freed: %I64d KB. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.    |
 |    [17892](mssqlserver-17892-database-engine-error.md)    |    14    |    Yes    |    Logon failed for login '%.*ls' due to trigger execution.%.*ls    |
 |    17894    |    10    |    Yes    |    Dispatcher (0x%lx) from dispatcher pool '%.*ls' Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.    |
@@ -6817,8 +6817,8 @@ ORDER BY message_id
 |    18469    |    10    |    No    |    [CLIENT: %.*hs]    |
 |    18470    |    14    |    Yes    |    Login failed for user '%.*ls'. Reason: The account is disabled.%.*ls    |
 |    18471    |    14    |    No    |    The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls    |
-|    18482    |    16    |    Yes    |    Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.    |
-|    18483    |    16    |    Yes    |    Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls.    |
+|    [18482](mssqlserver-18482-database-engine-error.md)    |    16    |    Yes    |    Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.    |
+|    [18483](mssqlserver-18483-database-engine-error.md)    |    16    |    Yes    |    Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls.    |
 |    18485    |    16    |    Yes    |    Could not connect to server '%.*ls' because it is not configured to accept remote logins. Use the remote access configuration option to allow remote logins.%.*ls    |
 |    18486    |    14    |    Yes    |    Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls    |
 |    18487    |    14    |    Yes    |    Login failed for user '%.*ls'. Reason: The password of the account has expired.%.*ls    |

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

@@ -0,0 +1,78 @@
+---
+description: "MSSQLSERVER_15401"
+title: MSSQLSERVER_15401
+ms.custom: ""
+ms.date: 10/27/2020
+ms.prod: sql
+ms.reviewer: ramakoni1, pijocoder, suresh-kandoth, vencher, tejasaks, docast
+ms.technology: supportability
+ms.topic: "language-reference"
+helpviewer_keywords: 
+  - "15401 (Database Engine error)"
+ms.assetid: 
+author: suresh-kandoth
+ms.author: ramakoni
+---
+# MSSQLSERVER_15401
+ [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+
+## Details
+
+|Attribute|Value|
+|---|---|
+|Product Name|SQL Server|
+|Event ID|15401|
+|Event Source|MSSQLSERVER|
+|Component|SQLEngine|
+|Symbolic Name|SEC_INVALIDLOGINORGROUP|
+|Message Text|Windows NT user or group '%s' not found. Check the name again.|
+||
+
+## Explanation
+
+This error occurs when [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is unable to create a login based on Windows principal (such as a domain user or a Windows domain group). An error message like the following is reported to the user
+
+> Error 15401: Windows NT user or group '%s' not found. Check the name again.
+
+## Cause
+
+The error can occur because of any of the following reasons:
+
+- The login does not exist in the active directory.
+- The domain controller is unavailable.
+- You are not using BUILTIN as the domain name when adding a local account.
+- Name resolution issues.
+
+## User action
+
+Review the following sections for actions you can take for each of the different causes mentioned above.
+
+### Verify the login you are trying to add
+
+1. Verify that the Windows login still exists in the domain. Your network administrator may have removed the Windows login for specific reasons, and you may not be able to grant that login access to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
+1. Verify that you are spelling the domain and login name correctly and that you are using the following format: `Domain\User`
+1. If the login exists, and it is correct, and you still receive the error, continue with the following sections in this article.
+
+### Verify if the domain controller is available
+
+You might receive error 15401 when the domain controller for the domain where the login resides (the same or a different domain) is not available for some reason.
+
+If the login is in a different domain than the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], verify that the correct trusts exist between the domains.
+
+Verify that the domain controller of the login is accessible by using the ping command from the computer that is running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Check both the IP address and the name of the domain controller.
+
+### Verify the domain name for local accounts
+
+Local (non-domain) accounts require special handling. If you are trying to add a local account from the local computer that is running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], ensure you are using BUILTIN as the domain name.
+
+### Check for name resolution issues
+
+If you have problems resolving the name of a computer that is involved in adding the login or group, you might receive error 15401.
+
+Verify that your name resolution mechanism (such as, WINS, DNS, HOSTS, or LMHOSTS) is configured correctly.
+
+## See Also
+
+- [Test a channel between the local computer and its domain](/powershell/module/microsoft.powershell.management/test-computersecurechannel#example-1--test-a-channel-between-the-local-computer-and-its-domain)
+- [LogonSessions v1.4](/sysinternals/downloads/logonsessions)
+- [sp_change_users_login (Transact-SQL)](/sql/relational-databases/system-stored-procedures/sp-change-users-login-transact-sql)

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

@@ -0,0 +1,78 @@
+---
+description: "MSSQLSERVER_1785"
+title: MSSQLSERVER_1785
+ms.custom: ""
+ms.date: 10/27/2020
+ms.prod: sql
+ms.reviewer: ramakoni1, pijocoder, suresh-kandoth, vencher, tejasaks, docast
+ms.technology: supportability
+ms.topic: "language-reference"
+helpviewer_keywords: 
+  - "1785 (Database Engine error)"
+ms.assetid: 
+author: suresh-kandoth
+ms.author: ramakoni
+---
+# MSSQLSERVER_1785
+ [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+
+## Details
+
+|Attribute|Value|
+|---|---|
+|Product Name|SQL Server|
+|Event ID|1785|
+|Event Source|MSSQLSERVER|
+|Component|SQLEngine|
+|Symbolic Name|CRTFKINVTOPO|
+|Message Text|Introducing FOREIGN KEY constraint '%.ls' on table '%.ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.|
+||
+
+## Explanation
+
+You receive this error message because in SQL Server, a table cannot appear more than one time in a list of all the cascading referential actions that are started by either a `DELETE` or an `UPDATE` statement. The tree of cascading referential actions must only have one path to a particular table on the cascading referential actions tree.
+
+An error message like the following is reported to the user:
+
+> Server: Msg 1785, Level 16, State 1, Line 1 Introducing FOREIGN KEY constraint 'fk_two' on table 'table2' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. Server: Msg 1750, Level 16, State 1, Line 1 Could not create constraint. See previous errors
+
+## User action
+
+To resolve this problem, create a foreign key that will create a single path to a table in a list of cascading referential actions.
+
+You can enforce referential integrity in several ways. Declarative Referential Integrity (DRI) is the most basic way, but it is also the least flexible one. If you need more flexibility, but you still want a high degree of integrity, you can use triggers instead.
+
+## More information
+
+The following sample code is an example of a FOREIGN KEY creation attempt that generates the error message:
+
+```sql
+USE tempdb
+GO
+
+CREATE TABLE table1 (user_ID INTEGER NOT NULL PRIMARY KEY, user_name
+CHAR(50) NOT NULL)
+GO
+
+CREATE TABLE table2 (author_ID INTEGER NOT NULL PRIMARY KEY, author_name
+CHAR(50) NOT NULL, lastModifiedBy INTEGER NOT NULL, addedby INTEGER NOT NULL)
+GO
+
+ALTER TABLE table2 ADD CONSTRAINT fk_one FOREIGN KEY (lastModifiedby)
+REFERENCES table1 (user_ID) ON DELETE CASCADE ON UPDATE cascade
+GO
+
+ALTER TABLE table2 ADD CONSTRAINT fk_two FOREIGN KEY (addedby)
+REFERENCES table1(user_ID) ON DELETE NO ACTION ON UPDATE cascade
+GO
+--this fails with the error because it provides a second cascading path to table2.
+
+ALTER TABLE table2 ADD CONSTRAINT fk_two FOREIGN KEY (addedby)
+REFERENCES table1 (user_ID) ON DELETE NO ACTION ON UPDATE NO ACTION
+GO
+-- this works.
+```
+
+### See Also
+
+[Cascading Referential Integrity](/sql/relational-databases/tables/primary-and-foreign-key-constraints#referential-integrity)