This article was previously published under Q191415
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 0325f310 263d3046 59544943 31463525 6c724f3d 0000018f iislog!STR::AppendCRLF (FPO: Non-FPO [4,77,3])
This happens when the NCSA log format is used by selecting "EnableLogging" on the Web Site property page, and the Active Log Format is setto "NCSA Common Log File Format".
This problem is caused by a problem in Iislog.dll, which tries to accessan invalid memory address that results in the above access violation.
This problem can be seen when an invalid client request is sent to the IISserver. The IIS server responds with an error 400 (invalid parametererror) to such requests.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
To work around this problem, do the following:
Disable logging for the Web site that has the problem.
Use W3C Extended Log Format for IIS logging.
Microsoft has confirmed this to be a problem in Internet InformationServer version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.