Post reply

Deadlocks from MSIS account

  • April 8, 2011 at 9:29 am

    #249117

    I working on a problem with deadlocks, we have a table to report on any deadlocks encountered. The deadlocks I am working on are very tricky to reproduce so running a trace does not help me. The deadlocks I can work through but what I am not sure about is deadlocks reported under an MSIS account. I can see no login or user in sql server named MSIS.

    In the logging table I set up I see the following for deadlocks

    1. Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    -- this is reported under the login that called the procedure that was deadlocked

    2. Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    -- this is reported under the login MSIS and does not specify a procedure that was deadlocked

    Can anyone help me understand where the MSIS account comes from?

  • April 8, 2011 at 1:33 pm

    #1309377

    Some random thoughts...

    1. MSIS = Microsoft Integration Services? Maybe a local Windows account or Domain account accessing the server via an AD group?

    2. Re: the logging table you have setup...do you know about Extended Events in 2008? http://www.sqlservercentral.com/articles/deadlock/65658/%5B/url%5D

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • April 8, 2011 at 1:50 pm

    #1309388

    Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.

    DBCC TRACEON(1222,-1)

    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

  • April 11, 2011 at 10:34 am

    #1309947

    Problem resolved, it turned out the msis account was hard coded in on the stored procedures used by our system. It did not resolve the deadlock issue but the mystery login is no longer a mystery.

    I will try the new features in 2008 to help determine the source of our deadlocks.

    Thanks for the tip!

Viewing 4 posts - 1 through 4 (of 4 total)

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