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

Create a technical support case if you need further support.

Memory usage of lsass.exe increases when the Security Agent is running

    • Updated:
    • 27 Aug 2015
    • Product/Version:
    • Worry-Free Business Security Standard/Advanced 7.0
    • Platform:
    • Windows 2003 Standard
    • Windows 2008 Enterprise
    • Windows 2008 Essential Business Server
    • Windows 2008 Small Business Server
    • Windows 2008 Standard
    • Windows 2011 Small Business Server Essentials
    • Windows 2011 Small Business Server Standard
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
Summary

When the Security Agent is running, the process lsass.exe's memory usage increases. The issue disappears when the Trend Micro Solution Platform service is disabled.

When you identify when the issue happened and check the Internet Information Services (IIS) logs for that period, you find the 401.1 error for port 8082 requests, like the one below:

2011-12-08 14:23:35 10.35.5.1 GET /tmcss/ LCRC=9C4E654146B6CBFA4E9DFE0CD913B3B85A0753D5E20A5BA903B68F53C506AD69 8082 - 10.35.5.66 WFBS;17.0;2316;a4f71263-504c-4cd3-b77a-f378ba2f79d5;4f337fbe-07a8-484a-9ed8-5eead0877b7f;Af9CAWBk 401 1 0
Details
Public

To resolve the issue:

 
This troubleshooting procedure applies to IIS 6.0.
  1. Open the IIS Manager.
  2. Expand the websites.
  3. Right-click either the OfficeScan or Smart Scan website and select Properties.
  4. Select Directory Security tab.
  5. Click Edit under Anonymous access and authentication control.
  6. Replace the default username (IUSR_ServerName) and password with administrator account and password.
  7. Click OK to exit the IIS configuration interface.
  8. Restart the IIS service or run iisreset on the command prompt.
  9. Start or load the Security Agent.
  10. Open task manager and observe the lsass.exe memory usage.

The issue will no longer occur after the procedure above. The IIS logs should now have "200" instead of "401.1" results for requests to port 8082.

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060052
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.


Need More Help?

Create a technical support case if you need further support.