Home Dashboard Directory Help
Search

Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION at Exception Address = 01025387 Module(sqlservr+00025387) by el_co


Status: 

Active


4
0
Sign in
to vote
Type: Bug
ID: 459309
Opened: 5/27/2009 11:42:19 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

In the last couple of weeks this error occurred twice in our SQL 2005 Server and after ten minutes SQL restarted on its own. Below are more details about the environment and circumstances when this happened:
We are running SQL 2005 Enterprise in a cluster (manual failover) environment on Win 2003 SP2 and two different queries generated the same error resulting in a SQL dump and restart after 10 minutes.
First time the access violation was generated as a result of a SP execution and the only non standard syntax I found inside was : DATEDIFF("d",@entered_on_in,entered_on)=0 where there are useless double quotes around the date alias d in the stmt above.
Second violation was caused by a simple SELECT where the only odd thing is that an integer column value is tested against a string '123456' value from the UI.
I looked at several known issues/fixes and the closest seems to be http://support.microsoft.com/kb/949595 however the second time the access violation occurred we didn't get the errors "New queries assigned to process on Node 1 have not been picked up by a worker thread in the last 60 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: 0%. System Idle: 98%." immediately after that but SQL restarted after 600 seconds.
Details
Sign in to post a comment.
Posted by Microsoft on 2/22/2010 at 10:06 AM
Dear customer,
Thanks for contacting us. you asked us two questions, please find our answers below.
1) Is there any documentation available regarding the installation of these two patches for SQL2005 Cluster?
Answer : The white paper here (http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&displaylang=en) describes how to download and apply a Service Pack (SP). the Cumulative Update (CU) patch process is the same process as the one described in whitepaper for SP for SQL Server 2005.
Note that for SQL Server 2005, when you run hotfix on the active node of your cluster and it takes care of all the updates on that node and remote nodes of a given cluster.
2)Are they "cluster aware" and is it possible to know if they be applied in a speciffic order? My guess is Yukon_SP2_CU4_SNAC should go first first then Yukon_SP2_CU4
Answer : There is no specific order required. The above patches can be applied in any order. In general individual patches are versioned and will confirm whether they can be applied against the chosen clustered instances based on current version. Hotfix.exe will not allow you to apply patches that are versioned lower than the instance.

Hope this helps,
Madhan
Posted by el_co on 2/12/2010 at 7:12 AM
As we got the same issue even after SP2 installation we are about to apply the (Cumulative Update 4 for SQL Server 2005 SP2) as per http://support.microsoft.com/kb/941450/LN/ however at the above link there are two files:
Yukon_SP2_CU4_SNAC (about 3MB for SQL Native) and Yukon_SP2_CU4 (about 128MB for SQL server itself). Is there any documentation available regarding the installation of these two patches for SQL2005 Cluster? Are they "cluster aware" and is it possible to know if they be applied in a speciffic order? My guess is Yukon_SP2_CU4_SNAC should go first first then Yukon_SP2_CU4.

Thanks,
Lawrence Cohan.
Posted by el_co on 12/9/2009 at 7:42 AM
We thank you very much for the solution (Cumulative Update 4 for SQL Server 2005 SP2) and we will try to apply that update shortly. Currently we are at SQL 2005 SP2(9.0-3080) and since we applied SQL SP2 the issue did not reocurred yet.
Posted by Microsoft on 11/16/2009 at 5:43 AM
Dear Customer,
Thanks once again for sending us the additional dumps. we were able to analyze it and determined that the issue you are seeing is fixed in Cumulative Update 4 for SQL Server 2005 SP2.

see below is the link to the issue that i am referring to.
http://support.microsoft.com/kb/941695

Please download the fix and let us know if it resolves your issue.

thank you for your patience,
Madhan
Posted by Microsoft on 11/7/2009 at 12:48 PM
we had some problem retrieving your latest attachement due to an internal tool error, but it looks like we can finally see the files. that you for your patience. Let us take a look and get back to you.

thanks,
Madhan
Posted by Microsoft on 11/7/2009 at 11:10 AM
Unfortunately no i still don't see your attachement. the only attachment i see is "dump.zip" which has the dump files 82 and 85. Can you please check? I will also double check with our tool owners.

thanks,
Madhan
Posted by el_co on 10/26/2009 at 1:54 PM
SQL dump files.zip contains SQLDump0081.mdmp, .log and .txt and looks like I missed them last time when I think I may have tried a multi file attachment - not relevant as they are there mpw and please let me know if you still can't access them.

Thanks,
Lawrence Cohan.
Posted by Microsoft on 10/21/2009 at 8:51 AM
Hello again,
you mentioned last on this thread that you had attached the SQLdump0081 files as we requested. however i cannot seem to find it in the defect. i thought it could be our tool issue not surfacing the new attachment and double checked with the tool owners, but it looks like it is not a tool issue. Can you please reattach SQLdump0081 files please. Apologies for any incovenience.

thanks,
Madhan
Posted by el_co on 6/26/2009 at 12:32 PM
Although we run in a cluster environment I can confirm that there was no a failover service or an Agent job that was causing this restart and that can be seen in the SQL logs as well as we stayed on the same node after the SQL Server Service restart.

Posted by el_co on 6/26/2009 at 12:08 PM
SQLdump0081 files attached as requested.
Posted by Microsoft on 6/22/2009 at 8:30 PM
Sorry about the multiple posts. Looks like out tool interface is acting flaky.
Posted by Microsoft on 6/22/2009 at 8:29 PM
After analyzing the dumps, we can see that there was a previous Access Violation that occurred causing the problem. However the dumps you provided did not have information regarding that AV. Can you send us the previous dump (SQLDump0081) which would help us investigate the problem further.

At any rate, SQL server should not be restarted. Can you confirm that there is not a failover service or an Agent job causing this restart?

thanks,
Madhan
Posted by Microsoft on 6/22/2009 at 5:11 PM
Dear Customer,
From analyzing the dump you provided, we see that there was a previous Access Violation that had left the system state in an unreliable state. We would need access to SQLDump0081 (contains information about the previous AV) in order to debug this further. Please send us this dump.

At any rate SQL Server should not be restarting on its own because of this problem. Can you please confirm that the restart is not a result of a failover monitoring process or a SQL Agent job?

thank you,
Madhan
Posted by Microsoft on 6/22/2009 at 3:59 PM
Dear Customer,
From analyzing the dump you provided, we see that there was a previous Access Violation that had left the system state in an unreliable state. We would need access to SQLDump0081 (contains information about the previous AV) in order to debug this further. Please send us this dump.

At any rate SQL Server should not be restarting on its own because of this problem. Can you please confirm that the restart is not a result of a failover monitoring process or a SQL Agent job?

thank you,
Madhan
Posted by el_co on 6/16/2009 at 10:16 AM
All dump files from the server where this error occured twice were zipped and uploaded as dump.zip
Posted by Microsoft on 6/5/2009 at 5:39 PM
Dear Customer,
Thanks for reporting your issue. You mentioned in the bug that you got a SQL dump. Can you please send that along with the error logs. This information would greatly help us in rootcausing this issue. Please let us know.

thanks,
Madhan
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
dump.zip (restricted) 6/16/2009 -
SQL dump files.zip (restricted) 10/26/2009 -