How can I re-start my SQL Server 2005 Express Database Engine Service?

I have installed SQL Server 2005 Express on a client's network.
Today I seem to be unable to logon to the database, either using my MS Access "project" application or the SQL Server Management Studio Express program.
When I use the SQL Server Surface Area Configuration program, I see that the SQLEXPRESS Database Engine has stopped even though the "Startup type" is set to "Automatic". When I click on the "Start" button a progess bar appears for about 10 seconds then I'm told the operation has timed out and I need to have administrator privileges to perform that action.

I am logged on to the hosting Server (running Windows Server 2003) using an "Administrator" logon from a Windows XP PC using a Remote Desktop connection. I used this method to install SQL Server on the server in the first place and up until now have been able to run the SQL Server Management Studio Express program to maintain the database.

Does anyone have any suggestions on how I can re-start my SQL Server Database Engine, and why I now appear to not be recognised as an Administrator?

Many thanks. Colin.
colinasadAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RiteshShahCommented:
what is your SQL Server service account?

generally you should be able to start service from control panel->administrative tools->services->SQL Server

if you are not able to do so than you MUST not have permission.
0
Rahul Goel ITILSenior Consultant - DeloitteCommented:
Services.msc
 
Locate MSSQLExpress.....rightclick and restart
0
boowhupCommented:
Check what account the service is trying to run as. If it's tryimg to Run as administrator then maybe the password has changed (you can check this where RiteshShah suggests). Otherwise check the event logs for a specific error and then do a search on it with google. Also check for other services related to MSSQL in the services tab under administrative services.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

colinasadAuthor Commented:
Thanks for the prompt responses.

I again logged on to the main server using Remote Desktop and the "Administrator" logon (which I assume has administrator priviliges) and found the SQL Server "services" as suggested.

However I was still unable to re-start the SQL Server service.
The services relating to SQL Server that were listed are :

                                                         Status           Startup Type             Logon As
SQL Server (SQLEXPRESS)               (blank)           Automatic                  Local System
SQL Server Active Directory Helper  (blank)           Disabled                    Network Service
SQL Server Browser                         Started          Automatic                  Local System
SQL Server VSS Writer                     Started          Automatic                  Local System

When I tried to "Start" "(SQLEXPRESS)" I again had a brief "Service Control" progress bar then a failure message at the end, quoting "service-specific error code 3417" and suggesting I review the System Event Log. I assume this is what "boowhup" was suggesting but I don't know how to do this (let alone react to whatever it might reveal).

I had a look at the Active Directory Helper service but couldn't see an option to "enable" it.

I will try to contact the people who look after the server for my client to see if they can shed any light on the problem, but any further suggestions would be appreciated.

0
colinasadAuthor Commented:
I have now found an "Event Viewer" on the main server and have found a few error messages relating to SQLServer.

On 16th June :
Operating system error 23(Data error (cyclic redundancy check).) on file "d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf" during CheckLogBlockReadComplete.

also :
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

Then no further events relating to SQL Server until today when there are whole list of them, presumably relationg to my multiple attempts to re-start the service.
(This is a "work in progress" and I have been away on holiday since the beginning of June. Things appear to have gone wrong on the 16th June and today is the first time it has been looked at since.)

It looks like there is corruption on the "master" database that needs to be fixed ... somehow.

Any suggestions in how to do this, given that the whole SQL Server service appears to have ground to a halt?
0
colinasadAuthor Commented:
I seem to be in a Catch 22.
It looks like my "master" database file "mastlog.ldf" is corrupted, or sitting on a corrupted area of hard disk. This seems to be preventing the SQL Server service from starting.

I can't even make a copy of this file for safe-keeping because I get a CRC error when I try (although I can rename it).

Any suggestions on how I can recover/repair this file without the SQL Server service running? Unfortunately I don't have a backup of the "master" database files.
0
RiteshShahCommented:
0
boowhupCommented:
Yep Ritesh is right. and failing that you can take a file copy of the mdf and ldf for your databases (whatever they are called). And do an uninstall/reinstall of SQL - but Ritesh's option might be faster.
0
colinasadAuthor Commented:
Thank you.
I tried the instruction in the article suggested by RiteshShah but it didn't work for me.
The article does say that the SQL Server instance should be running when you try the rebuild/repair of the master database, but the CRC error on my "mastlog.ldf" is preventing the SQL Server service from running at all.
The command suggested does do/attempt something for about 5 minutes but it gives no feedback at all, and does not indicate whether it thinks it succeeded or why it failed.
I think I will need to uninstall then re-install SQL Server on the client's server.
Luckily this is a system I was still developing and that my client was not actually using, but it is an early lesson in the importance of backing up the "system" databases as well as the "application" database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.