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

- Updated:
- 24 Nov 2016
- 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

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:

In Microsoft SQL Management Studio, go to Tools > Options > Query Execution.
Change the value of Execution time-out: to “0”.
Go to Tools > Options > Designers > Table and Database Designers.
Set the Transaction time-out after: to 1000 seconds.

You may enter a higher value depending on the SQL server performance if it needs more time.
Go to Server Properties > Connections. Set the value of Remote query timeout to “0” for no timeout.

You have the option to roll back the values once SecureCloud upgrade is complete.