[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.1

The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716)

Asked by evollic in SQL Server 2005

Tags: SQL Server 2005, MSSQLSERVER error 1814, error 1814 (0x716)

We are having an issue with our MSSQL server after a reboot that the these services won't autostart:
SQL Server (MSSQLSERVER)
SQL Server Agent (MSSQLSERVER)
SQL Server Analysis Services

Server info:
Windows Server 2003  R2 SP2
MSSQL Server 2005 9.0.3077
C: total size 35gb - 9gb free
D: total size 409gb - 98gb free

SQL Logs from startup:
Date,Source,Severity,Message
08/22/2009 12:06:38,spid9s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
08/22/2009 12:06:38,spid9s,Unknown,Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
08/22/2009 12:06:38,spid9s,Unknown,Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
08/22/2009 12:06:38,spid9s,Unknown,Error: 945<c/> Severity: 14<c/> State: 2.
08/22/2009 12:06:38,spid9s,Unknown,File activation failure. The physical file name "D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\modellog.ldf" may be incorrect.
08/22/2009 12:06:38,spid9s,Unknown,Unable to open the physical file "D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\modellog.ldf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
08/22/2009 12:06:38,spid9s,Unknown,Error: 5120<c/> Severity: 16<c/> State: 101.
08/22/2009 12:06:38,spid9s,Unknown,FCB::Open failed: Could not open file D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\modellog.ldf for file number 2.  OS error: 32(The process cannot access the file because it is being used by another process.).
08/22/2009 12:06:38,spid9s,Unknown,Error: 17204<c/> Severity: 16<c/> State: 1.
08/22/2009 12:06:38,spid9s,Unknown,FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\modellog.ldf'. Diagnose and correct the operating system error<c/> and retry the operation.
08/22/2009 12:06:38,spid9s,Unknown,Error: 17207<c/> Severity: 16<c/> State: 1.
08/22/2009 12:06:37,spid9s,Unknown,Unable to open the physical file "D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\model.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
08/22/2009 12:06:37,spid9s,Unknown,Error: 5120<c/> Severity: 16<c/> State: 101.
08/22/2009 12:06:37,spid9s,Unknown,FCB::Open failed: Could not open file D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\model.mdf for file number 1.  OS error: 32(The process cannot access the file because it is being used by another process.).
08/22/2009 12:06:37,spid9s,Unknown,Error: 17204<c/> Severity: 16<c/> State: 1.
08/22/2009 12:06:37,spid9s,Unknown,FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\model.mdf'. Diagnose and correct the operating system error<c/> and retry the operation.
08/22/2009 12:06:37,spid9s,Unknown,Error: 17207<c/> Severity: 16<c/> State: 1.
08/22/2009 12:06:37,spid5s,Unknown,Server name is 'ERIE'. This is an informational message only. No user action is required.
08/22/2009 12:06:37,spid9s,Unknown,Starting up database 'model'.
08/22/2009 12:06:36,spid5s,Unknown,The resource database build version is 9.00.3077. This is an informational message only. No user action is required.
08/22/2009 12:06:36,spid5s,Unknown,Starting up database 'mssqlsystemresource'.
08/22/2009 12:06:36,spid5s,Unknown,SQL Trace ID 1 was started by login "sa".
08/22/2009 12:06:35,spid5s,Unknown,CHECKDB for database 'master' finished without errors on 2009-08-21 09:41:02.033 (local time). This is an informational message only; no user action is required.
08/22/2009 12:06:35,spid5s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
08/22/2009 12:06:34,spid5s,Unknown,Starting up database 'master'.
08/22/2009 12:06:34,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
08/22/2009 12:06:33,Server,Unknown,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.
08/22/2009 12:06:31,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
08/22/2009 12:06:24,Server,Unknown,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.
08/22/2009 12:06:22,Server,Unknown,Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
08/22/2009 12:06:22,Server,Unknown,Detected 8 CPUs. This is an informational message; no user action is required.
08/22/2009 12:06:22,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
08/22/2009 12:06:22,Server,Unknown,-l D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\mastlog.ldf
08/22/2009 12:06:22,Server,Unknown,-e D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\LOG\ERRORLOG
08/22/2009 12:06:22,Server,Unknown,-d D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\master.mdf
08/22/2009 12:06:22,Server,Unknown,Registry startup parameters:
08/22/2009 12:06:22,Server,Unknown,This instance of SQL Server last reported using a process ID of 2252 at 8/22/2009 12:02:49 PM (local) 8/22/2009 4:02:49 PM (UTC). This is an informational message only; no user action is required.
08/22/2009 12:06:22,Server,Unknown,Logging SQL Server messages in file 'D:\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\LOG\ERRORLOG'.
08/22/2009 12:06:22,Server,Unknown,Authentication mode is MIXED.
08/22/2009 12:06:22,Server,Unknown,Server process ID is 2228.
08/22/2009 12:06:22,Server,Unknown,All rights reserved.
08/22/2009 12:06:22,Server,Unknown,(c) 2005 Microsoft Corporation.
08/22/2009 12:06:22,Server,Unknown,Microsoft SQL Server 2005 - 9.00.3077.00 (Intel X86) <nl/>      Dec 17 2008 15:19:45 <nl/>      Copyright (c) 1988-2005 Microsoft Corporation<nl/>      Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

I can see that if the first service doesn't start as to why the other won't since they are dependent on the first service. The real problem becomes that Citrix can't start/communicate and our Time Clocks fail due to SQL not being started. Any help would be appreciated.
[+][-]08/24/09 09:32 AM, ID: 25169971Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/24/09 09:35 AM, ID: 25169994Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/24/09 09:44 AM, ID: 25170090Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/24/09 11:08 AM, ID: 25170800Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]09/09/09 07:47 PM, ID: 25297087Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zone: SQL Server 2005
Tags: SQL Server 2005, MSSQLSERVER error 1814, error 1814 (0x716)
Sign Up Now!
Solution Provided By: BJLJ
Participating Experts: 2
Solution Grade: A
 
 
Loading Advertisement...
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625