January 25, 2017 at 6:02 am
Hi,
I restarted the Production SQL Service from the SSMS object explorer in my local machine. It didn't shhowed that SQL Agent stopped but looks it didn't shutdown the SQL Service. I am seeing the login failures showing only administators can connect at this time.
I can't able to RDP to the server and start option is not highlighted from the object explorer from my local machine.
I can able to run T-SQL Queries.What T- SQL commands I can use this time to start the service?
I believe it is still stopping the service. How can we know how long it will take? This instance is enterprise 2005.
January 25, 2017 at 7:01 am
If you can run queries, the service is running. What is the exact nature of your problem?
John
January 25, 2017 at 7:15 am
John Mitchell-245523 - Wednesday, January 25, 2017 7:01 AMIf you can run queries, the service is running. What is the exact nature of your problem?John
So many login failures. Error msg showing only administators can connect at this time. i.e. No one is not able to connect the SQL except DBAs. This is weird situation.
I saw the restarts happen in minutes but I am not sure why this is taking more 5 hrs.
January 25, 2017 at 7:26 am
Do you have any way of connecting to the server's event log to see what's happening on the server? If not, ask your server admin to help you.
John
January 25, 2017 at 7:32 am
Currently, I can't able. Not able to RDP.
I tried to start the agent but it failed telling it has dependency service. I have to wait for the server admin.
January 25, 2017 at 7:44 am
ramana3327 - Wednesday, January 25, 2017 7:32 AMCurrently, I can't able. Not able to RDP.
I tried to start the agent but it failed telling it has dependency service. I have to wait for the server admin.
You can run Event Viewer locally and then connect to a remote computer. You need to have sufficient access on the remote computer to do that, but it's worth a try while you're waiting for the server admin to come back from the pub!
John
January 25, 2017 at 8:12 am
I am getting the below error
Can't open the file. This may be because the file does not exist, is not an MMC console or was created by a later version of MMC. This may also be because you don't have sufficient access rights to the file.
Looks I don't have proper rights. Probably it requires to have domain admin permissions
January 25, 2017 at 8:25 am
What will happen to the SQL Server if they restart the system?
January 25, 2017 at 8:31 am
ramana3327 - Wednesday, January 25, 2017 8:25 AMWhat will happen to the SQL Server if they restart the system?
It'll stop when the server goes down, and restart when it comes back up (assuming the startup type is set to Automatic). Unless something is very wrong, that is. Best to do a bit of troubleshooting before resorting to the "off then on" mantra, though. Look at the event log. Look at the SQL Server errorlog. Speak to your company's change manager to find out whether there have been any (authorised) changes. Speak to users and ask whether they noticed anything before application became unavailable.
John
January 25, 2017 at 9:59 am
We are restarted the system. Now the SQL Server is up and running
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply