Printable View
dear friends/collegs:
for the past couple of weeks, we've been seeing:
SQL Server Error:
"kernel RA_Setup_IO [Bucket: 0] [slot: 0]: Process 4 generated access violation; SQL Server is terminating this process"
we're running SQL Server 6.5 sp4. on NT 4. sp3
On 2/19/99 8:55:01 AM, Greg wrote:
> dear friends/collegs:
for the past couple of weeks, we've been
> seeing:
SQL Server Error:
"kernel RA_Setup_IO [Bucket: 0] [slot:
> 0]: Process 4 generated access violation; SQL Server is terminating this
> process"
we're running SQL Server 6.5 sp4. on NT 4. sp3
Greg,
I've been seeing a very similar type of error which is..
"Message 17308: Kernel error - Lazywriter. Process (process ID number) generated access violation; SQL Server is terminating this process."
I have WinNT 4.0 Server Enterprise Edition loaded with SP4 and MS SQL Server 6.5 Enterprise Edition with SP5 installed.
I have 7 seperate active databases on the server supporting 7 different applications. The server has been on-line for approximately 4 weeks and just recently (last Thursday) it has started to "lock up" every couple of days. By lockup I mean that it starts to reject all requests by all users. No one can connect to the server including myself. The MS SQL error log grows and grows until we reboot the server. The error logs are 100 Mb or larger in size due to rejection errors being repeated over and over again.
We have an incident in with Microsoft but they are not responding fast enough.
Have you experienced the same "lock up" of the server when you receive these messages?
Jim
OK.
Then, what does perfmon tell you about "RA Slots Per Thread" and "RA Worker
Threads" - are there any signs of disk queuing? How is the overall performance?
On 2/23/99 9:03:53 AM, Greg wrote:
> I think, it's more because of NT server/hardware configuration
> itself.
RA(read-ahead) manager deals with memory/disk system, plus
in
> error message it says "kernel"......? and we didn't change RA
> configuration
settings for SQL Server.
On 2/22/99 3:55:15 PM, Frank
> Garcia (DBA) wrote:
> Access Violations are system bugs. You should
> contact Microsoft
> regarding
this error. You will have to keep track
> of all your error logs
> and zip them up along with your configuration
> files for Microsoft
> Support.
You will also have to experiment with
> work arounds until
> Microsoft comes
up with a suggestion.
If you are
> running service pack
> 4; service pack 5a can be downloaded. I'm
> not
sure how safe this
> would be - So if you have a test environment
> you should
probably install
> it there first to make sure that this
> will not bring
additional
> problems.
We are still waiting for
> Microsoft to tell us why we are
> experiencing Access Violations, however
> we have been able to run without
> major problems with the following
> steps:
We took our configurations back
> to default. As a start and
> built from there.
We isolated the transactions
> that were causing the
> problems. Usually unhandled implicit or long running
> transactions are
> good suspects for
Access Violations being raised. We
> reworked all of
> the transactions to the
point where we suffer AV's
> once in a
> while but I know exactly where they are coming from.
we are
>
> currently running on Alphas with service pack 4.
I hope this
>
> helps...
On 2/19/99 8:55:01 AM, Greg wrote:
> dear
>
> friends/collegs:
for the past couple of weeks, we've been
>
>
> seeing:
SQL Server Error:
"kernel RA_Setup_IO [Bucket: 0] [slot:
>
>
> 0]: Process 4 generated access violation; SQL Server is terminating
>
> this
> process"
we're running SQL Server 6.5 sp4. on NT 4.
> sp3