Application Log: Event ID 17311
SQL Server is terminating because of fatal exception c0000005. 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).
Message
[012] The MSSQL$DATAPROSQL service terminated unexpectedly
please please who can tell me why and how to ?
事件类型: 错误
事件来源: MSSQLSERVER
事件种类: (2)
事件 ID: 17311
日期: 2006-8-19
事件: 11:10:47
用户: N/A
计算机: TXOA
描述:
由于出现异常 c0000005,SQL Server 正在终止。此错误可能是由未处理的 Win32 或 C++ 异常造成的,也可能是因在处理异常过程中遇到的违规访问引起的。请查看 SQL 错误日志,获取任何相关的堆栈转储或消息。此异常会强制 SQL Server 关闭。要从此错误中恢复,请重新启动服务器(除非已将 SQLAgent 配置为自动重新启动)。
数据:
0000: 9f 43 00 00 10 00 00 00 ?C......
0008: 05 00 00 00 54 00 58 00 ....T.X.
0010: 4f 00 41 0
这里有没有微软中国的大侠啊,这个问题是到底怎么回事啊,在sql2000时,打sp3补丁可以解决,可是sql2005的sp1补丁我打了也没有解决啊,更奇怪的是,为什么我在“服务”中设置了sqlserver的故障恢复为“重新启动”也不执行呢???
我的数据库服务器配置是cpu:intel 至强 2.4×4,RAM:1GB,OS:MSWindows 2000 Advance Server
哪位大侠能告诉我这到底是为什么和怎么解决啊???
I think this might be a 'server guy' problem. It sounds like this is a windows issue.
You will probably need to work in tandem with that person to diagnose, if it keeps happening. Make sure your disks are good, RAM is good, etc. Think about rebuilding if it keeps happening.
Microsoft can read the dump for you, and there are switches, I believe, that you can set to make sure you get specific dump logs. If you are desperate and don't want to ask them, there are applications (some from them, I think) that can read a windows dump file.
|||Fatal exception tends to be a bug. I suggest you contact MS technical support.
No comments:
Post a Comment