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

Create a technical support case if you need further support.

Troubleshooting pattern deployment issues for Normal Servers (NS) on ServerProtect

    • Updated:
    • 13 Apr 2016
    • Product/Version:
    • ServerProtect for Microsoft Windows/Novell Netware 5.8
    • ServerProtect for Storage 6.0
    • Platform:
    • Windows 2000 Advanced Server
    • Windows 2000 Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Enterprise
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2012 Enterprise
Summary

Perform these steps when the ServerProtect Information Server (IS) is able to download the pattern file but the Windows Normal Servers (NS) do not receive the update.

Details
Public

If Windows Normal Servers are not getting updated:

  1. Check if the following services are started on the NS:
    • Remote Registry service
    • RPC service
    • RPC locator service
  2. Verify the following:
    1. Ping the NS from IS and vice versa using both IP address and host name.
    2. Access the C$ drive from NS to IS and vice versa. Make sure that port 3628 and 5168 are open in the firewall. The IS is listening to port 3628 and NS is listening to 5168.
    3. Check the TCP/IP configuration on IS.
      1. Make a backup of TmRpc.ini file found in the ..\Program Files\Trend\SProtect directory.
      2. Check if all the listed NS has a value of "2". For example, 10.10.10.10=2.
  3. Check if EventMsg2.dll is located in the ..\SProtect folder and ..\winnt\system32 folder of NS.
  4. Check if the latest ServerProtect patch has been installed.
  5. Verify that a task on IS is deploying the pattern to NS on a regular basis.
    1. Open the management console.
    2. Click the NS or domain and click Task > Existing Task to view the tasks assigned to a server.
    3. Click View to see the contents of a task.

If pattern files are still not deployed, collect and send the following files to Trend Micro Technical Support:

  • SPNT.log
    To get this file:
    1. Open the SPNT management console.
    2. Select the NS that is unable to receive the pattern update.
    3. Click Do > Create Debug Info.
    4. Select Enable debug log on the Debug Log Management page.
    5. Select Trace all messages, then select Normal Server.
    6. Select Output to a debug file, then type the path and filename of the log in the Directory field.
    7. Click OK > Apply.
    8. Deploy the pattern file and collect the SPNT.log file.
    9. Disable the debug log.
  • Tmudump.txt located under the ..\Program Files\Trend\SProtect\AC_Up-Rb.tmp\AU_Log directory.
  • IS Update log
    To get this file:
    1. On the IS, select the NS that is unable to receive the pattern update.
    2. Click View Log on the left side of the console.
    3. Select Update as the log type and specify the date range when the issue occurred.
    4. Click Export and save the Update log to a CSV file.
Premium
Internal
Rating:
Category:
Deploy; Update
Solution Id:
0124613
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.