Post reply

Need to worry about this error?

  • July 25, 2011 at 10:59 am

    #241305

    The client was unable to reuse a session with SPID , which had been reset for connection pooling. The failure ID is . This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

    In error log i founnd this:

    Error: 18056, Severity: 20, State: 29

  • July 25, 2011 at 11:03 am

    #1357985

    What other errors do you have around that time?

  • July 25, 2011 at 11:04 am

    #1357986

    Here's what MSDN says about severity 20:

    20-25

    Indicate system problems and are fatal errors, which means that the Database Engine task that is executing a statement or batch is no longer running. The task records information about what occurred and then terminates. In most cases, the application connection to the instance of the Database Engine may also terminate. If this happens, depending on the problem, the application might not be able to reconnect.

    Error messages in this range can affect all of the processes accessing data in the same database and may indicate that a database or object is damaged. Error messages with a severity level from 19 through 25 are written to the error log.

    20

    Indicates that a statement has encountered a problem. Because the problem has affected only the current task, it is unlikely that the database itself has been damaged.

    So, yeah, something important, but not something that probably damaged your database.

    Definitely worth digging in to.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • July 25, 2011 at 11:56 am

    #1358026

    No errors other than this

  • July 25, 2011 at 11:59 am

    #1358031

    Nothing??

    What does this return?

    CREATE TABLE #logs (LogDate DATETIME, ProcessInfo VARCHAR(50), Txt VARCHAR(MAX))

    INSERT INTO #logs (LogDate, ProcessInfo, Txt)

    EXEC master.sys.xp_readerrorlog 0,1

    INSERT INTO #logs (LogDate, ProcessInfo, Txt)

    EXEC master.sys.xp_readerrorlog 1,1

    INSERT INTO #logs (LogDate, ProcessInfo, Txt)

    EXEC master.sys.xp_readerrorlog 2,1

    SELECT * FROM #logs

    WHERE LogDate BETWEEN DATEADD(D, -1, DATEDIFF(D, 0, GETDATE())) AND GETDATE()

    -- AND Txt NOT LIKE 'The activated proc %'

    -- AND Txt NOT LIKE 'Login failed for user%'

    -- AND Txt NOT LIKE 'Erreur : 18456, Gravité : 14%'

    AND Txt NOT LIKE 'Log was backed up. Database: PROD-FORDIA%'

    -- AND Txt NOT LIKE '%Trace%'

    AND Txt NOT LIKE '%TEST_RESTORE%'

    AND Txt NOT LIKE '%CHECKDB%'

    -- AND Txt NOT LIKE '%PROD-BACKUP%'

    AND Txt NOT LIKE '%PROD-FORDIA_test_restore%'

    -- AND Txt NOT LIKE '%Starting Job Ceridian Paye XLS%'

    -- AND Txt NOT LIKE '%PROD-FORDIA_test_moul_FF80%'

    AND Txt NOT LIKE '%cachestore flush%'

    AND Txt NOT LIKE 'Database backed up. Database%'

    AND Txt NOT LIKE 'This instance of SQL Server has been using a process ID%'

    AND Txt NOT LIKE 'SQL Trace %'

    AND Txt NOT LIKE 'Erreur : 18456, Gravité : 14, État : 8.'

    AND Txt NOT LIKE 'I/O was resumed on database%'

    AND Txt NOT LIKE 'I/O is frozen on database%'

    --WHERE LOWER(Txt) LIKE '%memory%'

    ORDER BY LogDate DESC

  • July 25, 2011 at 12:22 pm

    #1358051

    There are no other errors in error log. I went through the error log. Any way let us c if it prompts again.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply