Applies ToSQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2012 Service Pack 3 SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Enterprise Core SQL Server 2012 Express SQL Server 2012 Standard SQL Server 2012 Web SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

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:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:

Status

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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.