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 |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2002-03-18 : 05:42:57
|
| Just got this - thankfully on a dev box. Tracked down the quilty culprit, in the sense oif who caused it, from the dmp file. What I can't see yet is WHY?SQL error message is:**********Error: 0, Severity: 21, State: 0SQL Server is aborting. Fatal exception 0 caught.**********BOL covers errors 1 to 21999 from the looks of things.In case anyone wants, I can send the DMP file contents (44K).If anyone can give me a pointer, I'd appreciate it.Off to the MS site now... |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-03-18 : 12:39:30
|
| Again,This is an access violation. 99.5% of the time it is a bug in SQL Server. Try the latest Service pack. If that doesn't resolve it, call MS Product Support. Since it is a bug, the call will be free.I feel like a broken record. Perhaps this can be posted in the FAQs?-Chad |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2002-03-19 : 02:07:58
|
| Thanx for the response Chad.I tried searching the SQLTeam apges for Error 0, got nowhere .... I guess people didn't use that as their description. Unfortunately, the MS online web site was unable to return decent match when searching for Error 0. Amongst others, a refernce to SP3 came up, but that page repeatedly refused to load properly.My problem is that, unfirtunately, we're running a packaged solution on the server, and it isn't certified for SP3 by the company who wrote it. Guess this gives me more ammo to push for it.Thanx again... |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-03-20 : 00:53:46
|
| Yeah,Error 0 is usually logged for an access violation. Search for access violation, and you will find many posts by me. Error 0 does not identify the problem, so you will not find any knowledge base articles. The short stack dump is the only way to diagnose the problem. Call Support, they may be able to give you a workaround that doesn't require SP3. Again, it is likely a bug in SQL server, so you won't have to pay.-Chad |
|
|
|
|
|
|
|
|
SQL ERROR 0 - SQL aborting