|
Home > Archive > MS SQL Server > March 2005 > SQL Agent Stops
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| DanielK. 2005-03-30, 9:40 am |
| Hallo
I`m using Windows 2000 Server Standard.SQL 2000 SP3a.
While Deleting and rebuilding Indexes, the following errors occured....
17310 :
SqlDumpExceptionHand
ler: Process 2888 generated fatal exception c0000005
EXCEPTION_ACCESS_VIO
LATION. SQL Server is terminating this process.
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
After that SQL Agent stopped. I stared it again and everthing was ok.
Bye
| |
| Andreas Mavrogenis 2005-03-30, 9:40 am |
| Hi,
Did you checked if any backups were running during re-indexing database. It
is possible that when you stoped the SQL Agent, all opened connections were
closed and then there were free unlocked indexes to re-index
Check in the EM -> SQL Agent --> jobs for failures
Andreas
"DanielK." wrote:
> Hallo
>
> I`m using Windows 2000 Server Standard.SQL 2000 SP3a.
>
> While Deleting and rebuilding Indexes, the following errors occured....
>
> 17310 :
> SqlDumpExceptionHand
ler: Process 2888 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIO
LATION. SQL Server is terminating this process.
>
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
>
> After that SQL Agent stopped. I stared it again and everthing was ok.
>
> Bye
| |
| DanielK. 2005-03-30, 9:40 am |
| Hello
No, there was only a TRN backup running. The SQL service stopped unexpectedly.
"Andreas Mavrogenis" wrote:
[color=darkred]
> Hi,
>
> Did you checked if any backups were running during re-indexing database. It
> is possible that when you stoped the SQL Agent, all opened connections were
> closed and then there were free unlocked indexes to re-index
>
> Check in the EM -> SQL Agent --> jobs for failures
>
> Andreas
>
> "DanielK." wrote:
>
| |
| Andreas Mavrogenis 2005-03-30, 9:40 am |
| Hi,
Check the Event Viewer of your machine and point out the specific error. It
probably tell you more about.
Also check SQL Server logs to trace the unexpected stop
Check if the TRN backup was started at the time you did the re-indexind.
Andreas
"DanielK." wrote:
[color=darkred]
> Hello
>
> No, there was only a TRN backup running. The SQL service stopped unexpectedly.
>
>
> "Andreas Mavrogenis" wrote:
>
|
|
|
|
|