May 18, 2021 at 4:27 pm
Hello All,
Need urgent help on this. We have applied latest sql patches on one of the server (SQL 2014, SP3, CU4) and somehow we were not able to start the SQL due to following error.
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Error: 3417, Severity: 21, State: 3.
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it.
So, i have started the server with Trace flag 902 and run the script msdb110_upgrade script and it failed with
Msg 468, Level 16, State 9, Procedure #syscollector_upload_package, Line 37659
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the not equal to operation.
Can anyone please help to fix this issue?
May 18, 2021 at 6:22 pm
Update:
I performed the steps described below with option 2 and run the script msdb110_upgrade script and it failed with following error message.
https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/
Msg 468, Level 16, State 9, Procedure sp_sqlagent_get_perf_counters, Line 5395
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AI" in the equal to operation.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply