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 |
|
smccreadie
Aged Yak Warrior
505 Posts |
 Posted - 2001-12-17 : 12:42:17
|
| In an application I'm developing, I got the following error message from the Messenger Service:SQL Server Alert System: 'Demo: Sev. 19 Errors' occured on \\PHARMDATADATETIME: etc.DESCRIPTION: Error 0, Severity: 19, State: 0SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.COMMENT: (None)JOB RUN: (None)According to BOL, all Sev 19 errors should be reported to the DBA (me), however I'm not sure what to do with this. The system was running a complex SPROC at the time with several pulls from a linked Oracle server.Any ideas? |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2001-12-17 : 18:13:14
|
| You have gotten an access violation.You should call Microsoft Product Support Services. I know, you are saying "I don't want to pay $245 to fix this" but wait! 99.9% of access violations are bugs in the product. The only time an AV is not considerted a bug is if you are doing something which is not supported, such as modifying system tables etc...Anyway, Microsoft does not charge for support if the inncident is the result of a bug.-Chad |
 |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2001-12-17 : 19:47:04
|
| OK, if it happens again, I will call. We've got some sort of premier support contract so it doesn't come directly out of my pocket. |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2001-12-18 : 00:31:26
|
| If you still have the errorlogs (Actually there should be a dump file in your Log directory) I wouldn't wait for it to happen again. Especially since you have a Premier contract, your company is paying for the incidents anyway, you might as well use them. Besides, like I said, your account won't be decremented because it is most likely a bug.-Chad |
|
|
|
|
|
|
|
|
Severity 19 Error - what to do?