FIX: SQL Server crashes when you run a remote query in a stored procedure by using an invalid user name

Applies to: SQL Server 2014 EnterpriseSQL Server 2014 EnterpriseSQL Server 2014 Developer More

Symptoms


Assume that you run a remote query such as sp_batch_params in a stored procedure in Microsoft SQL Server 2012, 2014, or 2016. If the user name is invalid and can't log in the remote server, your instance of SQL Server crashes, and you receive a generic error message.

Resolution


After you apply this hotfix, the instance of SQL Server won't crash, and you receive the following error message when you run the query that is described in the "Symptoms" section:
Msg 18487, Level 14, State 1,
Login failed for user <username>. Reason: The password of the account has expired.
Msg 18456, Level 14, State 1,
Login failed for user <username>.

The issue was first fixed in the following cumulative updates of SQL Server:

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.