SQL Server service not automatically starting (logon failure)

I just installed SQL Server 2012 on a machine. To run "SQL Server" as well as "SQL Server Agent" service I have created a domain account called SQLADMIN. This account is a service account and has no other rights like logon locally or
local administrator.
When the machine restarts, "SQL Server" service doesn't start automatically. When I click Start then it says "Logon Failure". Now if I simply enter the password again under tab "Log On" and then start service then it starts. Why
doesn't it start automatically?

Hello,
Please read the following article about permissions required by service accounts.
http://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Serv_Perm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
I do not see any special permission that is needed as per the article. For e.g. as per below:
SQL Server Service
Permissions granted by SQL Server Setup
SQL Server Database Engine:
(All rights are granted to the per-service SID. Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName.)
Log on as a service (SeServiceLogonRight)
Replace a process-level token(SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process(SeIncreaseQuotaPrivilege)
Permission to start SQL Writer
Permission to read the Event Log service
Permission to read the Remote Procedure Call service
I am running Database Engine service as DOMAIN\SQLADMIN account which can Log On As A Service. Other 3 permissions mentioned in article are not given so let me assign it and then see how it goes.
Could this issue be due to some domain policy? Because there is another SQL Server machine which shows same behaviour.

Similar Messages

Automatically start SQL Agent service after SQL Server service fails and starts.

Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server Service won't start on SQL Server 2008

Hi everyone,
I'm having trouble starting SQL Server service after stopping and starting the service. Before this happened, I created a Stored Procedure for marking all tables at once along with a maintenance plan for differential backup on all my databases based on the
recommendation from this link, http://msdn.microsoft.com/en-us/library/ms253070.aspx.
When I realized that the differential backup failed with some databases displaying (Restoring...) post-fix to the database name, I decided to stop SQL Server service and start it up. That is when I won't be able to start the service again.
Is there a fix for starting the SQL Server service? Any help is very much appreciated.
Additional information:
- With administrator permission granted.
- Service Pack 1 for SQL Server 2008 installed.
- Using default database instance.
- Tried C:\Program Files\Microsoft SQL Server\MSSQL.....\Binn>net start MSSQLSERVER /T3608 ( return msg: System error 5 has occurred. Access is denied.
- When I start SQL Server service, I keep getting this dialog msg:
"Windowns could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1814."
The event log does not explain or provide any hint on how to fix the problem.
- Log msg:
2010-07-22 10:30:25.09 Server      (c) 2005 Microsoft Corporation.
2010-07-22 10:30:25.09 Server      All rights reserved.
2010-07-22 10:30:25.09 Server      Server process ID is 6076.
2010-07-22 10:30:25.10 Server      Authentication mode is MIXED.
2010-07-22 10:30:25.10 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2010-07-22 10:30:25.11 Server      This instance of SQL Server last reported using a process ID of 5708 at 7/21/2010 3:27:01 PM (local) 7/21/2010 10:27:01 PM (UTC). This is an informational message only; no user action is required.
2010-07-22 10:30:25.11 Server      Registry startup parameters:
    -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2010-07-22 10:30:25.14 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-07-22 10:30:25.14 Server      Detected 4 CPUs. This is an informational message; no user action is required.
2010-07-22 10:30:25.23 Server      Using locked pages for buffer pool.
2010-07-22 10:30:25.43 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.
2010-07-22 10:30:25.73 Server      Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2010-07-22 10:30:25.81 spid7s      Starting up database 'master'.
2010-07-22 10:30:26.14 spid7s      CHECKDB for database 'master' finished without errors on 2010-07-19 21:15:02.823 (local time). This is an informational message only; no user action is required.
2010-07-22 10:30:26.18 spid7s      Resource governor reconfiguration succeeded.
2010-07-22 10:30:26.18 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.18 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.19 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-07-22 10:30:26.28 spid7s      SQL Trace ID 1 was started by login "sa".
2010-07-22 10:30:26.29 spid7s      Starting up database 'mssqlsystemresource'.
2010-07-22 10:30:26.31 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-07-22 10:30:26.43 spid10s     Starting up database 'model'.
2010-07-22 10:30:26.43 spid7s      Server name is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2010-07-22 10:30:26.47 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-07-22 10:30:26.47 spid10s     Error: 927, Severity: 14, State: 2.
2010-07-22 10:30:26.47 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
2010-07-22 10:30:26.59 spid10s     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.
2010-07-22 10:30:26.59 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Hello,
Could you please copy the model.mdf and modellog.ldf from
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Templates
To
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
Rebuilding the system databases you will lose lose logins, jobs, SSIS packages. You may have to restore or attach user databases.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Service can't start.

I was try start SQL Server Service in SQL Server Configuration Manager and it prompt out error 'The request failed or the service did not respond in a timely fashion.Consult the event log or other applicable error logs for details.'
I was try set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control ServicePipeTimeout
value to decimal 180000.
I try also change the service account to local system but it prompt WMI error.
But still failed to start the service.
Could anyone help me? Thanks in advance.

I check from event viewer it showing 30++ error
I post some error here:
Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Sqm\iesqmdata0.sqm to location \\?\C:\Users\MSSQL$SQLEXPRESS.NT Service\AppData\Local\Microsoft\Windows\Temporary Internet Files\Sqm\iesqmdata0.sqm. This error may be caused by network problems or insufficient security rights.
Windows cannot find the local profile and is logging
you on with a temporary profile. Changes you make to this profile will be lost when you log off.
Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Sqm\iesqmdata0.sqm to location \\?\C:\Users\TEMP.NT Service.001\AppData\Local\Microsoft\Windows\Temporary Internet Files\Sqm\iesqmdata0.sqm. This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
Windows cannot log you on because your profile cannot
be loaded. Check that you are connected to the network, and that your network is functioning correctly.
DETAIL - Only part of a ReadProcessMemory or WriteProcessMemory
request was completed.
**I
was using administrator account.

SQl Server service failed to start error 1053

Hi All
During installing MS SQL server 2005 ,i am getting the error like
Could not start SQL server Service.
When trying to start the service manually ,getting error like service could nto start in a timely fashion.
We are using Windows 2003 SP2 with 12 CPUs .
This is a domaininstallation ,the accounts are present ,but when tried with local installation also ,got the same error.
Is this article is of any use
http://support.microsoft.com/kb/954835
Does there any issue with Win 2003 SP2 and SQL Server domain installationwiht named instance.
Pls let me know if you have any suggestions.
Regards
Ajay

Hi Ajay
try this:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3.In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER.
4.Right-click ServicesPipeTimeout, and then click Modify.
5.Click Decimal, type 60000, and then click OK.
This value represents the time in milliseconds before a service times out.
6.Restart the computer.
Let me know if it helps
Rohit

SQL Server service not starting

Hi,
In my environment we have configured SQL server clustering. Currently we are getting the following error and the service is not starting up.
ERROR: TDSSNIClient initialization failed with error 0x2741, status code 0x1.

Hi winoa,
According to your description, you come across the error that TDSSNIClient initialization failed with error 0x2741. Please help to post the full error message from both SQL Server error log and cluster log for further analysis.
Based on my research, this issue could happen due to setting up SQL Server failover cluster over different subnets using these three SQL Server versions(SQL Server 2005, SQL Server 2008, or SQL Server 2008 r2), hardware issue, or that disk and network name
are offline.
Please pay attention to the points below to troubleshoot your issue.
•If you set up SQL Server failover cluster over multiple subnets using the versions of SQL Server 2005, SQL Server 2008 or SQL Server 2008 r2, please make all the nodes in the same subnet, since SQL Server multi-subnet failover cluster is not supported among
those three versions of SQL Server. If possible, you could use the later versions (SQL Server 2012 or 2014) for SQL Server multi-subnet failover cluster.
• Make sure that disk and network name are online.
Regards,
Michelle Li

Reporting Services not automatically starting. System event log 7009, Application event: 18456

For the past month (since Oct 11,2012) reporting services (SSRS 2008R2) is not starting after the server is rebooted. The service is set to automatically start and starts manually without a problem. The system event log contains the following error:
Event ID 7009: A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.
SQL logs :
The SQL logs has many "Event 18456 Login Failed, State 38" errors when the database engine starts. I assume clients conections are failing because the databases aren't online yet. None of these 18456 errors coorespond to the account reporting services
runs under.
The SQL logs indication Event 7009 occures before the "ReportingServer" database is online so im assuming there is a dependancy but I don't know how to avoid this.
This problem is occuring on a number of our servers running SSRS (if not all)
Any ideas?
Paul

Hi A141695,
For Event ID 7009, you can try to do the steps below to resolve it.
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry subkey:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    3. Right-click Control, point to New, and then click DWORD Value.
    4. In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
    5. Right-click ServicesPipeTimeout, and then click Modify.
    6. Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.
For example, to wait 60 seconds before the service times out, type 60000.
Quit Registry Editor, and then restart the computer. For more information about it, please see:
http://www.sqlservercentral.com/Forums/Topic850540-1550-1.aspx#bm851211
http://myitforum.com/myitforumwp/2012/08/22/configmgr-2012-sms_srs_reporting_point-component-failure/
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.

SQL Server could not be started: Reason- SqL Server Agent must be able to connect to SQL servwe As sytem Administrator

There is no http:// on one of the tool bars that allow me to log on. Warning appears: SQL Server Agent must be able to connect to SQL server as System Administrator. We bought this computer at a flee market and it already had names as administrators on it. How can I change my name to be administrator?

There is no http:// on one of the tool bars that allow me to log on. Warning appears: SQL Server Agent must be able to connect to SQL server as System Administrator. We bought this computer at a flee market and it already had names as administrators on it. How can I change my name to be administrator?

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,
error: 40 - Could not open a connection to SQL Server)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hello,
Make sure your SQL Server service is started.
Make sure TCP\IP and names pipes protocol is enabled
Make sure you have made an exception in firewall for SQL Server connection
Make sure SQL Server browser service is enabled
Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sql server will not start - Database 'model' cannot be opened. It is in the middle of a restore.

Sql server service will not start after server reboot:
2009-08-13 14:15:43.94 spid7s      SQL Trace ID 1 was started by login "sa".
2009-08-13 14:15:43.97 spid7s      Starting up database 'mssqlsystemresource'.
2009-08-13 14:15:43.97 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-08-13 14:15:44.30 Server      A self-generated certificate was successfully loaded for encryption.
2009-08-13 14:15:44.30 spid7s      Server name is 'WIN-37R9WFWAJIB\MSDB1'. This is an informational message only. No user action is required.
2009-08-13 14:15:44.32 spid10s     Starting up database 'model'.
2009-08-13 14:15:44.32 Server      Server is listening on [ 'any' <ipv6> 49167].
2009-08-13 14:15:44.33 Server      Server is listening on [ 'any' <ipv4> 49167].
2009-08-13 14:15:44.33 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSDB1 ].
2009-08-13 14:15:44.33 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-08-13 14:15:44.35 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2009-08-13 14:15:44.38 Server      Server is listening on [ ::1 <ipv6> 49168].
2009-08-13 14:15:44.38 Server      Server is listening on [ 127.0.0.1 <ipv4> 49168].
2009-08-13 14:15:44.38 Server      Dedicated admin connection support was established for listening locally on port 49168.
2009-08-13 14:15:44.39 spid10s     Error: 927, Severity: 14, State: 2.
2009-08-13 14:15:44.39 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
2009-08-13 14:15:44.49 spid10s     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.
2009-08-13 14:15:44.50 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informa
there is plenty of room on the server, so i dont think its a disk space issue. i am able to start the service as such:
C:\Users\Administrator>net start MSSQL$MSDB1 /c /m /T3608
The SQL Server (MSDB1) service is starting.
The SQL Server (MSDB1) service was started successfully
sqlcmd -e
1> select name, status from sysdatabases;
2> go
select name, status from sysdatabases;
name
                                                 status
