Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 5695 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

upgrading from EPC 5.3.1 to EPC 5.4 fails during PatchDB Upgrade

Frank-Michael Bickel

Hi,

during the Upgrade Process of Sophos Patch DB we are receiving the following Error:

Meldung '468', Ebene '16', Status '9', Server 'SSQL13C\INST2', Prozedur 'usp_PurgeDeletedEndpointData', Zeile 21
'Ein Sortierungskonflikt zwischen 'Latin1_General_CI_AS' und 'SQL_Latin1_General_CP1_CI_AS' im equal to-Vorgang kann nicht aufgelöst werden.'
Meldung '468', Ebene '16', Status '9', Server 'SSQL13C\INST2', Prozedur 'usp_PurgeDeletedEndpointData', Zeile 55
'Ein Sortierungskonflikt zwischen 'Latin1_General_CI_AS' und 'SQL_Latin1_General_CP1_CI_AS' im equal to-Vorgang kann nicht aufgelöst werden.'

In English: Cannot resolve the collation conflict between “Latin1_General_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation.

I followed the following KB Article: https://www.sophos.com/de-de/support/knowledgebase/116768.aspx#upgrademem
So I am trying to upgrade the Databases via Command Line Tools.

Is this a know Issue? What can we do for resolve this issue?
For your information, we are not using SophosPatch Analysis so this DB should be empty.

Can anyone suggest me sth for resolving this Error?

thanks and kind regards
Freank



This thread was automatically locked due to age.
Parents
  • 0

    Hello Freank,

    so you're not using the default instance.

    You did create the SOPHOS540 database which worked fine but upgrading SOPHOSPATCH52 (which already existed) failed? And you didn't try to update the SophosSecurity database (which might or might not have worked)?

    Wild guess: It looks like the default collation for your instance has changed and the newly created database SOPHOS540 has not the same collation as SOPHOSPATCH52. To verify from an elevated cmd prompt use:
    sqlcmd -E -S SSQL13C\INST2 -Y 40 -Q "SELECT DATABASEPROPERTYEX('SOPHOSPATCH52', 'Collation') SQLCollation"
    repeat with SOPHOS540.

    If you're not using Patch (and not really using Audit, i.e. the SophosSecurity database) you can use InstallSophosSecurity.bat and and CreatePatchDB.bat to create empty databases. You did back up your existing databases, didn't you? As I haven't tested it I'm not sure that "resetting" SophosSecurity this way during an upgrade is safe.

    Christian

Reply
  • 0

    Hello Freank,

    so you're not using the default instance.

    You did create the SOPHOS540 database which worked fine but upgrading SOPHOSPATCH52 (which already existed) failed? And you didn't try to update the SophosSecurity database (which might or might not have worked)?

    Wild guess: It looks like the default collation for your instance has changed and the newly created database SOPHOS540 has not the same collation as SOPHOSPATCH52. To verify from an elevated cmd prompt use:
    sqlcmd -E -S SSQL13C\INST2 -Y 40 -Q "SELECT DATABASEPROPERTYEX('SOPHOSPATCH52', 'Collation') SQLCollation"
    repeat with SOPHOS540.

    If you're not using Patch (and not really using Audit, i.e. the SophosSecurity database) you can use InstallSophosSecurity.bat and and CreatePatchDB.bat to create empty databases. You did back up your existing databases, didn't you? As I haven't tested it I'm not sure that "resetting" SophosSecurity this way during an upgrade is safe.

    Christian

Children
Unfiltered HTML