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

Create a technical support case if you need further support.

Unable to upgrade SecureCloud Key Management Server (KMS) 3.0 to 3.6

    • Updated:
    • 7 Mar 2014
    • Product/Version:
    • SecureCloud 3.0
    • Platform:
    • CentOS 5.6 32-bit
    • CentOS 5.6 64-bit
    • CentOS 5.7 32-bit
    • CentOS 5.7 64-bit
    • CentOS 5.8 32-bit
    • CentOS 5.8 64-bit
    • CentOS 6 32-bit
    • CentOS 6.1 32-bit
    • CentOS 6.1 64-bit
    • CentOS 6.2 32-bit
    • CentOS 6.2 64-bit
    • Linux - Red Hat RHEL 5.6 32-bit
    • Linux - Red Hat RHEL 5.6 64-bit
    • Linux - Red Hat RHEL 5.7 32-bit
    • Linux - Red Hat RHEL 5.7 64-bit
    • Linux - Red Hat RHEL 5.8 32-bit
    • Linux - Red Hat RHEL 5.8 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • Linux - Red Hat RHEL 6.1 32-bit
    • Linux - Red Hat RHEL 6.1 64-bit
    • Linux - Red Hat RHEL 6.2 32-bit
    • Linux - Red Hat RHEL 6.2 64-bit
    • Linux - SuSE 11
    • Ubuntu 10.04 32-bit
    • Ubuntu 10.04 64-bit
    • Ubuntu 10.1 32-bit
    • Ubuntu 10.1 64-bit
    • Ubuntu 11.04 32-bit
    • Ubuntu 11.04 64-bit
    • Ubuntu 12.04 32-bit
    • Ubuntu 12.04 64-bit
    • Windows 2003 Server R2
    • Windows 2008 Server R2
    • Windows 2012 Enterprise
    • Windows 7 Ultimate 32-bit
    • Windows 7 Ultimate 64-bit
Summary
You cannot upgrade the SecureCloud KMS from 3.0 to 3.6.
Details
Public
The issue occurs because there is a huge amount of data. During the upgrade, SecureCloud converts the data type and once there is a huge data the SQL session times out which results to upgrade failure.
To resolve the issue, extend the timeout setting:
  1. In Microsoft SQL Management Studio, go to Tools > Options > Query Execution.
  2. Change the value of Execution time-out: to “0”.
    Change the value of Execution time-out to “0”.
     
  3. Go to Tools > Options > Designers > Table and Database Designers.
  4. Set the Transaction time-out after: to 1000 seconds.
    Set the Transaction time-out after: to 1000 seconds or higher.
    You may enter a higher value depending on the SQL server performance if it needs more time.
  5. Go to Server Properties > Connections. Set the value of Remote query timeout to “0” for no timeout.
    Set the value of Remote query timeout  to "0".
    You have the option to roll back the values once SecureCloud upgrade is complete.
Premium
Internal
Rating:
Category:
Upgrade; Update
Solution Id:
1102452
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.