sc-win32-status 121 and 1236 in IIS log

6,590

Could be a denial of service attack via and improperly set MinFileBytesPerSec metabase setting.

For details:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0b447dba-6bcc-4238-a932-0e083170c3ab.mspx?mfr=true

Share:
6,590

Related videos on Youtube

Shiraz Bhaiji
Author by

Shiraz Bhaiji

Architect / dev lead / .net programmer Manager at Evry http://www.evry.no/ Board Member Oslo Software Architecture http://www.meetup.com/Oslo-Software-Architecture/

Updated on September 17, 2022

Comments

  • Shiraz Bhaiji
    Shiraz Bhaiji over 1 year

    I am trying to solve some performance problems.

    We have a web server that calls another web server with WCF services installed.

    There are about 20,000 calls in 1 hour, most are a few milliseconds.

    But about 20 of them are 10 to 50 seconds

    All of these have sc-win32-status 121 or 1236.

    Question is what could be causing sc-win32-status 121 or 1236, and how could I solve this?

    • MikeT
      MikeT over 13 years
      are they with sc-status 200?
  • Shiraz Bhaiji
    Shiraz Bhaiji over 13 years
    Thanks for the answer, it turned out that it was just normal use of the system with browser caching turned off
  • Joy George Kunjikkuru
    Joy George Kunjikkuru almost 6 years
    Hi @ShirazBhaiji, Were you able to solve the issue by reducing MinFileBytesPerSec setting from its default?