Re: SP1 does not work

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 04/21/04


Date: Wed, 21 Apr 2004 13:23:24 +0200

Perhaps you hit some other bug then the one referred to in SP1? I suggest you open a case with MS Support for
this.

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"AA" <not@noreply.com> wrote in message news:e$OO5w3JEHA.208@tk2msftngp13.phx.gbl...
> This mail is regarding a trouble I'm facing with SQL Server 2000. I'm
> working with ASP .NET V 1.1 and SQL Server 2000. I have a reporting module
> that generates XML reports from the SQL Server 2000 database. Things are
> fine and running, but at times I get a fatal SQL Server Exception when I
> access reports continuously. That is, this error occurs after I generate a
> report and immediately invoke another report. But the same process works
> without any problem some other time!
> The exception says" Process 55 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process."?
>
>
>
> Searching the cause of this bug, I learnt that the fix for this SQL bug is
> in SQL Server 2000 Service Pack 1. I installed it, but the error is still
> there. I tried service pack 3 also, but of no use. I also tried connecting
> to the database by setting "pooling=false" in the connection string so that
> every time I go to the database with a new connection. I did this thinking
> that it might be a corrupted connection in the pool which is creating the
> error, but of no effect.
>
>
>
> From the error, I can assess that it's an unmanaged memory violation
> exception that is occurring at the server. I also doubt whether it's any
> deadlock occurring at the server when the current connection tries to access
> the resource occupied by a previously unclosed connection in the database.
>
>
>
> I also got one more misleading error in the same context, which says
> "General Network Error. Please check your network documentation". I wonder
> whether this error is related to the previous bug.
>
>
>


Relevant Pages

  • Re: ASP.NET 2.0 - a newbie question
    ... the exception can be identified using the exception stack trace below. ... established connection failed because connected host has failed to ... connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& ... Microsoft SQL Server? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Driver corrupts prepared statements in pool.
    ... This test case demonstrates a bug in the Microsoft SQL Server 2005 JDBC ... cause an exception the next time it is used. ... Microsoft SQL Server 2005 JDBC driver 1.0.809.102 ... // A connection will NOT work properly until it has been ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: HELP on New request is not allowed to start because [1264822]
    ... Do you have a link to the bug? ... application doen't raise any exception during a distributed transaction. ... This error always occurs when we issue the command to SQL Server. ...
    (microsoft.public.dotnet.framework.adonet)
  • Losing SQL Server Connections every 30-90 seconds
    ... Our SQL Server runs on a different server than the BizTalk server. ... BizTalk processes running when the connection is lost and our Orchestrations ... Exception type: ServiceCreationException ...
    (microsoft.public.biztalk.general)
  • Re: SP1 does not work
    ... Perhaps you hit some other bug then the one referred to in SP1? ... > This mail is regarding a trouble I'm facing with SQL Server 2000. ... but at times I get a fatal SQL Server Exception when I ... > every time I go to the database with a new connection. ...
    (microsoft.public.sqlserver.programming)