各位高手：
今晚我的服务器在使用过程中，遭到了卡巴斯基杀毒软件的误杀MSSQL2005,当我把SQLSERVR.EXE加到卡巴信任的目录中之后，
MSSQL2005就不能启动了。我按照出错的消息号，查询到了微软官方的提供的解决方案，但是不知道怎么样来修复。
微软提供的解决方案的网址如下：
http://support.microsoft.com/kb/929665内容摘要如下:
You cannot start the SQL Server service after you install Active Directory on a Windows Server 2003-based member server or you run the DCPromo command on a Windows Server 2003-based domain controller
View products that this article applies to.
Article ID : 929665
Last Review : October 15, 2007
Revision : 1.1
SYMPTOMS
When a member server or a domain controller is running Microsoft Windows Server 2003 and has Windows Internal Database installed, you cannot start the Microsoft SQL Server service after you do one of the following: • Install Active Directory on the member server.
• Run the DCPromo command on the domain controller.
Additionally, the following error message is logged in Event Viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The Windows Internal Database (MICROSOFT##SSEE) service terminated with service-specific error 3417 (0xD59).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Back to the topCAUSE
This issue occurs because the required discretionary access control list (DACL) for some files has been deleted. The DACL is deleted when you install Active Directory on the member server or when you run the DCPromo command on the domain controller.
Back to the topWORKAROUND
To work around this issue, repair Windows Internal Database. To do this, run the following command line at a command prompt:
Msiexec <MSI_File_Name> CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <Log_File_Path>
Back to the topSTATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the topMORE INFORMATION
A message that resembles the following is logged in the SQL Server Errorlog file:2006-01-18 15:45:38.25 Server Microsoft SQL Server 2005 - 9.00.2025.00 (Intel X86)
Jan 16 2006 01:24:00
Copyright (c) 1988-2005 Microsoft Corporation
Embedded Edition (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1)2006-01-18 15:45:38.25 Server (c) 2005 Microsoft Corporation.
2006-01-18 15:45:38.25 Server All rights reserved.
2006-01-18 15:45:38.25 Server Server process ID is 1216.
2006-01-18 15:45:38.25 Server Logging SQL Server messages in file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
2006-01-18 15:45:38.25 Server This instance of SQL Server last reported using a process ID of 3152 at 1/18/2006 3:30:11 PM (local) 1/18/2006 11:30:11 PM (UTC). This is an informational message only; no user action is required.
2006-01-18 15:45:38.25 Server Registry startup parameters:
2006-01-18 15:45:38.26 Server -d D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
2006-01-18 15:45:38.26 Server -e D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
2006-01-18 15:45:38.26 Server -l D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2006-01-18 15:45:38.27 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-01-18 15:45:38.27 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-01-18 15:45:38.34 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.
2006-01-18 15:45:38.39 Server Database mirroring has been enabled on this instance of SQL Server.
2006-01-18 15:45:38.43 spid5s Starting up database 'master'.
2006-01-18 15:45:38.43 spid5s Error: 17207, Severity: 16, State: 1.
2006-01-18 15:45:38.43 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-18 15:45:38.43 spid5s Error: 17204, Severity: 16, State: 1.
2006-01-18 15:45:38.43 spid5s FCB::Open failed: Could not open file D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).
2006-01-18 15:45:38.43 spid5s Error: 5120, Severity: 16, State: 101.
2006-01-18 15:45:38.43 spid5s Unable to open the physical file "D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf". Operating system error 5: "5(Access is denied.)".
2006-01-18 15:45:38.44 spid5s Error: 17207, Severity: 16, State: 1.
2006-01-18 15:45:38.44 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-18 15:45:38.44 spid5s Error: 17204, Severity: 16, State: 1.
2006-01-18 15:45:38.44 spid5s FCB::Open failed: Could not open file D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).
2006-01-18 15:45:38.44 spid5s Error: 5120, Severity: 16, State: 101.
2006-01-18 15:45:38.44 spid5s Unable to open the physical file "D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf". Operating system error 5: "5(Access is denied.)".
transport is disabled or not configured.
Back to the top
--------------------------------------------------------------------------------微软提示说，出现这种情况，是系统执行了一个命令，或者误删了某些文件，
要求用如下命令行工具来修复：Msiexec <MSI_File_Name> CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <Log_File_Path>这条命令行，应该怎么样使用呀？
<MSI_File_Name> 指的是什么文件包？
<Log_File_Path> 指的的是什么文件路径？希望大家尽快回答，在此多谢先了。因为我的数据库是30G的大型数据，重装数据库是不现实的，那么多数据。
谢谢先！！
今晚我的服务器在使用过程中，遭到了卡巴斯基杀毒软件的误杀MSSQL2005,当我把SQLSERVR.EXE加到卡巴信任的目录中之后，
MSSQL2005就不能启动了。我按照出错的消息号，查询到了微软官方的提供的解决方案，但是不知道怎么样来修复。
微软提供的解决方案的网址如下：
http://support.microsoft.com/kb/929665内容摘要如下:
You cannot start the SQL Server service after you install Active Directory on a Windows Server 2003-based member server or you run the DCPromo command on a Windows Server 2003-based domain controller
View products that this article applies to.
Article ID : 929665
Last Review : October 15, 2007
Revision : 1.1
SYMPTOMS
When a member server or a domain controller is running Microsoft Windows Server 2003 and has Windows Internal Database installed, you cannot start the Microsoft SQL Server service after you do one of the following: • Install Active Directory on the member server.
• Run the DCPromo command on the domain controller.
Additionally, the following error message is logged in Event Viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The Windows Internal Database (MICROSOFT##SSEE) service terminated with service-specific error 3417 (0xD59).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Back to the topCAUSE
This issue occurs because the required discretionary access control list (DACL) for some files has been deleted. The DACL is deleted when you install Active Directory on the member server or when you run the DCPromo command on the domain controller.
Back to the topWORKAROUND
To work around this issue, repair Windows Internal Database. To do this, run the following command line at a command prompt:
Msiexec <MSI_File_Name> CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <Log_File_Path>
Back to the topSTATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the topMORE INFORMATION
A message that resembles the following is logged in the SQL Server Errorlog file:2006-01-18 15:45:38.25 Server Microsoft SQL Server 2005 - 9.00.2025.00 (Intel X86)
Jan 16 2006 01:24:00
Copyright (c) 1988-2005 Microsoft Corporation
Embedded Edition (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1)2006-01-18 15:45:38.25 Server (c) 2005 Microsoft Corporation.
2006-01-18 15:45:38.25 Server All rights reserved.
2006-01-18 15:45:38.25 Server Server process ID is 1216.
2006-01-18 15:45:38.25 Server Logging SQL Server messages in file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
2006-01-18 15:45:38.25 Server This instance of SQL Server last reported using a process ID of 3152 at 1/18/2006 3:30:11 PM (local) 1/18/2006 11:30:11 PM (UTC). This is an informational message only; no user action is required.
2006-01-18 15:45:38.25 Server Registry startup parameters:
2006-01-18 15:45:38.26 Server -d D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
2006-01-18 15:45:38.26 Server -e D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
2006-01-18 15:45:38.26 Server -l D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2006-01-18 15:45:38.27 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-01-18 15:45:38.27 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-01-18 15:45:38.34 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.
2006-01-18 15:45:38.39 Server Database mirroring has been enabled on this instance of SQL Server.
2006-01-18 15:45:38.43 spid5s Starting up database 'master'.
2006-01-18 15:45:38.43 spid5s Error: 17207, Severity: 16, State: 1.
2006-01-18 15:45:38.43 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-18 15:45:38.43 spid5s Error: 17204, Severity: 16, State: 1.
2006-01-18 15:45:38.43 spid5s FCB::Open failed: Could not open file D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).
2006-01-18 15:45:38.43 spid5s Error: 5120, Severity: 16, State: 101.
2006-01-18 15:45:38.43 spid5s Unable to open the physical file "D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf". Operating system error 5: "5(Access is denied.)".
2006-01-18 15:45:38.44 spid5s Error: 17207, Severity: 16, State: 1.
2006-01-18 15:45:38.44 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-18 15:45:38.44 spid5s Error: 17204, Severity: 16, State: 1.
2006-01-18 15:45:38.44 spid5s FCB::Open failed: Could not open file D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).
2006-01-18 15:45:38.44 spid5s Error: 5120, Severity: 16, State: 101.
2006-01-18 15:45:38.44 spid5s Unable to open the physical file "D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf". Operating system error 5: "5(Access is denied.)".
transport is disabled or not configured.
Back to the top
--------------------------------------------------------------------------------微软提示说，出现这种情况，是系统执行了一个命令，或者误删了某些文件，
要求用如下命令行工具来修复：Msiexec <MSI_File_Name> CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <Log_File_Path>这条命令行，应该怎么样使用呀？
<MSI_File_Name> 指的是什么文件包？
<Log_File_Path> 指的的是什么文件路径？希望大家尽快回答，在此多谢先了。因为我的数据库是30G的大型数据，重装数据库是不现实的，那么多数据。
谢谢先！！
应该可以搞定，偶经常也遇到过这样的缺少文件的故障。。