sql server 服务启动后 自动关闭 求大虾
错误日志如下
2013-08-29 12:57:45.81 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2013-08-29 12:57:45.81 Server (c) 2005 Microsoft Corporation.
2013-08-29 12:57:45.81 Server All rights reserved.
2013-08-29 12:57:45.81 Server Server process ID is 1360.
2013-08-29 12:57:45.81 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2013-08-29 12:57:45.81 Server This instance of SQL Server last reported using a process ID of 2616 at 2013-08-29 12:42:20 (local) 2013-08-29 04:42:20 (UTC). This is an informational message only; no user action is required.
2013-08-29 12:57:45.81 Server Registry startup parameters:
2013-08-29 12:57:45.81 Server -d D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-08-29 12:57:45.81 Server -e D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-08-29 12:57:45.81 Server -l D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-08-29 12:57:45.81 服务器 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-08-29 12:57:45.81 服务器 Detected 4 CPUs. This is an informational message; no user action is required.
2013-08-29 12:57:45.92 服务器 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-08-29 12:57:45.95 服务器 Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2013-08-29 12:57:46.98 服务器 Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2013-08-29 12:57:46.98 服务器 Database Mirroring Transport is disabled in the endpoint configuration.
2013-08-29 12:57:47.00 spid4s Starting up database 'master'.
2013-08-29 12:57:47.07 spid4s SQL Trace ID 1 was started by login "sa".
2013-08-29 12:57:47.07 spid4s Starting up database 'mssqlsystemresource'.
2013-08-29 12:57:47.09 spid4s 错误: 17207，严重性: 16，状态: 1。
2013-08-29 12:57:47.09 spid4s FCB::Open: Operating system error 5(拒绝访问。) occurred while creating or opening file 'D:\Program Files\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
2013-08-29 12:57:47.09 spid4s 错误: 17204，严重性: 16，状态: 1。
2013-08-29 12:57:47.09 spid4s FCB::Open failed: Could not open file D:\Program Files\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf for file number 1. OS error: 5(拒绝访问。).
2013-08-29 12:57:47.09 spid4s 错误: 5120，严重性: 16，状态: 101。
2013-08-29 12:57:47.09 spid4s 无法打开物理文件 "D:\Program Files\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf"。操作系统错误 5:"5(拒绝访问。)"。
2013-08-29 12:57:47.09 spid4s 错误: 17207，严重性: 16，状态: 1。
2013-08-29 12:57:47.09 spid4s FileMgr::StartLogFiles: Operating system error 2(系统找不到指定的文件。) occurred while creating or opening file 'D:\Program Files\MSSQL.1\MSSQL\DATA\mssqlsystemresource.ldf'. Diagnose and correct the operating system error, and retry the operation.
2013-08-29 12:57:47.09 spid4s 文件激活失败。物理文件名称'D:\Program Files\MSSQL.1\MSSQL\DATA\mssqlsystemresource.ldf'可能不正确。
2013-08-29 12:57:47.09 spid4s 错误: 945，严重性: 14，状态: 2。
2013-08-29 12:57:47.09 spid4s 由于文件不可访问，或者内存或磁盘空间不足，所以无法打开数据库 'mssqlsystemresource'。有关详细信息，请参阅 SQL Server 错误日志。
2013-08-29 12:57:47.09 spid4s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
[解决办法]
操作系统错误，数据库文件找不到或不能打开，你尝试一下修复安装
[解决办法]
#1.确定是否：内存或磁盘空间不足
#2.找一个相同版本的SQL SERVER，相同目录下，找到：mssqlsystemresource.mdf，mssqlsystemresource.ldf，两个文件，停止SQL SERVER服务，COPY过来覆盖一下。
这两个文件是系统文件，里面存放大部分系统的存储过程，函数，等对象的定义。
[解决办法]
必须先停掉sql server的，否则你无法将那两个文件(mssqlsystemresource.mdf，mssqlsystemresource.ldf)拷贝出来的
覆盖后再启动sql server
[解决办法]
根据提示，确认一下是否真的内存、磁盘空间不足，再看一下sql对应目录、文件是否正常，读写权限等
