system shutdown was unexpected
in [Server Configuration]
|
From: Claudio on 29 Sep 2009 14:43 Hola, estamos teniendo problemas al iniciar un reindex con una base, el servidor queda inoperativo, teniendo que ser apagado desde el boton de power para poder reiniciarlo (se cuelga mal). Este servidor tiene varias bases, y corren otros jobs de mantenimiento y optimizacion pero con esta base (que no es muy grande tampoco) siempre pasa lo mismo cuando se deja programada para que corra, no asi si se ejecuta manualmente. Ya se verifico y comprobo que no se superponga con otras tareas de mantenimiento o backups, se elmino el job y volvio a crear, pero nos ocurre lo mismo. Por ejmplo se programa para que se ejecute a las 23 hs de un dia sabado (donde naide utiliza el servidor) y nos encontramos el lunes que el servidor esta inoperativo y cuando se reinicia manualmente en el log de sistema nos aparece el mensaje: The previous system shutdown at 10:59:11 p.m. on 26/09/2009 was unexpected. Y en el log de SQL el job nunca corrio, es decir siempre se cuelga el server unos segundos antes que se dispare el job, este job. Alguna idea de cual puede ser le problema o como se puede monitorear para detectar la falla? SO: Windows 2003 server SP2 SQL server 2000 SP4 Enterprise edition
From: Jeroen Mostert on 29 Sep 2009 21:09 Claudio wrote: [Spanish] Try asking in English, or post your query to news:microsoft.public.es.sqlserver. -- J.
From: Greg Linwood on 30 Sep 2009 00:25 Anyone able / willing to translate? Cheers, Greg "Claudio" <Claudio(a)discussions.microsoft.com> wrote in message news:AD83C4E0-5DCF-4B30-B542-E2D046EA8A6B(a)microsoft.com... > Hola, estamos teniendo problemas al iniciar un reindex con una base, el > servidor queda inoperativo, teniendo que ser apagado desde el boton de > power > para poder reiniciarlo (se cuelga mal). Este servidor tiene varias bases, > y > corren otros jobs de mantenimiento y optimizacion pero con esta base (que > no > es muy grande tampoco) siempre pasa lo mismo cuando se deja programada > para > que corra, no asi si se ejecuta manualmente. Ya se verifico y comprobo que > no > se superponga con otras tareas de mantenimiento o backups, se elmino el > job y > volvio a crear, pero nos ocurre lo mismo. Por ejmplo se programa para que > se > ejecute a las 23 hs de un dia sabado (donde naide utiliza el servidor) y > nos > encontramos el lunes que el servidor esta inoperativo y cuando se reinicia > manualmente en el log de sistema nos aparece el mensaje: > > The previous system shutdown at 10:59:11 p.m. on 26/09/2009 was > unexpected. > > Y en el log de SQL el job nunca corrio, es decir siempre se cuelga el > server > unos segundos antes que se dispare el job, este job. > > Alguna idea de cual puede ser le problema o como se puede monitorear para > detectar la falla? > > SO: Windows 2003 server SP2 > SQL server 2000 SP4 Enterprise edition > >
From: Erland Sommarskog on 30 Sep 2009 06:52 Greg Linwood (g_linwoodho(a)tmaildotcom) writes: > Anyone able / willing to translate? In short, Claudio attempts to reindex a particular table, in a database of very modest size. This leads the entire machine becoming unresponsive, and they have to press the reset button. He has checked and there are no other jobs running at the same time. What is a little interesting is that he says that they started this job on Saturday night 23:00, and they had to reset the machine on Monday morning. But the error message says: The previous system shutdown at 10:59:11 p.m. on 26/09/2009 was unexpected. Thus the machine died about the same time as the job started. Or actually just before. I looked at this last night, but I was too tired to try composing a reply in Spanish, and in any case I don't have that much to say. But if my understanding is correct that the server dies, then it smells like a problem with faulty hardware and/or a bad driver. Had SQL Server alone become unreponsive, I would have suspected scheduler problems and seeing error 17383 in the error log. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Greg Linwood on 30 Sep 2009 07:18 Hopefully he will understand that the machine shutting down isn't directly SQL Server's fault, so he can focus on finding whatever the real underlying problem is.. Cheers, Greg "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message news:Xns9C9682EB65CBAYazorman(a)127.0.0.1... > Greg Linwood (g_linwoodho(a)tmaildotcom) writes: >> Anyone able / willing to translate? > > In short, Claudio attempts to reindex a particular table, in a database of > very modest size. This leads the entire machine becoming unresponsive, and > they have to press the reset button. He has checked and there are no other > jobs running at the same time. > > What is a little interesting is that he says that they started this job > on Saturday night 23:00, and they had to reset the machine on Monday > morning. But the error message says: > > The previous system shutdown at 10:59:11 p.m. on 26/09/2009 was > unexpected. > > Thus the machine died about the same time as the job started. Or actually > just before. > > I looked at this last night, but I was too tired to try composing a reply > in Spanish, and in any case I don't have that much to say. But if my > understanding is correct that the server dies, then it smells like a > problem > with faulty hardware and/or a bad driver. Had SQL Server alone become > unreponsive, I would have suspected scheduler problems and seeing error > 17383 in the error log. > > > -- > Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se > > Books Online for SQL Server 2005 at > http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx > Books Online for SQL Server 2000 at > http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|
Pages: 1 Prev: SQL Server Install Fails Next: Error 0X8007042B while restarting SQLServer Agent 2005 |