Forum Discussion
SQL Server 2019 CU22 (KB5027702) does not install correctly - crashes the server
- Aug 23, 2023Seems to come from here
Error: 2714, Severity: 16, State: 6.
2023-08-16 18:08:08.62 spid9s There is already an object named 'TargetServersRole' in the database.
Please follow below link. it is mentioning another object related to Database Mail but it should apply for your case too
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/install/windows/sql-server-upgrade-failed-error-2714
Error: 2714, Severity: 16, State: 6.
2023-08-16 18:08:08.62 spid9s There is already an object named 'TargetServersRole' in the database.
Please follow below link. it is mentioning another object related to Database Mail but it should apply for your case too
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/install/windows/sql-server-upgrade-failed-error-2714
- VK_DBAAug 24, 2023Copper Contributor
Resolution in my case is below
Cause:
The ##MS_SSISServerCleanupJobLogin## was missing from the SQL Server. The corresponding user was present in SSISDB database - likely dropped manually. Another possibility was that user was not following SSIS Catalog - SQL Server Integration Services (SSIS) | Microsoft Learn
There could be a missing user and login or problems with the user permissions ##MS_SSISServerCleanupJobLogin## and ##MS_SSISServerCleanupJobUser## - likely dropped manually
In some cases the SSISDB may missing/dropped but the login is still present
Resolution:
Resolution 1:
a. Start SQL Server with -T902
b. Recreate the login (server principal) on the server
CREATE LOGIN [##MS_SSISServerCleanupJobLogin##] WITH PASSWORD=N'<password>', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
c. Switch to the SSISDB database and map the existing user to the newly-created login
USE SSISDB
GO
ALTER USER[##MS_SSISServerCleanupJobUser##] with LOGIN =[##MS_SSISServerCleanupJobLogin##]
Resolution 2:
In some cases there may also be issues with the database user. In such cases you have to re-create it as well
a. Start SQL Server with -T902
b. Connect to SQL Server and drop and re-create the user the ##MS_SSISServerCleanupJobUser## in SSISDB using the following T-SQL Code:
USE [SSISDB]
GO
DROP USER [##MS_SSISServerCleanupJobUser##]
GO
USE [SSISDB]
GO
CREATE USER [##MS_SSISServerCleanupJobUser##] FOR LOGIN [##MS_SSISServerCleanupJobLogin##]
GO
USE [SSISDB]
GO
ALTER USER [##MS_SSISServerCleanupJobUser##] WITH DEFAULT_SCHEMA=[dbo]
GO
USE [SSISDB]
GO
GRANT EXECUTE ON [internal].[cleanup_server_project_version] TO [##MS_SSISServerCleanupJobUser##]
GO
GRANT EXECUTE ON [internal].[cleanup_server_retention_window] TO [##MS_SSISServerCleanupJobUser##]
- Aug 23, 2023Glad it helped.
Please mark the question as Answered so others can benefit too
Thanks
Javier