Post reply

SQL server service not starting

  • June 10, 2007 at 9:13 pm

    #68840

    Hi,

    I had installed sql server enterprise edition with SP4 on a new server with OS Windows server 2003 a few days back. Everything was running fine. Few days back I found that the MSSQLServer service was not running. I tried to start it but it is not getting started. Everytime I try to start it, it starts and then stops with the following message

    "The MSSQLServer Service on Local Computer Started and then Stopped. Some services stop automatically if they have no work to do, for example, the Performace logs and Alert Service."

  • June 10, 2007 at 9:39 pm

    #711899

    I'm going to assume that you didn't attach any system databases to this server in the last few days, but if you did, that's often a cause of this sort of thing.

    If that's out of the question, I'd check the error logs and see what they say when the service is starting up and then stops. It could be many things, even such problems as trial editions expiring, but the error logs should give a much better picture. Let us know what you find.

  • June 11, 2007 at 2:05 am

    #711919

    Starts and then stops:

     

    Does the SQL Server service run for few mins and then stops or it stops immediately. This might be a problem if the needed permissions for the account starting sql server is not suficient.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 11, 2007 at 4:29 am

    #711939

    it stops immediately with the message.

  • June 11, 2007 at 4:40 am

    #711941

    Also the event log has the following. The temdb database is in F:\sql\database folder. How to I go about resolving this now.The server has no g:\ drive associated with it.

     

    CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'g:\sql\database\tempdb.mdf'.

    udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device g:\sql\database\tempdb.mdf.

    FCB:pen failed: Could not open device g:\sql\database\tempdb.mdf for virtual device number (VDN)

    Device activation error. The physical file name 'g:\sql\database\tempdb.mdf' may be incorrect.

    CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.

  • June 11, 2007 at 7:05 am

    #711982

    You can alter the database path using alter database command and then once you give the correct path of the tempdb database restart sql services that should be running fine.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 11, 2007 at 8:38 am

    #712006

    BUt how do I alter the database when sql server is not running. How do I connect to the query analyser??

  • June 12, 2007 at 12:20 am

    #712181

    It seems like the easiest way would be to create a G: drive on the server temporarily that maps to the F: drive (or create an actual G: volume and move the files there temporarily if you prefer), then move tempdb to F: (via ALTER DATABASE) once it's up and running. Depending on your company and hardware setup, this might be something you can do, or it might require your company's infrastructure team.

    The other options I can think of use trace flags on startup (you'll basically end up with a new tempdb), and that can get messy fast if you're not used to them.

  • June 12, 2007 at 5:07 am

    #712214

    use trace flag -T3608 in the startup of sql server. This will only start your master database. Once the SQL server starts in this mode alter the tempdb location and then remove the trace flag and start your services as usual.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply