Quantcast
Channel: Forum Getting started with SQL Server
Viewing all articles
Browse latest Browse all 7129

Not Able to connect SQL server after installation

$
0
0

Hello,

I'm using Windows 2008 R2 SP1.

I created two servers.

the first server hold Domain controller and active directory and I created user called "kim_akers" and make him member of "Domain Admins","Domian Users", Enterprise Admins", and "Schema Admins".

The second server has joined the Windows Domain of the first server.

I logged in the second server with "kim_akers" and tried to install "SQL Server" and make this user used for windows authentication.

After Installation, I restarted the server.

Then login windows with "kim_akers". and tried to login SQL server with windows authentication. 

the message show to me

login failed for user 'CONTSO\KIM_AKERs'. (Microsoft SQL Server, Error: 18456)

at logs

2017-01-19 04:57:43.94 spid15s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\THIRDINST ].
2017-01-19 04:57:43.94 spid15s     Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$THIRDINST\sql\query ].
2017-01-19 04:57:43.94 Server      Server is listening on [ ::1 <ipv6> 49155].
2017-01-19 04:57:43.94 Server      Server is listening on [ 127.0.0.1 <ipv4> 49155].
2017-01-19 04:57:43.94 Server      Dedicated admin connection support was established for listening locally on port 49155.
2017-01-19 04:57:43.94 spid15s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-01-19 04:57:43.94 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-01-19 04:57:43.96 spid10s     Starting up database 'tempdb'.
2017-01-19 04:57:44.01 spid18s     The Service Broker endpoint is in disabled or stopped state.
2017-01-19 04:57:44.01 spid18s     The Database Mirroring endpoint is in disabled or stopped state.
2017-01-19 04:57:44.02 spid18s     Service Broker manager has started.
2017-01-19 04:57:44.03 spid8s      Recovery is complete. This is an informational message only. No user action is required.
2017-01-19 04:57:45.02 Server      Software Usage Metrics is disabled.
2017-01-19 04:57:49.62 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SQLNODE1.Contso.com:THIRDINST ] for the SQL Server service.
2017-01-19 04:59:54.01 Logon       Error: 18456, Severity: 14, State: 5.
2017-01-19 04:59:54.01 Logon       Login failed for user 'CONTSO\Kim_Akers'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2017-01-19 05:02:07.78 Logon       Error: 18456, Severity: 14, State: 5.
2017-01-19 05:02:07.78 Logon       Login failed for user 'CONTSO\Kim_Akers'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2017-01-19 05:02:16.59 Logon       Error: 18456, Severity: 14, State: 5.
2017-01-19 05:02:16.59 Logon       Login failed for user 'CONTSO\Kim_Akers'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

How I can solve this problem ?

Thanks.



Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>