Post reply

SQL Server is terminating because of fatal exception e06d7363

  • March 23, 2011 at 6:36 am

    #389115

    I get this error probably every 3 or 4 weeks, can someone help me what is causing it.

    SQL Server is terminating because of fatal exception e06d7363. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

    Thank you

  • March 23, 2011 at 7:21 am

    #1302442

    Call Customer Support and log a case with them. Make sure you're on the latest service pack first.

    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

  • March 23, 2011 at 8:50 am

    #1302522

    Is this production env or developer env with VS 2005\VS2008 on the same box as SQL server ?

    Cheers

    Sat

    Cheer Satish 🙂

  • March 23, 2011 at 9:03 am

    #1302535

    Is this production env or developer env with VS 2005\VS2008 on the same box as SQL server ?

    This is production with 2005.

    I found that under certain account before database went down, I had an error message that for certain account insufficent memory to run these query. This account is using 5 different databases

Viewing 4 posts - 1 through 3 (of 3 total)

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