Re: Windows NT user or group not found.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I only work with English (typical American I know) so this may be off base
but I recently worked on something that might help.
The SUSER_SID function has an optional parameter that can help you figure
out what SQL Server thinks the login name is vs. what Windows thinks the
login name is.

When the SQL Server collation and the Windows collation are different,
SUSER_SID can fail if SQL Server and Windows store the login in a different
format. For example, if a Windows computer named TestComputer has a login
named User, and SQL Server stores the login as TESTCOMPUTER\User, then the
lookup of the login TestComputer\User might fail to resolve login name
properly. Use the Param2 parameter to skip the validation of the login name.
The following example uses the Param2 parameter to get the SID from Windows
and uses that SID as an input to the SUSER_SNAME function.

SELECT SUSER_SNAME(SUSER_SID('TestComputer\User', 0)) ;

The example inputs the login in the format stored in Windows
(TestComputer\User), and returns the login in the format stored in SQL
Server (TESTCOMPUTER\User).


This may not be helpful, but maybe it will give you some ideas.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns9C4EEAF6E1DC9Yazorman@xxxxxxxxxxxx
Andreas (Andreas@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I encounter problems renaming an account with an Umlaut. Here is the
Sample: Domain\Müller should be renamed to Domain\Muller. In AD
everything is ok.

Here is the SQL:
CREATE LOGIN [Domain\muller] FROM WINDOWS
--> Windows NT user or group 'Domain\muller' not found. Check the name
again.

CREATE LOGIN [Domain\müller] FROM WINDOWS
--> Command(s) completed successfully.

ALTER LOGIN [Domain\müller] WITH NAME = [Domain\muller];
--> Windows NT user or group 'Domain\muller' not found. Check the name
again.

So what is the name of the user in the AD? Muller or Müller? The error
message complains about Domain\muller not being found, which makes me
think the name in the AD is still Müller.




--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx



.

Relevant Pages

  • Re: Granting permission to a database - need help
    ... Windows authentication, and not use an application login, as then ... Links for SQL Server Books Online: ... USE Driver Access ...
    (microsoft.public.sqlserver.programming)
  • Re: ODBC worked until Server reboot defaulted to windows authentic
    ... I got the exact spelling of the windows login with the case and I rebooted ... The odbc source is set up in windows and that connects on the test. ... The SQL Server Mgmt studio connects also but only as Windows authentication. ...
    (microsoft.public.sqlserver.setup)
  • Re: login 101..
    ... On Windows 2003, SQL Server 2005 can enforce the Windows password complexity ... Windows authentication - SQL Server uses a special protocol to ask ... user is in the list of allowed logins, ...
    (microsoft.public.sqlserver.security)
  • Re: Granting permission to a database - need help
    ... folder and it would have the database connection info. ... Windows authentication, and not use an application login, as then ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.programming)
  • RE: How to create a trusted connection
    ... You need to grant access for the Windows login by referring to the books ... is set to use Windows authentication to be able to do trusted connection. ... There are two modes of authentication in SQL Server: ...
    (microsoft.public.sqlserver.security)