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

Similar Messages

CF Mx6 admin & service wont start after successful new install on XP with IIS

I just installed a fresh copy of Coldfusion mx 6 on my
windows XP running IIS . After installation, the CF Administrator
didnt come up(
Http://Localhost:8500/CFDIE/Adminstartor.....whatever)-
loads on the browser but doesnt load the admin page.
Further attempts to manually restart the coldfusion server
from Control Panel>Adminstrative tools>services> prooved
abortive as it refused to start.
Please can anyone help me out there?
What aint I doing right?

thanks for reply
but my firewall is not on and the coldfusion server service
aint starting whiles the other two services(ODBC etc) are running
smooth.
cant afford to mess up my internet connection settings cos
it would warrant paying a visit to my ISP office with my PC . its a
mobile CDMA wireless box.
pls help or i ll drop CFM for PHP
chow

Windows 2008 R2 - Error 2 Server Service wont start

He
We tried to start the Server Service on windows 2008 R2 but it wont start error: 2. While we check the service dependency we are unable to see the "SMB 1 xxx Driver" instead it is having name SRV.
so how to restore the service back to the original state please let us know.

Hi SPV4645,
The following similar thread solution may work for your case.
Server service (lanmanserver) will not start
https://social.technet.microsoft.com/Forums/windowsserver/en-US/3316a5e0-fc2f-4300-917d-66e1527b4aa7/server-service-lanmanserver-will-not-start
Please also confirm the File and Printer Sharing for Microsoft Network driver has selected.
The related KB:
You receive a "The server service is not started" error message when you try to add a user to a group in Windows XP
http://support.microsoft.com/en-us/kb/885859
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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

Help please PC wont start after i combined double sided and singlesided RAM

Can anyone help me please. I have a neo2 platinum board and 3200+ cpu. i used to have 2 X 512MB(double sided) ddr400 Ram PH brand. When i bought and added NCP brand 2 X 512MB(single sided) my PC wont start anymore. It just powers up for 1/2 a second then dies. I tried putting back my old RAM and resetting the BIOS but it still wont start.

thanks everyone i have isolated the problem...the culprit is the psu i have another problem though, after i bought a new psu, the vga card is not detected from time to time...i also get the BSOD upon exiting windows and I cannot access the BIOS, it just freezes after I press the DEL key.

User profile synchronization service wont start after SharePoint Service pack SP2

Hi
-Using SharePoint 2010 with 1 appserver and 2 frontend webservers on Service Pack2. (ms server 2008r2, SQLServer2008r2).
-Farmaccount has been set to local admin on all sp servers.
-Firstly, the User Profile Service Application runs fine and is started. Dont mix it with the User profile synchronization Service.
Prior to installing SP2 User profile service application and user profile synchronization service were running fine.
The first thing I did after the installation of SP2 was running the:
-psconfig -cmd upgrade -inplace b2b -wait
As SharePoint setup user (spadmin).
This ran fine on the 2 front end web servers.
However i got one fault on the Appserver:
I have also tried:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
which led to same resulting error.
So I tried to start the Use profile synchronization service as suggested manually by logging on with the Farmaccount, starting the user profile synchronization service through Central Administration. This led to Stuck on Starting status.
The windows services Forefront had status starting, then stopped.
One question:
Prior to starting the User profile synchronization service through Central Administration. What account and startup status should the 2 Forefront Windows Services have? (Automatic and local system?) or (Automatic and Farmaccount?) or (Disabled and Local
system?) or (Disabled and farmaccount?). Because i know that SharePoint UPA will provision these services though Central Administration. However what is the default state prior to starting the Synchronization service?
So i continue...
Since it was stuck on starting i stopped it with:
stop-SPServiceInstance -identity <upaSyncguid>
which gave me:
Stop-SPServiceInstance : An object of the type Microsoft.SharePoint.Administrat
ion.SPServiceInstanceJobDefinition named "job-service-instance-36bdf2ef-58f2-45
e5-8f78-ab75f646611a" already exists under the parent Microsoft.SharePoint.Admi
nistration.SPTimerService named "SPTimerV4". Rename your object or delete the
and i could fix with:
#Stop the stopping:
stsadm -o provisionservice -action stop -servicetype "Microsoft.Office.Server.Administration.ProfileSynchronizationService, Microsoft.Office.Server.UserProfiles,
Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename FIMSynchronizationService
I also removed the forefront certificate from personal - certificate store, as this is provisioned when user profile synchronization service is provisioned.
That set the Central Administration Status on the User profile synchronization Service to disabled. Fine.
Everytime i tried to start the user profile synchronization service (logged on as farmaccount), left it for 10-15 min and did iisreset and restart sharepoint timer service, and also tried rebooting the appserver. No change.
A thought, is it important to restart timer service and do iisreset on the two frontend servers after trying to start the user profile synchronization service on the appserver?
I'm getting to the point were i just want to delete the whole service application and set it up anew...
any tips will be greatly appreaciated.
brgs
Bjorn

You're very welcome, hope it helped, if not the I suggest you clear the configuration cache as follows.
The config cache is where config settings are stored locally on the Microsoft SharePoint server, so a SQL call isn’t required.
To clear the cache:
Stop the SP Timer service. To do this, follow these steps:
Click Start, point to Administrative Tools, and then click
Services.
Right-click SharePoint 2010 Timer, and then click Stop.
Close the Services console.
On the computer that is running Microsoft SharePoint Server 2010 and on which the Central Administration site is hosted, click
Start, click Run, type explorer, and then press ENTER.
In Windows Explorer, locate and then double-click the following folder:
%SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID
Notes
The %SystemDrive% system variable specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
The GUID placeholder specifies the GUID folder. There may be more than one of these.
The ProgramData folder may be hidden. To view the hidden folder, follow these steps:
On the Tools menu, click Folder Options.
Click the View tab.
In the Advanced settings list, click Show hidden files and folders under
Hidden files and folders, and then click OK.
You can also simply type this directly in the path if you do not want to show hidden files and folders.
Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you
do NOT delete the GUID folder and the Cache.ini file that is located in the GUID folder.
Double-click the Cache.ini file.
On the Edit menu, click Select All.
On the Edit menu, click Delete.
Type 1, and then click Save on the
File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
On the File menu, click Exit.
Start the Timer service. To do this, follow these steps:
Click Start, point to Administrative Tools, and then click
Services.
Right-click SharePoint 2010 Timer, and then click Start.
Close the Services console.
Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.
BRGS
Mishagri

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 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

SQL Server Service Account - Domain Account - WMI Provider Error - 0x80092004

Hi,
if I try to use an domain account for SQL service start using SQL configuration Manager I receive the error
WMI Provider Error - 0x80092004
in Popup Window and in Eventlog 5 Error Events from Source MSSQLSERVER:
26014:
Unable to load user-specified certificate [Cert Hash(sha1) "BA78B5DBF93CCD7EFA1860C99B0D6141D480199A"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for
Use by SSL" in Books Online.
17182:
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. "
17182:
TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
17826:
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.
17120:
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
After I put the account in local administrator group the service starts up.
I want to use the lowest privileges. Do I really need the SQL server service account in local administrator group? How to fix the error?
thanks

Hi baschuel,
It is recommended to run SQL Server service by using the lowest possible user rights and it is supported to use a domain account instead of an account from local Administrators group to configure SQL Server service. According to your error messages, the
issue could be due to that the incorrect certificate is used, or the domain account has no access to the Crypto folder(C:\ProgramData\Microsoft\Crypto). To troubleshoot the issue, you could follow the two solutions below.
1.Import the correct certificate following the steps in the article:
http://windows.microsoft.com/en-hk/windows/import-export-certificates-private-keys#1TC=windows-7
2.Grant the domain account full access to the Crypto folder.
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"
The system logs reads:
Mar 29 22:06:25 server servermgrd[82]: servermgr_web: Error Domain=XSServerFoundationErrorDomain Code=4 "Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass
          ." UserInfo=0x7fc547901080 {NSLocalizedDescription=Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass

To check the local network for some of the common configuration problems, launch Terminal.app and issue the following diagnostic command:
sudo changeip -checkhostname
That'll report some local configuration information and then either no errors detected and no changes required, or it'll point to whatever configuration errors or issues it might detect. That doesn't catch everything, but it catches the common errors.
FWIW, 192.168.0.0/24 and 192.168.1.0/24 are poor choices for the local network, as VPNs are based on IP routing and IP routing gets tangled when the same subnet is used on both ends of the VPN. 192.168.0.0/24 and 192.168.1.0/24 are near ubiquitous in home networks and coffee shops.

SQL Server Integration Service wont start.

If integration services doesnt come online where should we check, apart from Event viewer, SQL Server Error logs and SQL Server Agent logs??
The below error is what I see in Event viewer.
Timeout (30000 milliseconds) waiting for the SQL Server Integration Services service to connect.
The SQL Server Integration Services service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
This doesnt tell me the real problem. The service account is Windows AD account. The other SQL Server services running under same account is up and running. Could you guys please help me in troubleshooting?

Hi Shanoof,
Please go through below links, hope these helps:
http://blogs.msdn.com/b/ajaykumarks/archive/2010/11/13/a-short-story-about-the-quot-ssis-service-that-failed-to-start-quot.aspx
http://biatlink.wordpress.com/2013/04/29/sql-server-request-failed-or-the-service-did-not-respond-in-a-timely-fashion

Having issues with getting SQL Server Express to start services and run.

Good afternoon everyone,
I have been working on a 2012 R2 server getting ready to move databases to new hardware. I had SQL Server Express 2008 R2 running on this server with no issues. I was handed another software package that ran SQL Express 2012 and had to for compatibility
reasons. I have had multiple versions run on Server 2012 before with no issues. This time, not so lucky. When the installer from the updated package put on SQL Express 2012 it completed with errors ( error log posted at the end of post) and
would not allow me to run software. I then tried the db that I had installed on 2008 R2 and it also gave the same error as the 2012 version. IN basic terms the required services attempted to start and shut back down again. I have received
Error 1068 about database handles and error %%945. I know this db has plenty of space and the permissions were added for the Admin account to access both db's. I then uninstalled both versions and tried again, with the same errors listed when
I tried to start the services. I am thinking that a clean install would fix the issue however I am not certain what files/folders/reg entries need to be deleted or modified. I have researched all the errors I can find, however I am very
new with SQL anything so I know I am missing something. I also do not have an "E:" drive on this server (not sure why it is going there). Input would be very welcome as I am not certain where to go from here.
Thanks,
Matt
Error Log follows, server and domain names have been blacked out with ****.
2015-04-15 11:57:55.16 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-04-15 11:57:55.16 Server (c) Microsoft Corporation.
2015-04-15 11:57:55.16 Server All rights reserved.
2015-04-15 11:57:55.16 Server Server process ID is 4104.
2015-04-15 11:57:55.16 Server System Manufacturer: 'HP', System Model: 'ProLiant ML350p Gen8'.
2015-04-15 11:57:55.16 Server Authentication mode is WINDOWS-ONLY.
2015-04-15 11:57:55.16 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-04-15 11:57:55.17 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required.
2015-04-15 11:57:55.17 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-04-15 11:57:55.17 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-04-15 11:57:55.48 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-04-15 11:57:55.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-04-15 11:57:55.48 Server Detected 8157 MB of RAM. This is an informational message; no user action is required.
2015-04-15 11:57:55.48 Server Using conventional memory in the memory manager.
2015-04-15 11:57:55.68 Server This instance of SQL Server last reported using a process ID of 7840 at 4/15/2015 11:57:47 AM (local) 4/15/2015 3:57:47 PM (UTC). This is an informational message only; no user action is required.
2015-04-15 11:57:55.68 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-04-15 11:57:55.69 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.
2015-04-15 11:57:55.72 Server Software Usage Metrics is disabled.
2015-04-15 11:57:55.73 spid5s Starting up database 'master'.
2015-04-15 11:57:55.79 spid5s 20 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.79 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.80 Server CLR version v4.0.30319 loaded.
2015-04-15 11:57:55.86 spid5s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-04-15 11:57:55.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-04-15 11:57:55.91 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.91 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.94 spid5s SQL Trace ID 1 was started by login "sa".
2015-04-15 11:57:55.94 spid5s Server name is '********\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-04-15 11:57:55.96 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2015-04-15 11:57:55.96 spid5s Starting up database 'msdb'.
2015-04-15 11:57:55.96 spid9s Starting up database 'mssqlsystemresource'.
2015-04-15 11:57:55.96 spid5s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:55.96 spid5s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:55.96 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:55.96 spid5s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:55.96 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-04-15 11:57:55.99 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-04-15 11:57:56.02 spid12s A self-generated certificate was successfully loaded for encryption.
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv6> 53345].
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv4> 53345].
2015-04-15 11:57:56.03 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-04-15 11:57:56.03 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-04-15 11:57:56.04 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-04-15 11:57:56.04 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been
manually registered.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:53345 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure
to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually
registered.
2015-04-15 11:57:56.09 spid9s Starting up database 'model'.
2015-04-15 11:57:56.10 spid9s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:56.10 spid9s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:56.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:56.10 spid9s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:56.10 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-04-15 11:57:56.10 spid9s Error: 945, Severity: 14, State: 2.
2015-04-15 11:57:56.10 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-04-15 11:57:56.10 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
Service it leads to Some other process failures.
RehaanKhan. M

After all the Errors, When I am restarting the SQL Server its working correctly.
Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
The following are the Errors i got connecting to SQl Server.
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Error-2:
Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303) OLE DB provider
"Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412). The step failed.
After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
for to fix above error i have followed the instructions in the following link,
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
Thank you.
RehaanKhan. M

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

I Cant find Sql Server 2014 express edition after installing it. How do I start the program

Hello,
I have Installed Sql Server 2014 Express edition and downloaded the AdventureWorks 2014 database and Back up files.
I cannot find an Icon for the Sql Server on my Desktop to start the Sql program. There is only an icon for the Server Installation Center.
How do I start the Sql server. I tried opening the AdventureWorks Database but I cant open it.
Thank you

Thanks Shanky
When I installed Sql I chose Windows Login. After Installing I logged into Sql server using windows account. Should I have chosen an Sql account instead.
Hi,
Its is Ok if you have chosen windows Login. But it should be part of local administrator. I assume you know how to check
Is it not a security risk having to run Sql server as an administrator when using windows account or sql account.
Yes it is but at this point where I guess only you would be using and to get around with problem which you are facing. its recommended to run SQL server service with least privileged domain account. If you wan to read more see
this link
How do I make sure the account with which SQL Server service is running has full permission on folder where adventure works mdf and ldf files are located.
Please make a habit to search on net it is filled with lot of information.
This link would help.
Locate the folder on drive where AD mdf and ldf file reside. Right click on folder select properties and then select security tab. Click on add and then type account name and search and add it
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

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

Similar Messages

Maybe you are looking for