IIS DeadlockedRSS

25 replies

Last post Oct 23, 2019 06:57 AM by Jalpa Panchal

  • IIS Deadlocked

    Apr 24, 2019 09:02 AM|AshutoshApte|LINK

    <div class="wrapper"> <div id="ng-view"> <div class="grid-container"> <div class="row"> <div> <div> <div class="analysisSummarySection"> <div id="analysisSummaryGroup"> <div class="summaryGroup mt20 normalText" id="errorsAnalysisSummarySection"> <div class="group mt20">

    We did a crash dump analysis on w3wp and following are the results. Is it something related to Microsoft or is it our software code? The application is in Classic ASP and the application pool fails to respond to a ping only for one client.

    Detected a serious critical section related problem in w3wp.exe__Ashutosh__PID__6224__Date__04_23_2019__Time_10_35_17AM__191__Manual Dump.dmp
    Lock at combase!g_MTAInitLock+14 owned by thread 69 is Deadlocked with lock at combase!g_mxsSingleThreadOle+14 owned by thread 105

    Impact analysis

    85.97% of threads blocked

    (Threads 2 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548)

    The following functions are involved in the root cause
    combase!COleStaticMutexSem::Request+17 [d:\blue\com\combase\common\olesem.cxx @ 197]

    The following modules are involved in the root cause
    C:\Windows\System32\combase.dll from Microsoft Corporation

    </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>

  • Re: IIS Deadlocked

    Apr 25, 2019 01:58 AM|Jalpa Panchal|LINK

    Hi AshutoshApte,

    Could you please tell us which OS you are using? If possible please use IIS 7 or above version.

    Try to set Application pool  Advance setting increase the ping timeout or set “ping enabled” to false until you collect the memory dump. 

    Run failed request tracing in iis:

    https://docs.microsoft.com/en-us/iis/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/using-failed-request-tracing-to-troubleshoot-classic-asp-errors

    Regards,

    Jalpa.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Apr 25, 2019 07:35 AM|AshutoshApte|LINK

    Hi Jalpa,

    The OS is Windows 2012 R2 and its on IIS 6. Ping Maximum Response Time and Ping Period both set to 10. Can you please tell me what is the significance of Ping Enabled set to False and dump? We have already taken dump and it shows deadlock. If we change Ping settings as you suggested, will it solve the deadlock issue?

    Thank you in advance.

    Regards

    Ashutosh Apte

  • Re: IIS Deadlocked

    Apr 25, 2019 07:44 AM|Jalpa Panchal|LINK

    Hi,

    The process is suspended when a dump is written to the disk, which means that it will not respond to WAS’ ping request and if that exceeds the ping maximum response times then WAS will terminate the process.

    If you see the similar behavior and you need to collect a useful dump then you may need to increase the ping timeout or set “ping enabled” to false until you collect the memory dump.

    For more detail you could see the below article:

    https://blogs.msdn.microsoft.com/amb/2015/03/26/iis-application-pool-may-be-terminated-while-collecting-dump/

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Apr 25, 2019 07:46 AM|Jalpa Panchal|LINK

    If possible try to use iis 8.5 rather than using iis 6. IIS 8.5 has more functionality and feature than iis 6.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Apr 25, 2019 07:58 AM|AshutoshApte|LINK

    Thank you Jalpa for explanation. I will try these changes and let you know what happens.

  • Re: IIS Deadlocked

    Apr 26, 2019 08:44 AM|AshutoshApte|LINK

    Hi,

    A small correction is we have IIS 8.5 itself. 

    Before I enable failed request tracing and set ping enabled to false, I have couple of question.

    The main issue is our application pool hangs intermittently and hence the portal becomes unresponsive. There will be no Status Code since the portal is unresponsive. So, while enabling Failed Request Tracing rule which option should I choose?

    Do we have any update on the deadlock error that debugdiag showed in my first post?

    Also, following event is thrown everytime we have a portal unresponsiveness. The application pool is set as "Network Service" and not "Application Pool Identity".

    And Ping maximum response time and ping period both are set to 10 sec.

    EventID            : 5010

    MachineName        : USPRO01

    Data               : {}

    Index              : 70208

    Category           : (0)

    CategoryNumber     : 0

    EntryType          : Warning

    Message            : A process serving application pool 'Ashutosh' failed to respond to a ping. The process id was

                         '4216'.

  • Re: IIS Deadlocked

    May 07, 2019 10:41 AM|AshutoshApte|LINK

    Hi Team,

    Any update on this? We are still getting errors from Microsoft dlls in DebugDiag Analysis.

    <div class="wrapper"> <div id="ng-view"> <div class="grid-container"> <div class="row"> <div> <div> <div class="analysisSummarySection"> <div id="analysisSummaryGroup"> <div class="summaryGroup mt20 normalText" id="errorsAnalysisSummarySection"> <div class="group mt20">

    combase!COleStaticMutexSem::Request+17 [d:\blue\com\combase\common\olesem.cxx @ 197]
    combase!_CoInitializeEx+114 [d:\blue\com\combase\class\compobj.cxx @ 3622 + 13]
    ntdll!LdrpAcquireLoaderLock+29

    The following modules are involved in the root cause
    C:\Windows\System32\combase.dll from Microsoft Corporation
    C:\Windows\System32\ntdll.dll from Microsoft Corporation

    <div class="wrapper"> <div id="ng-view"> <div class="grid-container"> <div class="row"> <div> <div> <div class="analysisSummarySection"> <div id="analysisSummaryGroup"> <div class="summaryGroup mt20 normalText" id="warningsAnalysisSummarySection"> <div class="group mt20">
    The following functions are trying to enter this critical section
    asp!CViperActivity::PostAsyncRequest+60

    The following module(s) are involved with this critical section
    \\?\C:\Windows\System32\inetsrv\asp.dll from Microsoft Corporation
    </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>
    </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>
  • Re: IIS Deadlocked

    May 08, 2019 07:08 AM|Jalpa Panchal|LINK

    Hi,


    Firstly print the stack trace from dump using windbg and look for the hang threads.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 01, 2019 12:27 PM|AshutoshApte|LINK

    I need to get analysis done for one dump file from DebuDiag. Can you please help me with that? How can I send you the dump file?

  • Re: IIS Deadlocked

    Oct 08, 2019 02:28 PM|AshutoshApte|LINK

    Type Description Recommendation
      Error Detected a serious critical section related problem in W3WPEX~1.DMP
    Lock at combase!g_mxsSingleThreadOle+14 is Orphaned

    Impact analysis

    1 critical sections indirectly blocked

    (Critical Sections combase!g_MTAInitLock+14)

    64.84% of threads blocked

    (Threads 2 3 37 38 41 45 48 50 52 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127)

    The following functions are involved in the root cause
    combase!COleStaticMutexSem::Request+17
    combase!_CoInitializeEx+114

    The following modules are involved in the root cause
    C:\Windows\System32\combase.dll from Microsoft Corporation
    The critical section at combase!g_mxsSingleThreadOle+14 has been orphaned, which means the owning thread is no longer present in the process. In most cases this is due to an earlier exception causing the thread to terminate without leaving (unlocking) the critical section. Consider the following approach to determine root cause for this critical section problem:
    1. Use a DebugDiag crash rule to monitor the application for exceptions which cause the owing thread of the critical section to exit prematurely
    2. If there are no such exceptions, enable 'lock checks' in Application Verifier
      • Download Application Verifier from the following URL:
             Microsoft Application Verifier
      • Enable 'lock checks' for this process by running the following command:
             Appverif.exe -enable locks -for w3wp.exe
      • See the following document for more information on Application Verifier:
             Testing Applications with AppVerifier
      Warning Detected possible blocking or leaked critical section at asp!g_ViperReqMgr+2c owned by thread 47 in W3WPEX~1.DMP

    Impact of this lock

    2.34% of threads blocked

    (Threads 6 7 35)

    The following functions are trying to enter this critical section
    asp!CViperActivity::PostAsyncRequest+60

    The following module(s) are involved with this critical section
    \\?\C:\Windows\System32\inetsrv\asp.dll from Microsoft Corporation
    The following vendors were identified for follow up based on root cause analysis

    Microsoft Corporation
    Please follow up with the vendors identified above
  • Re: IIS Deadlocked

    Oct 09, 2019 09:28 AM|Jalpa Panchal|LINK

    Hi,

    You could share the dump file on one drive and share that link with us.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 10, 2019 03:20 PM|AshutoshApte|LINK

    Here is the link to the dump file. Please note that this link will expire in 1 day

    https://atos365-my.sharepoint.com/:u:/g/personal/ashutosh_apte_atos_net/EZQuAOIigx9DpGyY_-6SV9QBs2IX1zHveMxpAzsQyTfQYg?e=kNdHPf

  • Re: IIS Deadlocked

    Oct 15, 2019 02:11 PM|AshutoshApte|LINK

    Please let me know if you have received the file. If not I will put the file on OneDrive again.

  • Re: IIS Deadlocked

    Oct 16, 2019 07:08 AM|Jalpa Panchal|LINK

    it shows that the link is expired. 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 16, 2019 11:07 AM|AshutoshApte|LINK

  • Re: IIS Deadlocked

    Oct 17, 2019 01:21 AM|Jalpa Panchal|LINK

    I will give you a response soon after reviewing the dump file. 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 21, 2019 11:29 AM|AshutoshApte|LINK

    Hi Jalpa,

    Any update?

  • Re: IIS Deadlocked

    Oct 22, 2019 06:13 AM|Jalpa Panchal|LINK

    Hi,

    do you make any calls to COM component? 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 22, 2019 07:29 AM|AshutoshApte|LINK

    Yes we do. 

  • Re: IIS Deadlocked

    Oct 22, 2019 07:31 AM|Jalpa Panchal|LINK

    what com component you use?

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 22, 2019 07:34 AM|Jalpa Panchal|LINK

    asp itself is a single thread model, thread lock may happen in the com component. classic asp does not support multi-thread.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 22, 2019 07:38 AM|AshutoshApte|LINK

    No we have not used multi-threads. Are you seeing any COM calls in the dump? 

  • Re: IIS Deadlocked

    Oct 22, 2019 07:40 AM|Jalpa Panchal|LINK

    what com component you use?

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: IIS Deadlocked

    Oct 22, 2019 03:50 PM|AshutoshApte|LINK

    We have quite a few VB6 Dlls which are getting used from ASP.

  • Re: IIS Deadlocked

    Oct 23, 2019 06:57 AM|Jalpa Panchal|LINK

    Hi,

    CoInitializeEx this method is used for initializing com component.combase!COleStaticMutexSem::Request this is method call in com component.ntdll!RtlEnterCriticalSection goes to the system internal. 

    Critical Section: combase!g_mxsSingleThreadOle Owning Thread ID: 0x124c - Warning!!! Thread ID does not exist in current process. Orphaned Critical Section. this means code is trying to acquire the mutex.from thread 0x124c .0:003> !mex.t -t 0x124c
    Invalid thread.this command indicate thread 0x124c does not exist anymore.

    all the other request is waiting for the dead thread to release the lock.so, check VB code, you can try to remove the mutex or lock-in VB than test again.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.