help me
-
Hello,
can anyone help me in find the solutions to
this error.
EXCEPTION_ACCESS_VIOLATION raised, attempting to create symptom dump
Initializing symptom dump and stack dump facilities
***BEGIN STACK TRACE***
0x004045CE in SQLSERVR.EXE, closetable () + 0x065E
0x0040CBE3 in SQLSERVR.EXE, close_range () + 0x0003
0x0040B5F3 in SQLSERVR.EXE, mkresdom () + 0x0233
0x0040BC41 in SQLSERVR.EXE, s_execute () + 0x0121
0x0040D84C in SQLSERVR.EXE, sequencer () + 0x006C
0x00419B6E in SQLSERVR.EXE, execproc () + 0x3A2E
0x0040C1D5 in SQLSERVR.EXE, s_execute_1147c_73e_19s_20820er () + 0x00F5
0x0040D84C in SQLSERVR.EXE, sequencer () + 0x006C
0x0042BE21 in SQLSERVR.EXE, language_exec () + 0x01F1
0x0024134D in opends60.dll, srv_post_handle () + 0x0000
0x002408BB in opends60.dll, srv_post_handle () + 0x0000
0x00231569 in opends60.dll, Ordinal65 () + 0x0000
0x00231384 in opends60.dll, Ordinal65 () + 0x0000
0x10219D84 in MSVCRT40.dll
x77F04EDE in KERNEL32.dll, lstrcmpiW () + 0x0000
***END STACK TRACE***
I have SQL Server 6.5 SP5 running on Windows NT 4.0 Server sp6a
-
Not much to go on. If you can reproduce it, I'd call MS support about it.
Andy
-
What were you doing when you got the error?
Have you gone to http://www.microsoft.com and entered the error (EXCEPTION_ACCESS_VIOLATION) into the search?
-SQLBill
-
These are some of the causes for your error...as you can see it depends on what you were doing at the time:
174512-If a stored procedure or trigger is created that does not contain active code (which means it only contains comments and/or DECLARE statements), SQL Server may stop responding.
176493-A handled access violation (AV) may occur if all of the following conditions are true:
A query references a view.
The view contains a join.
The query contains a subselect.
SET FORCEPLAN ON was run before the query.
181986-A handled access violation (AV) is generated if all of the following conditions are true:
A SELECT statement has two sub-selects that are UNIONed together
The second sub-select statement contains a sub-select that is a JOIN.
And there are many more. BTW- the number is the Microsoft Knowledgebase article number.
-SQLBIll
-
How often does it occure
You do your update stats, defrag, checkdb, etc. stuff
-
this error occur when i call store procedure
but not every time
Create Procedure ssg_ApvOrder @skcode char(10) as
Begin
set nocount on
declare @sdate smalldatetime, @edate smalldatetime,
@stcode char(3), @pr char(13),
@mxpo char(10), @mode char(1)
create table #tmpprod(pr char(13),
stock money,
onorder money,
sale money,
ponum char(10),
type char(1))
create index A on #tmpprod(pr)
create table #epr (pr char(13))
create table #tmpp (pr char(13),
stock money,
onorder money,
sale money,
ponum char(10),
type char(1))
create table #sumpr( pr char(13),
qnt money)
create index A on #sumpr(pr)
select @stcode=ST_CODE
from LOCATION
/*** Prepare Product group by SKCODE and use PROMOTION before ***/
insert #tmpprod
select A.PR_CODE,BR_STOCK,BR_ONDLV,0.00,PO_NUM,PROMOTE
from TMPSUGGEST A,BRPROD B
where A.PR_CODE=B.PR_CODE and DP_CODE like @stcode+'___'
and SK_CODE like @skcode
if @@ROWCOUNT>0
begin
select @mode='0' /*** Insert Mode ***/
insert #epr select pr from #tmpprod group by pr having count(pr)>1
delete #tmpprod from #tmpprod A,#epr B where A.pr=B.pr and type=' '
delete #epr
insert #epr select pr from #tmpprod group by pr having count(pr)>1
if @@ROWCOUNT>0
begin
/*** Use Max PO_NUM to be choice ***/
insert #tmpp
select A.* from #tmpprod A,#epr B where A.pr=B.pr
delete #tmpprod from #tmpprod A,#epr B where A.pr=B.pr
Declare cur CURSOR for
select distinct pr from #tmpp
open cur
fetch next from cur into @pr
while @@FETCH_STATUS<>-1
begin
select @mxpo=max(ponum) from #tmpp where pr=@pr
insert #tmpprod select * from #tmpp where pr=@pr and ponum=@mxpo
fetch next from cur into @pr
end
close cur
Deallocate cur
end
end
else
begin
select @mode='1' /*** Edit Mode ***/
insert #tmpprod
select A.PR_CODE,BR_STOCK,BR_ONDLV,0.00,' ',PROMOTE
from DAVIDPO A,BRPROD B
where A.PR_CODE=B.PR_CODE and DP_CODE like @stcode+'___'
and SK_CODE like @skcode and STATUS=' '
end
update #tmpprod set sale=case QUANT when null then 0.00 else QUANT/7.00 end
from #tmpprod A,CWKSALE B
where A.pr=B.PR_CODE
if @mode='0'
begin
/*** Accept Data from Entry Template Before ***/
insert DAVIDPO
select PROMOTE,pr,PR_NAME,PR_PACKSZ,0.00,SG_ORDER,SK_CODE,convert(char(8),getdate(),10),' ',stock
from TMPSUGGEST A,#tmpprod B
where A.PR_CODE=B.pr and A.PO_NUM=ponum
order by PROMOTE,A.PO_NUM,SEQ
if @@ERROR=0
begin
delete TMPSUGGEST
from TMPSUGGEST A,#tmpprod B
where A.PR_CODE=B.pr and A.PO_NUM=ponum
end
select 'ÃËÑÊÊÔ¹¤éÒ'=pr,'ª×èÍÊÔ¹¤éÒ'=substring(PR_NAME,1,24)+' ',
'ºÃèØ'=convert(char(6),PR_PACKSZ),
'T'=PROMOTE,
'¤§àËÅ×Í'=convert(char(7),convert(int,round(stock,2))),
'ÂÍ´¢ÒÂ'=convert(char(6),convert(int,round(sale,2))),
'¨Ó¹Ç¹'=convert(money,OD_PACK)
from DAVIDPO A,#tmpprod B
where A.PR_CODE=B.pr and STATUS=' '
order by T desc
end
else
begin
select 'ÃËÑÊÊÔ¹¤éÒ'=pr,'ª×èÍÊÔ¹¤éÒ'=substring(PR_NAME,1,24)+' ',
'ºÃèØ'=convert(char(6),PR_PACKSZ),
'T'=PROMOTE,
'¤§àËÅ×Í'=convert(char(7),convert(int,round(stock,2))),
'ÂÍ´¢ÒÂ'=convert(char(6),convert(int,round(sale,2))),
'¨Ó¹Ç¹'=convert(money,OD_PACK)
from DAVIDPO A,#tmpprod B
where A.PR_CODE=B.pr and STATUS=' '
order by T desc
end
End
-
My first instinct would be to try to hunt down the error at microsoft.com. Looking at your script (some of it looks like gibberish
), I see some temp tables and cursors. If I rememebr correctly, wasn't there a pretty vague bug with SQL 6.5 that was something like "Access violations can occur with intensive cursor operations".. Maybe that was 7.0, not sure.I said my first instinct would be to check with MS, but that's because I keep all my db's healthy
. Access violation things have a way of intermittenly happening when a db or table has problems.
-Ken -
quote:
Not much to go on. If you can reproduce it, I'd call MS support about it.Andy
http://www.sqlservercentral.com/columnists/awarren/
I'm not trying to hijack this thread, but- does MS still support 6.5?
-Ken -
TO latch onto what spongemagnet is saying, remember a problem with an Invoice Age Analysis sp with which I ran into trouble with on 6.5. After some MS help decided to revert back to dynmic SQL (40Kb), due to time limit for the development. Was using DB lib. Problem was, when the database was upgraded (new release of app) the sp was not recompiled although a sp_recompile was issued. Some problem with the query plan, etc.
), I see some temp tables and cursors. If I rememebr correctly, wasn't there a pretty vague bug with SQL 6.5 that was something like "Access violations can occur with intensive cursor operations".. Maybe that was 7.0, not sure.
. Access violation things have a way of intermittenly happening when a db or table has problems.Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply