SQL Server 2008 Restart

Question

SQL Server 2008 Restart

sqlrocks79

Old Hand

Points: 354
More actions
September 30, 2010 at 9:46 am

#241201

Hi
I am repeatedly getting the folowing error and the SQL Server is getting restarted. I am using SS2K8
A user request from the session with SPID X generated a fatal exception. SQL Server is terminating this session.
Has anyone seen this issue before. Any help in this regard is much appreciated.
Thanks in advance
SQLRocks

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

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

george sibbald SSC Guru Points: 104210 More actions · Answer 1

not enough information to help there. Is there a stack trace in your SQL log directory or any further messages in the errorlog.

As a fatal exception this might require MS to provide a fix.

What version of 2008 are you on? Have you applied SP1? SP2 is out today so might contain a fix for your problem.

---------------------------------------------------------------------

sqlrocks79 Old Hand Points: 354 More actions · Answer 2

Sorry for the late reply. The problem still persists. I am trying to solve it.

Thanks a lot for your help. Much appreciated!

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

sqlrocks79 (10/6/2010)
Sorry for the late reply. The problem still persists. I am trying to solve it.

If you want our help, answer George's questions.

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

Nakul Vachhrajani SSChampion Points: 10294 More actions · Answer 4

george sibbald (9/30/2010)
not enough information to help there. Is there a stack trace in your SQL log directory or any further messages in the errorlog.
As a fatal exception this might require MS to provide a fix.
What version of 2008 are you on? Have you applied SP1? SP2 is out today so might contain a fix for your problem.

I agree. Not enough information here. The user who is on SPID X is probably running some code that is generating a fatal SQL Server exception. This should be in the SQL Logs and you can also capture the activity using the Profiler.

Other than these vague pointers, we cannot help much unless we have specific information (there are a thousand different directions in which we will need to go based on the scenario - no point in attacking all directions simultaneously).

Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com

Follow me on
Twitter: @sqltwins