Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Troubleshooting IWSS 3.1 for Windows HTTP service issues

    • Updated:
    • 8 Apr 2020
    • Product/Version:
    • Interscan Web Security Suite 3.1
    • Platform:
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Enterprise
    • Windows 2008 Standard

InterScan Web Security Suite (IWSS) HTTP Service performs content scanning for web browsing and is the main scanning functionality in this application.  Hence, any issue or problem encountered by this service will affect the web access experience of the end users.

This solution provides the steps on how to isolate and address the issue by checking the dependent components. 


Using the IWSS verbose HTTP log, you can identify why the IWSS HTTP service fails to start. The following are the most common causes of this issue:

  1. Check if the SQL server is up.
  2. Telnet to the SQL port to check if it is responding.
  3. Check if the IWSS System DSN in the ODBC Data Sources has the correct configuration.
  4. Go to Administration > Database on the IWSS management console and then perform a test database connection.
  1. Open the intscan.ini file.
  2. Make sure that the value of the "keep_running_if_ldap_fail" parameter is "yes".
  3. Check if the LDAP server is up and running.
  4. Go to HTTP > User Identification on the IWSS management console and verify the LDAP settings.
  1. Check if there is ample disk space for logs and temp files.
  2. Check if verbose logging is enabled. If yes, disable it. Verbose logging significantly increases log size, thus consuming disk space.
  3. Open the IWSS management console and then go to Logs > Settings > System Logs.
  4. Set the number of day by which IWSS will keep system logs.

When an INI, PNI or DSC file is corrupted, IWSS will not be able to read them. This prevents IWSS from loading the configuration at startup. This also applies when the pattern file or URL filtering database is corrupted.

To resolve the issue, contact Trend Micro Technical Support for assistance in verifying the integrity of the files.

If the issue persists or the cause of the issue is not among the four reasons stated above, use the ..\IWSS\UtilBin\CaseDiagnosticTool.exe to collect information. Send the collected information to Trend Micro Technical Support.

Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.