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