Not able to start sqlserver default instance in sqlserver 2005

  • Hi

    i Not able to start (automatically) sqlserver default instance in sqlserver 2005

    every day manually i am staring the instances

    first i installed sqlserver 2005 dev edition ((default instance) and later i install lserver2000(named instance)

    it was working fine for some days but last 10 days onwards the default instance is not starting automatically when i start my system daily i am manually stopping named instance then starting default instance then staring named instance .(i.e) (when i stop the named instance then only default instance services are starting if i start directly default instance error is comming that is the reasin every day first i will stop the named instance then i will start default instance

    experts pls help me

    how to fix this issue ( iwant to start both (named and default instances the services automatically)

    i checked all the services properties all are in automatic mode only

    pls give u r valuable suggestions to fix this issue permanently

    thanks in advance

  • hi experts

    please reply to this issue.

    Thanks

  • what is the error that you get : check the event and SQL Server logs

    post the errors here

    Abhay Chaudhary
    Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)

  • Hello,

    If the issue is related to a lack of system resources, then you could consider setting the SQL Services to auto start in sequential order i.e. to automatically do what you are now manually doing. Be warned that this involves updating the Registry.

    Please see the following MS KB Article:-

    http://support.microsoft.com/kb/193888

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

  • sivark1 (6/18/2009)


    first i installed sqlserver 2005 dev edition ((default instance) and later i install lserver2000(named instance)

    Is this your personal box or a production machine?

    Are all your SQL instances properly patched?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • I don't know which environment you are running (Production or Test - Development) but seems that you should uninstall and reinstall again you SQL Server!

    Consider this as the last thing to do! Very hard to check on the registry and other deep places in your system if you do not have much information how to do that!

    ============================================================
    SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
    http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

  • I'm thinking you have a Dev version of one software and a regular "production" version of the other software and that's why you're having problems. So Dugi would be correct about requiring a re-install.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Viewing 7 posts - 1 through 6 (of 6 total)

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