none
BHM Report- Error- Long time waiting SPID(s) detected on SQL Server RRS feed

  • Question

  • We are getting the below Critical Warning after running the BHM report. Could you please let me know the steps that need to be followed in order to fix this issue?

    Details
    Category:Other MsgBox Checks 
    Caption:Long time waiting SPID(s) detected on SQL Server ABC
    Value:Longer time waiting SPID : 411 (200617 ms) 
    Tuesday, May 23, 2017 9:01 AM

All replies

  • HI,

    Any other errors on the vent log of the sql server?? The SQL server resources are blocked hence you are getting this error.

    Do you get any other warning in the BHM report?


    Mandar Dharmadhikari

    Wednesday, May 24, 2017 12:24 AM
    Moderator
  • Hi Vipin

    First make sure that all the BizTalk SQL Agent Jobs are running fine as per schedule - you can do a View History on each of the Jobs in SQL Server Agent to check this out.

    If they are okay, you will have to investigate what those SPIDs correspond to. This should help-

    https://www.mssqltips.com/sqlservertip/2429/how-to-identify-blocking-in-sql-server/


    Thanks Arindam

    Wednesday, May 24, 2017 12:34 AM
    Moderator
  • Ran the below query and from the results we came to know that the processes were related to BizTalk and hence we restarted all the host instances. This fixed the issue.

    select * from master..sysprocesses t where spid>50 order by waittime desc

    Tuesday, July 11, 2017 1:50 PM