Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Assume that you use Management Data Warehouse (MDW) in a named instance of Microsoft SQL Server 2016 or 2017. When you try to reconfigure MDW settings by using SQL Server Management Studio (SSMS) or by executing the sp_syscollector_update_collection_set stored procedure, you may receive an error message that resembles the following:

Msg 14684, Level 16, State 1, Procedure ProcedureName, Line LineNumber [Batch Start Line LineNumber]

Caught error#: 14684, Level: 16, State: 1, in Procedure: ProcedureName, Line: LineNumber, with Message: Caught error#: 14262, Level: 16, State: 1, in Procedure: ProcedureName, Line: LineNumber, with Message: The specified @ServerName (...) does not exist.


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

      Cumulative Update 4 for SQL Server 2017

      Cumulative Update 7 for SQL Server 2016 SP1

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2016


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


Learn about the terminologythat Microsoft uses to describe software updates.

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!