master
                                                       65544
tempdb
                                                       65544
model
                                                       65568
msdb
                                                  1073807368
SS_DBA_Dashboard
                                                  1073807368
(5 rows affected)
model is in RESTORING state and I dont know how to fix it. I am running simple backups, so I have a somewhat recent backup of model.bak but when I attempt to restore it I get an error:
1> restore database model
2> go
restore database model
Msg 3112, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
Cannot restore any database other than master when the server is in single user
mode.
Msg 3013, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
RESTORE DATABASE is terminating abnormally.
other forums suggest manually updating the status column but i dont know if my syntax is wrong or it just cant be done in sql server 2008:
1> begin transaction
2> update sysdatabases set status=16 where name='model'
3> ;
4> go
begin transaction
update sysdatabases set status=16 where name='model'
Msg 4406, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 2
Update or insert of view or function 'sysdatabases' failed because it contains a
derived or constant field.
1>
yet another forum suggested taking a cleanly shut down model.mdf and model.ldf from another sql server 2008 instance and placing those in the data directory while moving the 'restoring' ones to a backup location. this didnt work either. any help is appreciated im new to sql server and this is very frustrating! thanks in advance!

I have the same issue on SQL Server 2008R2, after a server reboot, but none of the NET START commands or command line attempts are successful to start the Service.
NET START command results in "Access Denied" "System Error 5" and the Command line attempts result in
Server      Error: 17058, Severity: 16, State: 1.
Server      initerrlog: Could not open error log file ''.
Any help?
SQL Error log file:
2011-03-29 16:50:49.40 Server      (c) Microsoft Corporation.
2011-03-29 16:50:49.40 Server      All rights reserved.
2011-03-29 16:50:49.40 Server      Server process ID is 7292.
2011-03-29 16:50:49.40 Server      System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T710'.
2011-03-29 16:50:49.40 Server      Authentication mode is MIXED.
2011-03-29 16:50:49.40 Server      Logging SQL Server messages in file 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-03-29 16:50:49.40 Server      This instance of SQL Server last reported using a process ID of 7448 at 3/29/2011 4:30:06 PM (local) 3/29/2011 8:30:06 PM (UTC). This is an informational message only; no user action is required.
2011-03-29 16:50:49.40 Server      Registry startup parameters:
-d E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 4616
2011-03-29 16:50:49.42 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-29 16:50:49.42 Server      Detected 24 CPUs. This is an informational message; no user action is required.
2011-03-29 16:50:49.84 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.
2011-03-29 16:50:49.84 Server      Lock partitioning is enabled. This is an informational message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.89 spid9s      Starting up database 'master'.
2011-03-29 16:50:49.95 spid9s      CHECKDB for database 'master' finished without errors on 2011-03-18 08:46:34.257 (local time). This is an informational message only; no user action is required.
2011-03-29 16:50:49.95 spid9s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-03-29 16:50:49.97 spid9s      SQL Trace ID 1 was started by login "sa".
2011-03-29 16:50:49.97 spid9s      Starting up database 'mssqlsystemresource'.
2011-03-29 16:50:49.99 spid9s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-03-29 16:50:50.20 spid13s     Starting up database 'model'.
2011-03-29 16:50:50.20 spid9s      Server name is 'XXXX'. This is an informational message only. No user action is required.
2011-03-29 16:50:50.21 Server      The certificate [Cert Hash(sha1) "C41DC20703F049763778AC2842C3C8A3A2C6EED4"] was successfully loaded for encryption.
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv6> 1433].
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv4> 1433].
2011-03-29 16:50:50.21 Server      Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2011-03-29 16:50:50.21 Server      Server named pipe provider is ready to accept connection on [
\\.\pipe\sql\query ].
2011-03-29 16:50:50.21 Server      Server is listening on [ ::1 <ipv6> 1434].
2011-03-29 16:50:50.21 spid13s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-03-29 16:50:50.21 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-03-29 16:50:50.21 spid13s     Error: 927, Severity: 14, State: 2.
2011-03-29 16:50:50.21 spid13s     Database 'model' cannot be opened. It is in the middle of a restore.
2011-03-29 16:50:50.21 Server      Dedicated admin connection support was established for listening locally on port 1434.
2011-03-29 16:50:50.22 spid13s     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.
2011-03-29 16:50:50.22 spid13s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Sql server service wont start after disabling TLS 1.0 and SSL 3.0 on windows

We have been hardening our servers for some time now and recently we disabled SSL 3.0 because of the poodle attack. When I did this on one of our test servers SQL Server failed to start up after the restart.
I have been able to reproduce this on Windows Server 2012 and Windows 7 by disabling TLS 1.0 and SSL 3.0 through the registry. I am using SQL Server 2012 on the server machine. On my windows 7 machine sql server 2012 and sql server 2005 will not start with
those disabled.
These are the event log errors I get:
Application Logs:
(28/10/2014 8:38:54 AM) SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
(28/10/2014 8:38:54 AM) Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
(28/10/2014 8:38:54 AM) TDSSNIClient initialization failed with error 0x80090331, status code 0x1.
(28/10/2014 8:38:54 AM) TDSSNIClient initialization failed with error 0x80090331, status code 0x80.
System Logs:
(28/10/2014 8:38:54 AM) The SQL Server (MSSQLSERVER) service terminated with service-specific error %%-2146893007.
(28/10/2014 8:38:54 AM) A fatal error occurred while creating an SSL server credential. The internal error state is 10013.
Done anyone know have we can keep SSL 3.0 and TLS 1.0 disabled and get SQLServer server to start?

Hi Don,
I already have TLS 1.0 Disabled to prevent the BEAST exploit. So the values I have for:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Server
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Client
Both have enabled set to ("Enabled"=dword:00000000).
If change both of these back to ("Enabled"=dword:00000001)
to enable TLS 1.0, and restart then SQLServer is able to start again. But we are now vulnerable to the BEAST attack once again.
If I keep server enabled and disable the client or vice versa and restart. Then SQLServer starts but I
am unable to connect to it. When I check the Event logs I get the same errors as my original past.
With your last post, do you mean to backup SCHANNEL and delete it so it gets recreated? If that is the case it will probably work because if I re enable SSL 3.0 or TLS 1.0 from here it fix's the issue, but I then I won't have the exploits patched and
we need this for some of our customers.
This is my SCHANNEL Export:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Client]
"DisabledByDefault"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
"Enabled"=dword:00000000

