ApsaraDB RDS:What do I do if the "Logon failed for login 'user' due to trigger execution" error message is displayed when I connect to my ApsaraDB RDS for SQL Server instance?

Problem description

The Logon failed for login 'user' due to trigger execution error message is displayed during the connection to an ApsaraDB RDS for SQL Server instance.

Causes

The number of connections to the RDS instance reaches the upper limit.

Solution

1. Connect to the RDS instance from a client. For more information, see Connect to an ApsaraDB RDS for SQL Server instance.

2. Check whether the number of connections reaches the upper limit. You can execute the following SQL statement to query the number of connections:

   SELECT * FROM SYS.SYSPROCESSES WHERE SPID > 50 AND LOGINAME NOT IN ('SA', 'AURORA');

   Note

   If a large number of connections are established, you can resolve the issue based on the instructions provided in What do I do if the number of connections to an ApsaraDB RDS for MySQL instance reaches the upper limit?

3. If the number of connections does not reach the upper limit, execute the following SQL statement to query the number of processes and check whether a blocking issue exists:

   SELECT * FROM SYS.SYSPROCESSES

   Note

   If a blocking issue exists, you can resolve the issue based on the instructions provided in What do I do if requests are blocked on an ApsaraDB RDS for SQL Server instance?

References

• In specific scenarios, if the number of connections to the RDS instance reaches the upper limit, you can manually restart the RDS instance to alleviate or resolve the issue. For more information, see Restart an instance.

• For more information about how to resolve a connection failure of an RDS instance, see What do I do if I fail to connect to an ApsaraDB RDS instance?