Article ID: 929665
Article Last Modified on 10/15/2007
APPLIES TO
- Windows Internal Database
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.
CAUSE
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.
WORKAROUND
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>
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE 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.
Keywords: kbexpertiseadvanced kbtshoot kbsql2005setup kbprb KB929665
