Home/ Questions/Q 6165519
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T22:10:49+00:00

Given a Windows Server 2008 R2 system, where the service accounts use a non-English

  • 0

Given a Windows Server 2008 R2 system, where the service accounts use a non-English display language, with SQL Server 2008, the following Transact-SQL statement fails:

CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS ...

with the following error:

Windows NT user or group ‘NT AUTHORITY\NETWORK SERVICE’ not found. Check the name again.

(or the same message in the non-English display language for the service accounts, depending on the context).

This same statement succeeds if the service accounts use English as their display language.

The reason seems clear: on, e.g., a German system the display name for this account is NT-AUTORITÄT\NETZWERKDIENST, and the name NT AUTHORITY\NETWORK SERVICE (with a space) is not recognized. Also the non-localized name NT AUTHORITY\NETWORKSERVICE (no space) does not work.

My question: How should I rewrite the above statement so that it works irrespective of the display language? Or am I forced to find out the localized name (in InstallScript in my case)? Then I can use

CREATE LOGIN [NT-AUTORITÄT\NETZWERKDIENST] FROM WINDOWS

which does work…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From what I’ve tried, and from what I read in a German forum thread entitled “Well-known SID im SQL Server nutzen”, this is not possible. Apparently unfortunately SQL Server’s CREATE LOGIN was designed to accept only a localized name in DOMAIN\username format.

    A hint, from that same thread, is to look at section “Localized Service Names” in “Setting Up Windows Service Accounts” for the localized names that need to be used in a CREATE LOGIN statement.

    The only alternative is to try and find out the system language of the Windows system running SQL Server, then use the “Localized Service Names” table to find the localized service account name, and use that to create a working CREATE LOGIN statement.

    • 0