September 13, 2015 at 12:24 pm
I have a Dell PC, Win 7 Prof, with Sql Server 2014 Express and VS Express 2013, stand alone PC without network or remote connection.
I have always been able to start the SQL Server either through the connection button on the SQL Server Configuration Manager or through a connection string in Visual Studio. It has stopped, now I get a long error message:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) - The system cannot find the file specified"
Now I need first to start the SQL Server manually either through the properties in SQL Server Configure Manager or from an elevated command: 'Net Start MSSQLSERVER' or a Bat file from a VB.NET application. Then the SQL Server is running until I boot the PC next time. And a manual start of the SQL Server is needed again.
MSSQLSERVER Properties, Start Mode is Automatic, Log on as: Local Service
SQL Server Browser Propertie Log on as: Local Servise
After boot the following SQL services appears in the net start output:
SQL Server Browser
SQL Server Reporting Services /MSSQLSERVER)
SQL Server VSS Writer
I can find the logfile: C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles\ReportSercerService_09-13-2015_01_40.log 64 KB
but do not get any usefull information by reading in it.
If I shall send it to you, please tell my how, it is several pages long. To an e-maill address or shall I pick out the lines marked with error?
Please help, what can I do to get start of the SQL Server back to normal?
September 13, 2015 at 12:37 pm
Have you checked the [Install dir]\MSSQL\Log\ERRORLOG file?
September 13, 2015 at 3:07 pm
https://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/
I can find the logfile: C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles\ReportSercerService_09-13-2015_01_40.log 64 KB
but do not get any usefull information by reading in it.
Indeed. The reporting services error log is unlikely to contain any information as to why the database engine won't start.
Also, have you tried setting the service to Delayed Start?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 13, 2015 at 8:17 pm
Thank you Eirikur for the answer and Excuse for my mistake, in the Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG file I can see something is wrong. I will come back tomorrow
September 14, 2015 at 11:43 am
Thanks to Eirikur and GilaMonster for your answers, which has helped me a lot.
I thing the problem is solved. Now I have had 2 succesfully start of the SQL Server.
The key is GilaMonster answer Automatic (Delayed Start) of the Server.
For me to see, it is only possible through the Control Panel->Administrative Tools->Services area ? SQL Server (MSSQLSERVER).
In the search in log files I found this Warning, which occur in every shut down of the PC:
Log Name: Application Source: User Profile Service14-09-04:20:10 Event ID: 1530
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
2 user registry handles leaked from \Registry\User\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582:
Process 4052 (\Device\HarddiskVolume3\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582\Control Panel\International
Process 5232 (\Device\HarddiskVolume3\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\fdhost.exe) has opened key \REGISTRY\USER\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582\Control Panel\International
If it is not recommended to ignore it, I would like to know what to do with it
Thank again for your help.
September 14, 2015 at 11:53 am
zzzzcarl (9/14/2015)
Thanks to Eirikur and GilaMonster for your answers, which has helped me a lot.I thing the problem is solved. Now I have had 2 succesfully start of the SQL Server.
The key is GilaMonster answer Automatic (Delayed Start) of the Server.
For me to see, it is only possible through the Control Panel->Administrative Tools->Services area ? SQL Server (MSSQLSERVER).
In the search in log files I found this Warning, which occur in every shut down of the PC:
Log Name: Application Source: User Profile Service14-09-04:20:10 Event ID: 1530
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
2 user registry handles leaked from \Registry\User\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582:
Process 4052 (\Device\HarddiskVolume3\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582\Control Panel\International
Process 5232 (\Device\HarddiskVolume3\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\fdhost.exe) has opened key \REGISTRY\USER\S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582\Control Panel\International
If it is not recommended to ignore it, I would like to know what to do with it
Thank again for your help.
You are very welcome and thanks for the feedback.
Quick question, are you using the full text search? If not you might want to disable it.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy