RE: Error 18452

From: Fany Vargas [MSFT] (fvargas_at_online.microsoft.com)
Date: 11/20/04 

Date: Sat, 20 Nov 2004 07:23:47 GMT

This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:

In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.

References:
See Books Online topic: Authentication Modes

Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Relevant Pages

  • Re: System Administrator Implied Permissions
    ... >> Hi Dan, ... >> Now, given this, why does SQL Server ... However, these logins were not ... Other sysadmin role members have the ...
    (microsoft.public.sqlserver.security)
  • MS03-031 issue
    ... After installing the hotfix on sql server 2000 sp3/windows ... 2000 there is a problem when altering a standard ID login ... to the database user account within the database itself ... there isn't an issue, only with logins. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... Only creating Logins is not the complete solution of course, then you'll need to map those users to the appropriate databases and assign them roles and grant them permissons. ...
    (microsoft.public.sqlserver.clients)
  • Re: Windows permissions to run Jet OLEDB 4.0
    ... in SQL Server or not when you have to go outside of the server to the ... Actually I was talking about Windows logins. ... There is no security whatsoever implemented on the mdb ...
    (microsoft.public.data.oledb)
  • Re: Logins & Permissions
    ... At server level, we use "Logins" to connect to a SQL Server Instance and perform server level jobs. ... "Users" are used and these users are mapped to Logins. ... I am using SQL Server 2005 on a Windows NT Network ...
    (microsoft.public.sqlserver.security)
Loading