September 30, 2010 at 10:18 am
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.
---------------------------------------------------------------------
October 6, 2010 at 10:42 am
Sorry for the late reply. The problem still persists. I am trying to solve it.
Thanks a lot for your help. Much appreciated!
October 6, 2010 at 10:53 am
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
October 6, 2010 at 11:28 pm
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
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply