Sql Server 2005 Error 109

  • Hi

    I have a Sql server 2005 on windows XP that i have been working on for the past few months without any problems.

    I had a virus on my PC and I installed Symantech and spy bot.

    Now I cannot login and i see in control panel that the service

    'Sql Server' is not running. When I am trying to start the service I am getting the following error :-

    Could not start sql server service on local computer.

    Error 109: the pipe has been ended.

    I tried to switch off firewall, spybot but it is still the same problem.

    any ideas ?

    loki.

  • Hi Loki,

    Please try adding the "sqlservr.exe" to the exception list of Symantec.

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • Hi

    I disabled spybot and symantech but the problem is still not resolved.

    I also see that my sql server service is not running, do i need to have this service started before i login ?

    Any other ideas ?

    Loki.

  • loki_l77 (3/10/2009)


    I also see that my sql server service is not running, do i need to have this service started before i login ?

    Um, yes. The service is SQL Server. If that isn't running there's nothing to log into.

    If the SQL Server service won't start, find a file called errorlog (should be somewhere beneath the SQL installation directory) and check what it says. There's usually an entry indicating why the service wouldn't start.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hi

    thans for replying.

    Tried to start the database from the command prompt and got the following error in the errorlog:-

    Sql server is terminating because of fatal exception c0000005, This error may be caused by an unhandled win32 or c++ exception using dbghelp.dll version 4.0.5.

    ..Loki.

  • Try starting the service from the service control app and then checking the error log file. Post the whole thign here if you're not sure how to interpret it.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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