sqlserver数据库出错的解决方法
1.SQLServer2008数据库sa账户登录127.0.0.1失败
http://blog.sina.com.cn/s/blog_546a30270102weh2.html
2.SqlServer配置管理器中的sql服务 远程过程调用失败
3.无法通过windows authentication进行登录
http://www.cnblogs.com/zerocc/p/3425431.html
通过命令行来启动数据库的话，
C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn>sqlservr.exe
2017-06-07 11:16:15.12 Server Microsoft SQL Server 2012 (SP1) - 11.0.3156.0 (X64)
May 4 2015 18:48:09
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2017-06-07 11:16:15.12 Server (c) Microsoft Corporation.
2017-06-07 11:16:15.12 Server All rights reserved.
2017-06-07 11:16:15.12 Server Server process ID is 21236.
2017-06-07 11:16:15.12 Server System Manufacturer: 'Dell Inc.', System Model: 'Latitude E5470'.
2017-06-07 11:16:15.12 Server Authentication mode is MIXED.
2017-06-07 11:16:15.12 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2017-06-07 11:16:15.13 Server The service account is 'ASNET\clu'. This is an informational message; no user action is required.
2017-06-07 11:16:15.13 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2017-06-07 11:16:15.29 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-06-07 11:16:15.29 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-06-07 11:16:15.29 Server Detected 16266 MB of RAM. This is an informational message; no user action is required.
2017-06-07 11:16:15.31 Server Using conventional memory in the memory manager.
2017-06-07 11:16:15.41 Server This instance of SQL Server last reported using a process ID of 27204 at 2017/6/7 11:14:29 (local) 2017/6/7 3:14:29 (UTC). This is an informational message only; no user action is required.
2017-06-07 11:16:15.41 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-06-07 11:16:15.42 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2017-06-07 11:16:15.44 Server Software Usage Metrics is disabled.
2017-06-07 11:16:15.44 spid4s Starting up database 'master'.
2017-06-07 11:16:15.53 Server CLR version v4.0.30319 loaded.
2017-06-07 11:16:15.56 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-06-07 11:16:15.69 spid4s Resource governor reconfiguration succeeded.
2017-06-07 11:16:15.69 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-06-07 11:16:15.70 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-06-07 11:16:15.75 spid4s SQL Trace ID 1 was started by login "sa".
2017-06-07 11:16:15.75 spid4s Server name is 'WASYGSHA01-1020'. This is an informational message only. No user action is required.
2017-06-07 11:16:15.77 spid4s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
2017-06-07 11:16:15.78 spid16s Starting up database 'msdb'.
2017-06-07 11:16:15.78 spid17s Starting up database 'LISA5_RPS'.
2017-06-07 11:16:15.78 spid18s Starting up database 'LISA5_PRG_Rewind'.
2017-06-07 11:16:15.78 spid20s Starting up database 'LISA5_CMS_Rewind'.
2017-06-07 11:16:15.78 spid9s Starting up database 'mssqlsystemresource'.
2017-06-07 11:16:15.78 spid19s Starting up database 'Installer_Repository5'.
2017-06-07 11:16:15.78 spid22s Starting up database 'Installer_CMS_Master5'.
2017-06-07 11:16:15.78 spid21s Starting up database 'Installer_Program_Master5'.
2017-06-07 11:16:15.78 spid23s Starting up database 'd_lisa_Program_RDC1F47A8FA04CD9272'.
2017-06-07 11:16:15.80 spid13s A self-generated certificate was successfully loaded for encryption.
2017-06-07 11:16:15.80 spid24s Starting up database 'd_lisa_CMS_RDC1F47A8FA04CD9272'.
2017-06-07 11:16:15.80 spid25s Starting up database 'TW_LS_RPS'.
2017-06-07 11:16:15.80 spid26s Starting up database 'TW_LS_PRG_DHL4_Base'.
2017-06-07 11:16:15.85 spid27s Starting up database 'TW_LS_CMS_DHL4'.
2017-06-07 11:16:15.85 spid13s Server is listening on [ 'any' <ipv6> 1433].
2017-06-07 11:16:15.86 spid28s Starting up database 'TW_LS_PRG_DHL4'.
2017-06-07 11:16:15.87 spid13s Server is listening on [ 'any' <ipv4> 1433].
2017-06-07 11:16:15.87 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2017-06-07 11:16:15.87 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2017-06-07 11:16:15.89 spid13s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2017-06-07 11:16:15.91 Server Server is listening on [ ::1 <ipv6> 1434].
2017-06-07 11:16:15.91 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2017-06-07 11:16:15.91 Server Dedicated admin connection support was established for listening locally on port 1434.
2017-06-07 11:16:15.93 spid13s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-06-07 11:16:15.93 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-06-07 11:16:15.94 spid9s Starting up database 'model'.
2017-06-07 11:16:15.97 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WASYGSHA01-1020.asnet.accorservices.net ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-06-07 11:16:15.98 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WASYGSHA01-1020.asnet.accorservices.net:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-06-07 11:16:16.01 spid9s Clearing tempdb database.
2017-06-07 11:16:16.45 spid9s Starting up database 'tempdb'.
2017-06-07 11:16:16.53 spid29s The Service Broker endpoint is in disabled or stopped state.
2017-06-07 11:16:16.53 spid29s The Database Mirroring endpoint is in disabled or stopped state.
2017-06-07 11:16:16.55 spid29s Service Broker manager has started.
2017-06-07 11:16:16.65 spid4s Recovery is complete. This is an informational message only. No user action is required.
2017-06-07 11:16:40.50 Logon Error: 18456, Severity: 14, State: 5.
2017-06-07 11:16:40.50 Logon Login failed for user 'ASNET\clu'. Reason: Could not find a login matching the name provided. [CLIENT: 127.0.0.1]
2017-06-07 11:20:29.80 Logon Error: 18456, Severity: 14, State: 5.
2017-06-07 11:20:29.80 Logon Login failed for user 'ASNET\clu'. Reason: Could not find a login matching the name provided. [CLIENT: 172.31.212.20]
2017-06-07 11:21:45.60 Server Using 'dbghelp.dll' version '4.0.5'
2017-06-07 11:23:15.55 Server ***Unable to get thread context for spid 0
2017-06-07 11:23:15.55 Server * *******************************************************************************
2017-06-07 11:23:15.55 Server *
2017-06-07 11:23:15.55 Server * BEGIN STACK DUMP:
2017-06-07 11:23:15.55 Server * 06/07/17 11:23:15 spid 14040
2017-06-07 11:23:15.55 Server *
2017-06-07 11:23:15.55 Server * Non-yielding Scheduler
2017-06-07 11:23:15.56 Server *
2017-06-07 11:23:15.56 Server * *******************************************************************************
2017-06-07 11:23:15.56 Server Stack Signature for the dump is 0x000000000000029A
2017-06-07 11:23:17.04 Server External dump process return code 0x20000001.
External dump process returned no errors.
2017-06-07 11:23:17.04 Server DoMiniDump () encountered error (0x80004005) - Unspecified error
2017-06-07 11:23:17.04 Server Process 0:0:0 (0x511c) Worker 0x00000004784A0160 appears to be non-yielding on Scheduler 5. Thread creation time: 13141278975449. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 95%. Interval: 70137 ms.
https://www.isunshare.com/sql-server/fix-sql-server-failed-login-error.html
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos.
最后发现是域账号的问题导致的，电脑的sql server是前同事安装的，但是安装的时候，是用的他自己的域账号。
我的域账号尝试登陆无法识别的。
处理方法，用之前同事的域账号登陆电脑，然后连接上数据库。然后把自己的域账号加入到logins中。
SQL server 2008 15434 以及 15023
从数据库删除用户的的时候，提示用户已经登录，不允许删除
通过下面的查询语句找到session编号
SELECT session_id
FROM sys.dm_exec_sessions
WHERE login_name = 'chuck'
然后强制结束session，其中67是我找到的编号
kill 67
=========================================
删除用户之后，重新创建用户遇到的问题
在出问题的数据库上执行这个命令
sp_change_users_login 'AUTO_FIX', 'chuck'
The row for user 'chuck' will be fixed by updating its login link to a login already in existence.
The number of orphaned users fixed by updating users was 1.
The number of orphaned users fixed by adding new logins and then updating users was 0.
多次 执行直到出现
The number of orphaned users fixed by updating users was 0.
The number of orphaned users fixed by adding new logins and then updating users was 0.
sqlserver附加数据库失败
我遇到的问题是，之前用的EntityFramework，添加数据库，是以链接数据文件生成的。
链接数据库后台是由EF做的
<connectionStrings>
<add name="SchoolDBEntities" connectionString="metadata=res://*/School.csdl|res://*/School.ssdl|res://*/School.msl;provider=System.Data.SqlClient;provider connection string="data source=LUJUNTAO\MSSQLSERVER2012;initial catalog=SchoolDB;persist security info=True;user id=sa;password=123456;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
</connectionStrings>
坑爹了，发现之前连接数据库的时候，没有用127.0.0.1，用的居然是LUJUNTAO\MSSQLSERVER2012
备注：
在"127.0.0.1"附加的数据库和在"用户名\数据库实例"附加的数据库是不一致的
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
连接局域网中的数据库（remote database），遇到上面的错误。原因是本地配置的代理没有bypass掉局域网的ip。然后还需要重启一下机器
登录失败 18456
Server Name: .
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
State 1
Error information is not available. This state usually means you do not have permission to receive the error details. Contact your SQL Server administrator for more information.
最后发现是因为连错了数据库，
本地安装了sql server 2008和sql server 2014，其中sql server 2008的连接是127.0.0.1，但是sql server 2014的连接应该是127.0.0.1\sql2014
用everything搜索，ssms.exe "C:\Program Files (x86)\Microsoft SQL Server\" 【ssms.exe是sql server management studio】
"C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\Ssms.exe"
登陆失败 error 26
在连接数据库的时候，需要显示指定端口1433。
或者启用SQL Server Browser
https://dba.stackexchange.com/questions/118458/connect-to-sql-server-without-specifying-port
如果sql server browser是灰色的，无法启用。那么打开services管理工具，设置SQL Server Browser服务的启动方式为Automatic()
https://stackoverflow.com/questions/21375014/i-cannot-start-sql-server-browser
