August 21, 2002 at 1:02 pm
I couldn't find much help on microsoft.com about the above error, anyone seen this one before? Thanks.
August 21, 2002 at 2:48 pm
I ran into it recently in a dts scenario. I was attempting to use a sql2000 function against a sql 7 database. Once I checked the sql7 box in the options tab - problems disappeared. I don't know what your situation is, perhaps more information would help.
Jody
August 21, 2002 at 3:14 pm
Where does this occur?
Steve Jones
http://qa.sqlservercentral.com/columnists/sjones
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
August 21, 2002 at 3:25 pm
I see it in the log files and my user does not remember what she was doing at the time this occured. I will keep an eye on it and see if it happens again.
August 22, 2002 at 10:08 am
I have gotten this error a couple times in EM while connecting to our remote SQL Server (2000).
I don't remember exactly, but I think I've gotten it while trying to a variety of do basic things in EM like view a table or open a DTS package. It seems to happen most when I've been doing lots of stuff. EM seems to somehow get confused or something.
When I get it, I close EM and go right back in and don't have a problem.
August 22, 2002 at 2:00 pm
Is it a multi processor box? If so, it's possible you've run across one of the many parallelism bugs in SQL Server. Try turning off parallel query execution (right click the server in EM, Properties, Processor Tab, choose Use (1) Processor(s)) and see if the errors go away. I have seen this eliminate internal access violations at a couple of sites...
Of course, if it's a single processor server, then you can disregard this post 🙂
August 22, 2002 at 2:23 pm
Just a point of clarification since we're talking about both servers and clients. An access violation occurs when a particular application attempts to access a memory location in a way it isn't supposed to. Here's the Microsoft glossary definition on an access violation:
quote:
access violationAn attempt to execute a memory operation that is not allowed by the underlying page protection. Applies to memory operations; does not apply to checking user-mode access rights to objects by the Security Manager.
See also probe and SEH.
There are four types of access violations. An access violation occurs if you attempt:
An invalid operation, such as writing to a read-only page.
To access memory beyond the limit of the current program's address space (known as a length violation).
To access a page to which the system forbids access. For example, code is not allowed to run in the low-order 64K of the system's user-mode address space in order to simplify the detection of NULL pointer references.
To access a page that is currently resident but dedicated to the use of a system component. For example, user-mode code is not allowed access a page that the kernel is using.
So the access violation error on the server is considerable different than one occuring from Enterprise Manager on a workstation.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
August 22, 2002 at 2:46 pm
Very true...in reading shahgols response to where it was occuring...
"I see it in the log files..."
I had (rather hastily) assumed he was referring to the SQL Server log files, which would indicate that SQL server itself was throwing the AV and handling it internally.
So, the question is, does this error show up in the SQL Sever logs, indicating an AV on the server, or does it show up in some application or dr. watson log on the client machine, which is, as bkelly stated, a whole other issue entirely.
August 22, 2002 at 5:41 pm
I read that, too, in shagols response and assume it's on the server as well. I was referring to the posts talking about issues with EM generating the access violation.
With respect to an AV with the server, typically it'll invoke a debugger to do a stack dump of the error. This should be in the error log. If it is, you might submit it here and we can take a look at it and help try and point you in the right direction.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
August 23, 2002 at 12:42 pm
I am sorry for the late reply to this thread...yesterday was a D Day here at work. Anyways, the log files I was refering to were the SQL Server 2000 log files on the server. What can I do if I see this error occurs again? Bounce the SQL Server service?
August 23, 2002 at 1:25 pm
Do you still have the original log files? If not, look in your LOG directory and see if you can find any .dmp files. These are text outputs of what the debugger would have pulled together.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
August 23, 2002 at 1:41 pm
Yes, I found the .dmp files, but have no idea what to do next.
August 23, 2002 at 2:19 pm
If you could post what's in the first dump file, we may be able to get a handle on what broke.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
August 24, 2002 at 4:40 pm
Yes post the data from the dump file and also if not already done so check Event Viewer applications and system to see if any other details there.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
August 28, 2002 at 2:22 pm
The .dmp file is too big, should I post it anyways? Does this forum allow me to post such a big file?
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply