Sql state 28000 native 18452 ошибка входа пользователя

  • Remove From My Forums

  • Вопрос

  • Hi All,

    Good Day!!!,

    Issue is when run the sql job from query its failed.

    Infra Brief 

    SQL Ver: SQL Server 2017, OS : Windows Server 2012

    We have 3 node Cluster and first 2 nodes will be part of active/passive and fail-over in between only &3rd Node we configured of Async  mode SQL AG on top of Cluster,

    the same jobs are executed successfully on first 2 nodes , whereas the same is not executed in 3rd node.

    Job Query
    ———-
    exec PROC_LCS_REPORT_ASSOCIATE_MASTER_TC_Card_SendMail null,’InActive’,’T’,null,null,null,’\\FileServer1\ITDev\DBA\PRIMARY-SQL\’

    output
    ——-
    SQLState = 28000, NativeError = 18452
    Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed. The login is from an  untrusted domain and cannot be used with Integrated authentication.

    thanks in Advance,

    Regards,

    Kesavan  K M

    Regards, Kesavan K M. Please remember to mark the replies as answers if they help.

    • Перемещено

      6 августа 2019 г. 1:38
      more related to this forum

Источник

I use windows 7 ultimate. I can login with windows authentication mode but SQL authentication with user sa doesn’t work. sa user is enabled. So what do I do?

RBT's user avatar

RBT

24.2k21 gold badges159 silver badges240 bronze badges

asked Aug 27, 2010 at 11:16

Rev's user avatar

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager

Right-click the SQL Server instance name > Select Properties from the context menu > Select Security node in left navigation bar

Under Authentication section, select SQL Server and Windows Authentication

Note: The server must be stopped and re-started before this will take effect

Error 18452 (not associated with a trusted sql server connection)

RBT's user avatar

RBT

24.2k21 gold badges159 silver badges240 bronze badges

answered Aug 27, 2010 at 11:18

Kashif's user avatar

KashifKashif

14.1k18 gold badges66 silver badges98 bronze badges

Login with windows authentication mode and fist of all make sure that the sa authentication is enabled in the server, I am using SQL Server Management Studio, so I will show you how to do this there.

Right click on the server and click on Properties.

enter image description here

Now go to the Security section and select the option SQL Server and Windows Authentication mode

enter image description here

Once that is done, click OK. And then enable the sa login.

Go to your server, click on Security and then Logins, right click on sa and then click on Properties.

enter image description here

Now go tot Status and then select Enabled under Login. Then, click OK.

Now we can restart the SQLExpress, or the SQL you are using. Go to Services and Select the SQL Server and then click on Restart. Now open the SQL Server Management Studio and you should be able to login as sa user.

answered Aug 29, 2019 at 9:58

Sibeesh Venu's user avatar

Sibeesh VenuSibeesh Venu

18.9k12 gold badges103 silver badges141 bronze badges

  1. Click on Start menu > Programs > Microsoft Sql Server > Configuration Tools

  2. Select Sql Server Surface Area Configuration.

  3. Now click on Surface Area configuration for services and connections

  4. On the left pane of pop up window click on Remote Connections and Select Local and Remote connections radio button.

  5. Select Using both TCP/IP and named pipes radio button.

  6. click on apply and ok.

Now when try to connect to sql server using sql username and password u’ll get the error mentioned below

Cannot connect to SQLEXPRESS.

ADDITIONAL INFORMATION:

Login failed for user ‘username’. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
ation
To fix this error follow steps mentioned below

  1. connect to sql server using window authentication.

  2. Now right click on your server name at the top in left pane and select properties.

  3. Click on security and select sql server and windows authentication mode radio button.

  4. Click on OK.

  5. restart sql server servive by right clicking on server name and select restart.

Now your problem should be fixed and u’ll be able to connect using sql server username and password.

Have fun.
Ateev Gupta

answered Feb 2, 2011 at 12:03

Ateev Gupta's user avatar

  1. First make sure sa is enabled
  2. Change the authontication mode to mixed mode (Window and SQL authentication)
  3. Stop your SQL Server
  4. Restart your SQL Server

RBT's user avatar

RBT

24.2k21 gold badges159 silver badges240 bronze badges

answered Aug 24, 2013 at 10:23

user2713396's user avatar

  1. Go to services.msc from run prompt.
  2. Restart the services of SQL server(MSSQLSERVER)
  3. Restart the services of SQL server(SQLEXPRESS)

RBT's user avatar

RBT

24.2k21 gold badges159 silver badges240 bronze badges

answered Jul 18, 2016 at 10:55

siva's user avatar

sivasiva

1151 silver badge4 bronze badges

I faced the very same error when I was trying to connect to my SQL Server 2014 instance using sa user using SQL Server Management Studio (SSMS). I was facing this error even when security settings for sa user was all good and SQL authentication mode was enabled on the SQL Server instance.

Finally, the issue turned out to be that Named Pipes protocol was disabled. Here is how you can enable it:

Open SQL Server Configuration Manager application from start menu. Now, enable Named Pipes protocol for both Client Protocols and Protocols for <SQL Server Instance Name> nodes as shown in the snapshot below:

enter image description here

Note: Make sure you restart the SQL Server instance after making changes.

P.S. I’m not very sure but there is a possibility that the Named Pipes enabling was required under only one of the two nodes that I’ve advised. So you can try it one after the other to reach to a more precise solution.

answered Mar 15, 2018 at 12:43

RBT's user avatar

RBTRBT

24.2k21 gold badges159 silver badges240 bronze badges

I was stuck in same problem for many hours. I tried everything found on internet.

At last, I figured out a surprising solution : I had missed \SQLEXPRESS part of the Server name: MY-COMPUTER-NAME\SQLEXPRESS

I hope this helps someone who is stuck in similar kind of problem.

answered Jun 29, 2020 at 7:39

Bigyan Chapagain's user avatar

Источник

Are you receiving a Microsoft SQL error 18452 while connecting to the database?

Incorrect authentication mode commonly causes this error.

Here at Bobcares, we routinely resolve SQL errors such as this as part of our Server Management Services.

Today we’ll cover the most effective fix and alternate solutions for Microsoft SQL error 18452.

What leads to Microsoft SQL error 18452?

SQL Server supports two authentication modes:

Windows authentication is the default mode. Specific Windows user and group accounts are trusted to log in to SQL Server.

Mixed-mode supports authentication by both Windows and SQL Server. SQL server maintains the User name and password pairs.

As Windows authentication mode is the default authentication mode enabled after installing the Microsoft SQL Server, users may face issues while connecting to the server.

[Need help to fix Microsoft SQL error 18452? We are available 24×7]

How to fix Microsoft SQL error 18452?

Switching to the Mixed-mode authentication can fix the Microsoft SQL error 18452.  This can be done easily with the steps below:

  • From Start >> click All Programs >> click Microsoft SQL Server 20xx (where xx is the version of SQL)>>and then click SQL Server Management Studio.
  • In the SQL Server Management Studio, right-click the server, and then click Properties.

Microsoft SQL error 18452

  • On the Security page, under Server authentication, click the SQL Server and Windows Authentication
    mode option button, and then click OK.

  Microsoft SQL error 18452

  • In the SQL Server Management Studio dialog box, click OK to restart SQL Server.

Alternative Fixes

At times, this error occurs when users try to connect by using SQL Server Authentication but the login used does not exist on SQL Server
To resolve this issue, verify that the SQL Server login exists.

Also, this error can occur if the login may use Windows Authentication but the login is an unrecognized Windows principal. An unrecognized Windows principal means that Windows can’t verify the login. This might be because the Windows login is from an untrusted domain. To resolve this issue, verify that you are logged in to the correct domain.

[Need help to fix Microsoft SQL error 18452? We are available 24×7]

Conclusion

In short, the common cause for SQL error 18452 is the Windows authentication mode. Today, we discussed how our support engineers fix this error easily.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

  • Hi,

    I have a SQL Server 2008R2 version which is configured to run with a local machine account. Lets call it A.This server has a linked server to another SQL Server ,say B.

    Now, i have an agent job on A which executes some code on Server B remotely. This job fails with an error below:

    Executed as user: A\UNITY. Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQLSTATE 28000] (Error 18452). The step failed.

    Looks like because ‘A’ is running with a local system account, therefore B is not able to recongnize it. Is there a way to solve this problem. Please help.

    Regards

    Chandan

  • Koen Verbeeck

    SSC Guru

    Points: 259075

  • chandan_jha18

    SSChampion

    Points: 11330

    🙂

    I cannot change the local system account:-(

    I am considering the option to run the job as proxy. Let’s say we use proxy by creating one and then use it in ‘run as user’ option in the job step. What connection will go to remote server B. Will it be proxy connection?

    currently, in the event viewer of B, I am seeing:

    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed.

  • Koen Verbeeck

    SSC Guru

    Points: 259075

    The connection will be the same. The credentials using that connection will however be that of the proxy account.

  • chandan_jha18

    SSChampion

    Points: 11330

    Thanks for your link above. To create a proxy, I needed to create a credential but while creating a credential, I got an error:

    an error occured during decryption Error: 15466 :w00t:

    Is there an easier way to create a proxy?

    Regards

    Chandan

  • Koen Verbeeck

    SSC Guru

    Points: 259075

    You have two options:

    create a proxy through TSQL, or use the Management Studio Interface.

    I think the last one will be the easiest.

    At which step did you get that error?

  • chandan_jha18

    SSChampion

    Points: 11330

    Koen Verbeeck (3/14/2012)

    You have two options:

    create a proxy through TSQL, or use the Management Studio Interface.

    I think the last one will be the easiest.

    At which step did you get that error?

    I read from the link that for creating a proxy, I need to have a credential. So while creating a credential,I put its name, the account and passwords. Then got the error when I tried to click on ‘OK’.

  • chandan_jha18

    SSChampion

    Points: 11330

    Also, in the microsoft link, it is mentioned that:

    Job steps that execute Transact-SQL do not use SQL Server Agent proxies. Transact-SQL job steps run in the security context of the owner of the job

    My job step has direct T-SQL code and not some procedures so proxy might not work for me. I put the owner as ‘sa’ but still the connection that goes to remote server is the local system account ‘A\Unity’.

  • Koen Verbeeck

    SSC Guru

    Points: 259075

    Ah ok. Maybe change the owner of the job to another account than sa?

    sa is a built-in account, so that also uses the local system account for connecting.

  • chandan_jha18

    SSChampion

    Points: 11330

    Koen Verbeeck (3/14/2012)

    Ah ok. Maybe change the owner of the job to another account than sa?

    sa is a built-in account, so that also uses the local system account for connecting.

    I changed the job owner to a windows account which is sysadmin on A. Following error is recorded in the job:

    Could not obtain information about Windows NT group/user ‘Doamin\account’, error code 0x5. [SQLSTATE 42000] (Error 15404)).

  • Koen Verbeeck

    SSC Guru

    Points: 259075

    Are server A and B in the same domain?

  • chandan_jha18

    SSChampion

    Points: 11330

    Koen Verbeeck (3/14/2012)

    Are server A and B in the same domain?

    Both the servers are in the same domain. One is running under a local account and other is running under domain account.

    I can login to both machines using my domain account. I cannot even create a linked server, it gives me authentication fail.

  • Ant-Green

    SSC Guru

    Points: 113275

    what account is the SQL Agent running as on A? Is it local system? Could you add a login to B which is DOMAIN\A$ and give it the access it needs? Which should allow local system to connect.

    On the linked server front, could you not create the linked server using a SQL authentication account (if your in mixed mode).

  • chandan_jha18

    SSChampion

    Points: 11330

    anthony.green (3/14/2012)

    what account is the SQL Agent running as on A? Is it local system? Could you add a login to B which is DOMAIN\A$ and give it the access it needs? Which should allow local system to connect.

    On the linked server front, could you not create the linked server using a SQL authentication account (if your in mixed mode).

    A is having local accounts for both sql services and agent services.

    For linked server, it gives me an error: anonymous logon failed

  • Ant-Green

    SSC Guru

    Points: 113275

    is that authentication error using windows accounts or sql accounts?

    can you post screen shots of the linked server config?

Viewing 15 posts — 1 through 15 (of 19 total)

Источник

Can’t connect a new client box (with XP pro SP3) to our existing sql server instance in our office. A dozen other computers connect just fine. We are a Workgroup setup, no domain. SQL Server is installed on a stand alone server up (Windows 2003)  with Windows authentication.

The user name and password (spelling and case) have been doubled checked in Local Users set up on the server. (password checked not to expire, just like the rest of our client set-ups)

Also, in our SQL database  on the server, in the security folder, the user name path shows correctly.

The ODBC DNS configuration on the client box is set with Windows NT authentication. Network libraries are TCP/IP with port dynamically determined. (Protocols for SQLEXPRESS have TCP/IP and named pipes enabled.)

I can’t find what I’m overlooking that is keeping the sql server from seeing this client machine.

Should I try renaming the user on the client machine (no data/settings to lose on this new box) ? I thought maybe a maximum amount of clients has been reached  for a Workgroup arrangement (SQL is set to zero — for no limit on connections)?

Unfortunately I am not a database person of any sorts, so kindly bear with me as I work to grasp your responses.

ES

Источник

Понравилась статья? Поделить с друзьями:
  • Sql state 28000 native 18456 ошибка входа пользователя
  • Sql server проверка базы на ошибки
  • Spore ошибка configuration script failed 2000
  • Sql server права учетной записи программы установки ошибка
  • Sql server ошибка при установке 1603