Post reply

Error [36, 17, 145] occurred while attempting to drop allocation unit

  • May 4, 2015 at 6:41 am

    #296555

    Hi,

    Sine a couple days, we are getting this message the errorlog of one of our SQL2012 server

    LogEntry: Error [36, 17, 145] occurred while attempting to drop allocation unit ID 451879652360192 belonging to worktable with partition ID 451879652360192.

    (version Microsoft SQL Server 2012 - 11.0.5058.0 (X64))

    I am wondering what is the best way trying to troubleshoot this issues? I do not know from which of out database this is coming.

    Thanks,

  • May 14, 2015 at 2:38 pm

    #1798012

    .

  • May 14, 2015 at 11:55 pm

    #1798092

    Does a consistency check return any errors? If so, what errors?

    DBCC CheckDB ('<database name>') with no_infomsgs, all_errormsgs

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • May 15, 2015 at 11:43 am

    #1798289

    Thanks GilaMonster for getting back to me.

    Unfortunately, I ran DBCCs on all DBs. Everything came back okay, no messages or warnings.

    After getting the first occurrences of the messages a few weeks ago, I did some searches and decided to add a second datafile on Tempdb, to avoid contention. This did not resolve the problem.

    I can't figure out form what database this is coming from. Anything to help will be appreciated.

    Thanks

  • May 15, 2015 at 12:55 pm

    #1798308

    Offhand, no idea. Is your SQL instance patched? You may also consider contacting Microsoft Customer Support.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 14, 2015 at 12:17 pm

    #1826498

    I just found this error as well. DBCC Checkdb was clean and was running at the time of the error, completing 45 minutes after the error message occurred and taking a total of 4 hours and 8 minutes to complete. About an hour longer than usual. The message before the error:

    SQL Server has encountered 4706 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [....tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000001798. The offset of the latest long I/O is: 0x00000580b40000

    I don't see this happening earlier this year, so now I'm going to see if there is something new happening on the server at this time.

    Have you discovered anything since your last post?

    Alan Vogan

  • September 14, 2015 at 12:20 pm

    #1826499

    Ack! Forgot....

    MSSQL 2012 11.0.3000

    Windows 2012 R2

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

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