FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 or 2016 if the server name is too long

Applies to: SQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 Enterprise Core


Assume that you use the multiserver environment in Microsoft SQL Server 2014 or 2016. When you try to enlist a target server to a master server by using the sp_msx_enlist stored procedure, if the length of the server name that you specified for the @msx_server_name argument is longer than 32 characters, the operation may fail. Additionally, you may receive an error message that resembles the following:

Msg 22026, Level 16, State 1, Line LineNumber

The enlist operation failed (reason: The time-out was exceeded while the server waited for a response from SQL Server Agent. Make sure that the SQL Server Agent service is running)


This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 5 for SQL Server 2016 RTM

Cumulative Update 2 for SQL Server 2016 SP1



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


Learn about the terminology that Microsoft uses to describe software updates.