Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Teroman
Posting Yak Master
115 Posts |
 Posted - 2002-03-07 : 12:45:23
|
| Ok, this is driving me right up the wallMy proc I was working on was working fine yesterday, and today i went to finish it off.I tried to run it and got:ODBC: Msg 0, Level 19, State 1SqlDumpExceptionHandler: Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionWrite (GetOverLappedResult()).[Microsoft][ODBC SQL Server Driver]Communication link failureConnection BrokenOh joy!!Ive tracked it down to something that was working fine, a pretty complex select that inserts into a temp table.I messed about with this for ages, and it seemed to work. The long and the short of it is it runs fine as a select, takes only a couple of seconds, but if i replace the "insert into #temptbl(...)" line it fails again.I honestly havn't a clue whats happening.Dont think its just temp tables though, do an insert into another one just before this, and that works fineany ideas, or im going to abandon this and go on a mission to invent new and interesting swear words to call my pcthankscol |
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2002-03-20 : 16:26:30
|
| hey col - post your select statement - PS what's your version?--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-20 : 16:35:11
|
| According to Chadmat, who works in MS Tech Support, Access Violation errors are almost always due to bugs (99%). If you don't have the latest service pack installed, try installing it and see if it fixes the problem. If that doesn't fix it, contact MS and open a case with them (Product Support Services), it will cost you nothing if it's a bug.Can you configure your setup to use TCP/IP instead of named pipes? The named pipes library appears to be the culprit. |
|
|
|
Jay99
468 Posts |
Posted - 2002-03-20 : 16:37:24
|
| If you select statement references and views, especially indexed views, post the ddl for those too . . .AV's are usually (almost always) caused by a SQL Server bug. Either apply the latest service pack, call microsoft (free since its a bug), or rewrite it so it doesn't cause the AV . . . "pretty good software, for the masses"Jay<O> |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-03-20 : 18:17:03
|
| Rob,I USED to work in Support. I am now an MCS consultant.Let me explain why I always qualify this with the 99% thing. AVs should ALWAYS be bugs, but I have seen where somenoe mucked around with the system tables, and then all of a sudden the server starts AVing.So, I always qualify that, I don't want to tell someone the case will be free if it turns out they did something stupid and the AVs are their fault.-Chad |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-20 : 23:06:21
|
 See guys, whenever I say something, DON'T BELIEVE ME! |
|
|
|
|
|
|
|
|
Strange problem inserting into a Temp table