The SQL Server Express stopped working after restart system - sql

After restart system I try to connect to SQL Server Express, but I get an error; then I open services and try to start SQL Server (SQLEXPRESS) service manually but I get another error
The dependency service or group failed to start

Try the following steps:
Change the startup account of both the MSSQLSERVER and SQLServerAgent to use the local system account.
Restart the server.

Related

TFS Configuration Error

I am facing a problem that when i try to configure my TFS it show me the following Error Message
Error
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you are attempting to connect to is online, and that you have the required permissions to connect. If you are attempting to connect to the remote SQL Server instance, then verify that it is configured to allow remote connections, that TCP/IP protocol is both enabled and configured to use port 1433 (default), and that Windows Firewall does not block this port.
Check whether the SQL version is supported by the TFS version: https://www.visualstudio.com/en-us/docs/setup-admin/requirements#sql-server
Check the permission of the account that you use, and make sure it belongs to SysAdmin Server Role.
As #Daniel mentioned in comment, follow the troubleshooting steps provided in the error message, and check this blog to see whether it is helpful: https://elhajj.wordpress.com/2013/02/25/workaround-error-tf255049-punching-a-hole-through-windows-firewall/
I was running an upgrade from TFS 2018 to Azure DevOps 2020.
After the server restart, the Azure DevOps Server Configuration wizard opened.
I was logged in as the local machine administrator and got this error (TF255049: A connection cannot be made to the server that is running SQL Server...) when trying to connect to my SQL Server machine (to chose the configuration database).
I logged in as Network Administrator, started the wizard again and the SQL connection worked.
To restart the Azure DevOps Configuration Wizard again...
Open the Azure DevOps Administration Console and choose Configure Installed Features to open the Server Configuration Wizard...

Microsoft SQL Server Error: 18456 + windows authentication

My PC name is IBALL1. I get an error
Login Failed for user 'iball1\User1'.(Microsoft SQL server, Error: 18456)
I am trying to log in using Windows authentication.
And in SQL Server Configuration Manager > SQl Server Service > SQL Server Logon As Local System.
In error log text file, at C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log
Log says:
Login failed for user 'iball1\User1'. Reason: Could not find a login matching the name provided. [CLIENT: local machine]
i have also faced same problem then i have followed this intructions
Try this once other wise will look into other solution
Go to SQL Server Configuration Manager
Start->all program->SQL Server 2008 R2->Configuration Tools->SQL Server Configuration Manager
Explore "SQL Server Network Configuration" and then select "Protocols For MSSQLSERVER".
Check your TCP/IP Protocols in right side pane. If it is disabled then enabled it and Restart the "Sql Server(MSSQLSERVER) service" that available in "SQL Server 2008 R2 services pane".
Couple of check points:
1) make sure your your sql express services is up and running with name 'IBALL1'
if not try restarting.
2) while connecting give pc name as prefix for server name too .

SQL Server Service Stuck in ‘Starting’ Status

I am not able to connect to the database engine. I have recently installed SQL Server 2012 after formatting my hard drive.
Operating system : Win 7 Enterprise 64-bit
When I try to connect to the database engine :
WN7X64-XXXXXXX, I get the following error message
A network-related or instance-specific error occured. Could not open connection to the SQL Server'.
I tried accessing using (localhost). It did not work.
I tried accessing using (localhost)/SQLExpress. It did not work.
I tried accessing using (localhost)/MSSQLServer. It did not work.
I tried accessing using MSSQLServer. It did not work.
When I checked the services. SQL Server status is starting, and it does not give me the option to start/stop. SQL Server Agent status is blank, when I start the service it gives
Error 1068 : dependency service or group failed to start.
Name Status Startup Type
SQL Full-text Filter Daemon Launcher (MSSQLSERVER) Started Automatic
SQL Server (MSSQLSERVER) Starting Automatic
SQL Server Agent (MSSQLSERVER) Automatic
SQL Server Analysis Services (MSSQLSERVER) Started Automatic
SQL Server Browser Started Automatic
SQL Server Distributed Replay Client Started Automatic
SQL Server Distributed Replay Controller Started Automatic
SQL Server Integration Services 11.0 Started Automatic
SQL Server Reporting Services (MSSQLSERVER) Started Automatic
SQL Server VSS Writer Started Automatic
I sometimes get SQL Server Express stuck in 'starting', in fact, just now, which is why I googled up this page. The solution is to kill the process and restart it.
Simplest way to do that is through Task Manager, which you can start by right clicking the Windows system tray (banner at the bottom of the screen where minised programs go). Processes tab, Sort processes by Name, find all beginning 'SQL...' and stop them.
To restart SQL Server right click the Windows Start button, start Control Panel, Administrative Tools, Services, scroll to all services starting 'SQL...', right click to refresh, and stop any that are running, then start the 'SQL Server' service, followed by any others that are set to Auto or Manual start.
I had the same issue and MSDN Documentation did not help. https://support.microsoft.com/en-us/kb/307288.
It was to do with that there was an orphan Sql related service i.e SqlWriter was hanging around. Go to task manager and killed it. Then the error went away.
To connect to a SQL Server default instance (not Express), you can use:
just a . (dot)
just a (local) (be aware: in round brackets)
just a localhost (be aware: NO brackets)
See the official MSDN documentation on Logging In to SQL Server for more details and explanations, and for even more options how to connect.
Try localhost or (local). Not (localhost).
I had the same issue . go to task manager , search for "SQL Server Windows NT" then end the task . after that , go to your services (Run services.msc) and restart your sql server instance .
Solution works for me in MSSQL Server express edition with Windows 10 environment .

Unable to start service MSSQLSERVER on server (mscorlib)

I tried to restart a remote SQL server (2012 full) and I got this error:
Unable to start service MSSQLSERVER on server (mscorlib)
Every time I try I get this message. How can I fix it?
It looks like the service got setup wrong.
Try The following:
Run services.msc
Find the MSSQLSERVER Service.
Right click and open properties
Check what service account it is running under (usually NTAUTHORITY\SYSTEM, NTAUTHORITY\LOCAL SERVICE or NTAUTHORITY\NETWORK SERIVICE unless you have it running under a different user account for security purposes).
Also, they might have moved things around in 2012 I'm still on 2008 R2
I was getting the same error message for days. I went to my domain controller and changed the password of the sql server agent and updated the password in the configuration manager. And, it connected.
Go to Services and right click on sql server agent. select properties and update password/ confirm password if you not using local system account. Its working for me.
changing password and restarting service works for me

How to find why application cannot connect to SQL Server 2008

Windows application is set to connect to the SQL Server using SQL Server authentication.
When I RDP to the box where the application resides and start the application, it successfully connects to the SQL Server.
When a customer runs the application on his desktop (he is on the network with the application box) and starts the application, connection fails (error. Server does not exist or access denied).
The customer can ping the SQL Server IP in his command prompt.
Yet, when I look at the error log on the SQL server I don't see the logs of his failure to connect.
What could be blocking his access to the SQL Server?
You may have to enable the TCP/IP protocol in SQL Server Configuration Manager - it's disabled by default.