KB4469140 - FIX: "Could not find server" when the publisher database name contains a period in SQL Server 2017


Assume that you set up SQL Server replication and created a publication on a database that has a period in its name. If you run the Expired subscription clean up job or the sys.sp_expired_subscription_cleanup stored procedure, the job or stored procedure fails, and you receive an error message that resembles the following:

Msg 7202, Level 11, State 2, Procedure sp_expired_subscription_cleanup

Could not find server 'dbname' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.


A fix for this issue is included in the following update for SQL Server:

Cumulative Update 12 for SQL Server 2017

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

SQL Server 2017 build versions


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


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.