Installing service pack 1 on server using default language British English

  • Fishbarnriots

    SSCrazy

    Points: 2568

    Hi,

    I am having great difficulty installing Service Pack 1 on a server that has been configured to use British English.

    It is implying that there is no instance of SQL Server to upgrade (when clearly there is). Investigation would seem to suggest that the reason for this is that the instance of SQL on the sever has been set to use British English and the service pack is expecting US English.

    The install fails at the Select Features option where no features are selected by default and it is not possible to manually select any.

    MSSQLSERVER =

    "The language of SQL Server instance MSSQLSERVER does not match the language expected by the SQL Server update. The installed SQL Server product language is English (United Kingdom) and the expected SQL Server language is English (United States)."

    Analysis services =

    "The language of SQL Server instance MSSQLSERVER does not match the language expected by the SQL Server update. The installed SQL Server product language is English (United Kingdom) and the expected SQL Server language is English (United States)."

    Shared features =

    "The language of SQL Server instance Shared Component does not match the language expected by the SQL Server update. The installed SQL Server product language is English (United Kingdom) and the expected SQL Server language is English (United States)."

    Does anyone have a solution to this, other than altering the default language to US English, installing the service pack and then changing the language back again.

  • george sibbald

    SSC Guru

    Points: 104200

    bit of a shot in the dark but has anyone changed the locale of the server?

    ---------------------------------------------------------------------

  • ServerGuy

    Newbie

    Points: 1

    Is there any chance you got this sorted out?  If so can you provide any information on the solution?  I am in the exact same situation now while trying to upgrade SQL 2008 R2 SP1 to SP2

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply