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

Create a technical support case if you need further support.

The ServerProtect for Microsoft Windows/Novell Netware 5.8 Information Server is unable to deploy pattern updates to the Normal Server

    • Updated:
    • 21 Sep 2016
    • Product/Version:
    • ServerProtect for Microsoft Windows/Novell Netware 5.8
    • Platform:
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Small Business Server
Summary
ServerProtect for Microsoft Windows/Novell Netware 5.8Information Server (IS) cannot push update to the Normal Server (NS) after scheduled or manual update.
The following appears in the logs:
----cut----
Inf 20091028 16:47:39 2116 7096 Downloading [.\serverprotect\spnt580\auspnt50.zip] to [C:\Program Files\
Trend\SProtect\AC_Up-Rb.tmp\AU_Data\AU_Temp\2116_7096\AU_Down\serverprotect\
spnt580\auspnt50.zip]...
Inf 20091028 16:47:39 2116 7096 Download cancelled by user in Get_File_Info
Inf 20091028
Upon checking the product list on the IS, there was no auspnt50.zip:
------cut-----
[C:\Program Files\Trend\SProtect\SpntShare\ServerProtect\spnt580\]
2009/10/15 11:49 <DIR> .
2009/10/15 11:49 <DIR> ..
0 File(s) 0 bytes
------cut-----
Or, it seems that the auspnt50.zip file is incorrect:
-----cut-------
[C:\Program Files\Trend\SProtect\SpntShare\ServerProtect\spnt580\]
2009/10/26 16:51 <DIR> .
2009/10/26 16:51 <DIR> ..
2009/10/26 11:01 26663 auspnt50.zip
-----cut-------
Details
Public
To resolve this issue, do the following:
  1. Download the AUSPNT50.zip file.
  2. After downloading, make sure that the file size is 43914 bytes.
  3. Copy the file under C:\Program Files\TM\SPROTECT\SpntShare\ServerProtect\spnt580.
  4. Perform another deployment.
If you are still unable to deploy the pattern files after performing the steps above, then collect the following files and send them to Trend Micro Technical Support:
  1. SPNT.log
    Enable the debug mode on the Normal Server:
    1. Log on to the SPNT management console.
    2. Select the Normal Server 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 and 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. Repeat steps a-d, but this time, deselect Enable debug log to disable the debug.
  2. Tmudump.txt
    The tmudump.txt file is located in the ..\Program Files\TM\SPROTECT\AC_Up-Rb.tmp\AU_Log directory.
  3. IS Update log
    1. On the IS side, select the Normal Server 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:
Troubleshoot; Deploy
Solution Id:
1054993
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.