September 24, 2008 at 3:07 pm
Hi folks
The SQL server 2005 x64 that I have is giving this weird error.
SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It started giving the error yesterday evening. and then it did a stack dump. After that the server started kicking users out and
The stack dump lists an open query and the spid that caused this issue. It started to stack dump every time someone uses the openquery after that, but with out the actual query.
Please find the attached sqldump for additional information.
I am thinking that the first occurance of the error caused the oracle oledb drivers to be corrupted in some way, causing it to not support the openquery after that. I had to restart the SQL service before it let anybody in.
What I dont understand is, what actually caused it to happen? Iam able to run the same query that caused the original issue after the service restart.
How can I analyze the stackdumps? is there any resource that can help me with this task.
Thanks for your advise!!
Also, this is the hot fix for an issue that seems to be the closest to mine; http://support.microsoft.com/kb/919144/en-us, but i already have SP2 installed.
thanks
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 8, 2008 at 7:49 am
This issue did not reoccur yet. but my concern is that it might and i dont have any explaination of what happened.
Do any of you good folks at sqlservercentralville have a pointer in analyzing the SQL stackdump?
thanks
shiva
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 9, 2008 at 4:19 pm
My theory is that the Sql server was reeling under memory pressure at the time when this openquery statement was executed. The query fetched data and didnt have any memory space to store it and took a stack dump.
What was your memory usage when you restarted and re-executed the same openquery statement ?
I would like to load the memory like it is in the stack dump and then execute the openquery and see what happens ?
October 10, 2008 at 9:02 am
Once after the service restart, it took less than 1 second to respond to the query, which is what it should be.
SQL server could be out of memory when Stack dump occured the first time. but I cant understand the 15 subsequent stack dumps occured after the original event. And it kicking out all the users was odd, considering that this was after alteast 12hrs after teh original event.
How can you recreate the memory pressure based on the stack dump?
Another problem is that this is my quasi production machine, so can't put undue pressure on the server.
It already takes a lot of abuse from the MS Access users directly connecting to the sql server.
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 10, 2008 at 2:31 pm
By creating memory pressure, i meant that the stack dump mentions the memory used at the time of dump, so by runnign extraneous queries of big-joins etc .. you can create that scenario.
But would not do this on a production box. Instead, i would suggest contact microsoft support and make them read the stack dump. Sorry out of theories.
October 10, 2008 at 3:04 pm
Thanks!! I guess I have to do that.
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
March 29, 2012 at 12:45 am
Dear All,
I need your help.
I have one production server working on environment Windows Server 2008 (32 bit) with SQL Server 2008 R2 Service pack 1 CU4 (32 bit).
We have created one link server to Oracle 9i server.
I migrated my 2000 database to 2008. I have created link server also.
But after that I am facing a very serious problem.
Sometimes my SQL server stop automatically and when I checked in error log I found stack dump in that. And event viewer log shows me following errors.
SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
The OLE DB provider "MSDAORA" for linked server "IIS" reported an error 0x80004005 aborting the current transaction.
Can anyone please help me on this.
April 2, 2012 at 2:51 pm
Before engaging Microsoft I would first upgrade your SQL Server software. At present you are executing SQL Server 2005 with Service Pack #2 - the stack dump gives you the version - 9.00.3042.00.
I would suggest an upgrade to SQL Server 2005 Service Pack #4 - version 9.00.5000 - at a minimum. To be even more up to date I would also apply MS11-049 security update for SQL Server 2005 Service Pack #4 - getting you to version 9.00.5292.00.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply