Quantcast
Viewing all articles
Browse latest Browse all 7696

update to sql2012 failed: collation conflict.

I tried to change (update) the server from 2008 to 2012. The update fails with the error-code 0x851A0019.

what can I do?

the last lines of the protocol:

2013-06-03 11:56:51.86 spid8s      Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the not equal to operation.

2013-06-03 11:56:51.94 spid8s      The failed batch of t-sql statements :

CREATE PROCEDURE #syscollector_upload_package

    @packagename sysname,

    @packageid uniqueidentifier,

    @versionid uniqueidentifier

AS

BEGIN

    DECLARE @installpath nvarchar(2048);

    EXEC master.dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\MSSQLServer\Setup', N'SQLPath', @installpath OUTPUT;

    IF RIGHT(@installpath,1) != N'\' set @installpath = @installpath + N'\'

    SET @installpath  = @installpath + N'Install\'

    DECLARE @filename nvarchar(2048);

    SET @filename = @installpath + @packagename + N'.dtsx'

    RAISERROR ('Uploading data collector package from disk: %s', 0, 1, @filename) WITH NOWAIT;

    EXEC #syscollector_upload_package_from_file @filename=@filename, @packagename=@packagename, @packageid=@packageid, @versionid=@versionid;   

END;

2013-06-03 11:56:51.95 spid8s      Error: 912, Severity: 21, State: 2.

2013-06-03 11:56:51.95 spid8s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_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.

2013-06-03 11:56:52.02 spid8s      Error: 3417, Severity: 21, State: 3.

2013-06-03 11:56:52.02 spid8s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

2013-06-03 11:56:52.04 spid8s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.


O.F.



Viewing all articles
Browse latest Browse all 7696

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>