ADFS 2.0 service does not automatically start after reboot

Hello,
We have two ADFS 2.0 servers in a farm. Any time these servers reboot, the ADFS service does not automatically start, even though the service is set to auto start. If I manually start the service it starts within 10 seconds.
The error in the logs show:
A timeout was reached (30000 milliseconds) while waiting for the AD FS 2.0 Windows Service service to connect.
The AD FS 2.0 Windows Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
But after the reboot is completed, I can manually start the service with no problems. Again, this ONLY happens on restart. I've searched the forums and found potential solutions for people who have consistent issues with starting ADFS every time.
Any ideas?

UPDATE - I built a 3rd ADFS server and was unable to reproduce the problem, until...
I went in to the service properties of ADFS and saw that even though I specified a Log On As account during the ADFS wizard, it changed itself back to "Network Service". I re-entered our ADFS service account username and password, it was
accepted, and I rebooted. On the next reboot, the service did not start automatically (with the same errors as the other ADFS servers), but I was able to manually start it.
I then went to the original ADFS server having the problem, switched it to use "Network Service", rebooted, and the service started up properly on reboot. I then changed it back to the named domain service account, and the issue came right
back. There are no other errors in the System Log indicating a problem with anything else.
So my guess is that something is happening to prevent the service from starting with the named Domain account on server reboot. But what?

The specified credentials that were provided for the SQL Server service are not valid

after i enter account name and password for server configuration...the error appear...is it problem with acc name or password?help!!

Hi help933,
According to your description, when you use the Server Configuration page of the SQL Server Installation Wizard to assign login accounts to SQL Server services, you can
assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled.
For example, on Windows Vista and Windows Server 2008 ,most accounts are set to the default NETWORK SERVICE account.
For more information, see:
http://msdn.microsoft.com/en-us/library/cc281953.aspx
Also there is a similar issue about seivice account, you can review the following post.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c7139740-ab93-48c2-b357-31bb7935b83d/rc0-rs-installation-problem-the-credentials-you-provided-for-reporting-services-service-are?forum=sqlsetupandupgrade
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Cannot start SQL Server Service (SQLEXPRESS).

Cannot start SQL Server (SQLEXPRESS). When i tried to start the SQL Server Services, the warning: This request failed or the service did not respond in a timely fashion. Consult the event log or other application error logs for details.
I opened the Event Viewer, Error is shown as : An error occurred in the Service Broker / Database Mirroring transport manager. Error: 9694, Stare 27.

Here is the ERRORLOG
2015-03-16 11:20:30.50 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2015-03-16 11:20:30.50 Server (c) Microsoft Corporation.
2015-03-16 11:20:30.50 Server All rights reserved.
2015-03-16 11:20:30.50 Server Server process ID is 6816.
2015-03-16 11:20:30.50 Server System Manufacturer: 'LENOVO', System Model: '20C5A01K00'.
2015-03-16 11:20:30.50 Server Authentication mode is MIXED.
2015-03-16 11:20:30.50 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-03-16 11:20:30.50 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-03-16 11:20:30.50 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-03-16 11:20:30.50 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-03-16 11:20:30.64 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 11:20:30.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 11:20:30.64 Server Detected 7906 MB of RAM. This is an informational message; no user action is required.
2015-03-16 11:20:30.64 Server Using conventional memory in the memory manager.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 27.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server Error: 9643, Severity: 16, State: 1.
2015-03-16 11:20:30.75 Server An error occurred in the Service Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 30.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server SQL Server Audit failed to record the SERVER SHUTDOWN action.

SQL Server service not automatically starting (logon failure)

Similar Messages

Maybe you are looking for