sql-server-2008 - 无法启动 SQL Server

Question

关闭。这个问题是 off-topic 。它目前不接受答案。












想改善这个问题吗？ Update the question 所以它是堆栈溢出的 on-topic。

8年前关闭。




Improve this question




我正在为一个学校项目制作一个网站。下载了 Visual Studio 2010(我们在学校使用的版本)，现在我正在尝试在其上运行我的网站。
SQL 不会连接。我尝试了我所知道的一切，但没有任何效果。
尝试在 SQL Server Management Studio 中进行连接时，它为我的用户显示“登录失败”。顺便说一下，我正在尝试 Windows 身份验证尝试查看 SQL 错误日志，但没有!

我感到非常沮丧，我在网上看到的每个答案都提到了我不理解的真实网站和术语。我只是想让我的数据库工作!请，请帮助。

不知道该怎么办。

编辑:好的，找到了日志!!它在一个文件夹中，然后提到的有点不同。
我认为这是问题:
编辑:尝试了几个建议的步骤。服务器现在(我认为)处于单用户模式。
仍然无法登录但不同的问题 - 这是日志。

2013-05-26 19:14:03.97 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) 
    Jun 28 2012 08:36:30 
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2013-05-26 19:14:03.97 Server      (c) Microsoft Corporation.
2013-05-26 19:14:03.97 Server      All rights reserved.
2013-05-26 19:14:03.97 Server      Server process ID is 2968.
2013-05-26 19:14:03.97 Server      Authentication mode is MIXED.
2013-05-26 19:14:03.97 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2013-05-26 19:14:03.97 Server      This instance of SQL Server last reported using a process ID of 4068 at 26/05/2013 19:11:31 (local) 26/05/2013 16:11:31 (UTC). This is an informational message only; no user action is required.
2013-05-26 19:14:03.97 Server      Registry startup parameters: 
     -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
     -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
     -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
     -m
2013-05-26 19:14:03.99 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-05-26 19:14:03.99 Server      Detected 4 CPUs. This is an informational message; no user action is required.
2013-05-26 19:14:04.00 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2013-05-26 19:14:04.00 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.
2013-05-26 19:14:04.01 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-05-26 19:14:04.02 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2013-05-26 19:14:04.02 spid6s      Warning ******************
2013-05-26 19:14:04.02 spid6s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2013-05-26 19:14:04.02 spid6s      Starting up database 'master'.
2013-05-26 19:14:04.10 spid6s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-05-26 19:14:04.14 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2013-05-26 19:14:04.15 spid6s      SQL Trace ID 1 was started by login "sa".
2013-05-26 19:14:04.15 spid6s      Starting up database 'mssqlsystemresource'.
2013-05-26 19:14:04.19 spid6s      The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2013-05-26 19:14:04.28 spid9s      Starting up database 'model'.
2013-05-26 19:14:04.28 spid6s      Server name is 'NETA\SQLEXPRESS'. This is an informational message only. No user action is required.
2013-05-26 19:14:04.28 spid6s      Informational: No full-text supported languages found.
2013-05-26 19:14:04.28 spid6s      Starting up database 'msdb'.
2013-05-26 19:14:04.39 Server      A self-generated certificate was successfully loaded for encryption.
2013-05-26 19:14:04.39 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2013-05-26 19:14:04.39 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2013-05-26 19:14:04.39 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2013-05-26 19:14:04.39 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2013-05-26 19:14:04.39 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-05-26 19:14:04.50 spid9s      Clearing tempdb database.
2013-05-26 19:14:04.74 spid9s      Starting up database 'tempdb'.
2013-05-26 19:14:04.80 spid6s      Recovery is complete. This is an informational message only. No user action is required.
2013-05-26 19:14:14.60 Logon       Error: 18456, Severity: 14, State: 11.
2013-05-26 19:14:14.60 Logon       Login failed for user 'Neta\Neta'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

Answer 1

也许你的 sql server 服务没有启动。尝试这个...

转到:控制面板 -> 管理工具 -> 服务

检查这些服务是否已启动:

SQL 全文过滤器守护程序启动器 (MSSQLSERVER)

SQL Server (MSSQLSERVER)

SQL Server 集成服务 10.0

SQL Server 报告服务 (MSSQLSERVER)

SQL Server VSS 编写器

检查完所有内容后，启动 SQL Server Management Studio 。

您现在可以通过单击连接按钮连接到您的服务器:
(服务器类型:数据库引擎，服务器名称:.和身份验证:windows身份验证)

默认情况下，在左侧的对象资源管理器中，您应该看到您的服务器，如果没有，请尝试单击“连接对象资源管理器”，然后单击连接按钮。

对于可怕的延迟，我很抱歉，因为我现在看到了您的评论。我只是想，也许您有另一个使用您的 ms sql server 端口的程序。例如 ms sql server 使用端口 80 和另一个程序/服务器，如 apache 使用相同的端口。
如果每个程序都在 Windows 登录/启动时更早开始，则第一个程序会占用该端口，因此不允许其他人使用该端口。
所以 !？如果您的问题仍然存在，您必须检查 80 端口未被其他程序使用。