No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

The serial number of the desktop cloud service is not valid causes to VDI installing the database automatically failed

Publication Date:  2012-11-13  |   Views:  255  |   Downloads:  0  |   Author:  c00230043  |   Document ID:  EKB1000019428


Issue Description

Related version: V100R002C01SPC100
While using the VDI automatic tool (VDesktop Install Assistance) to create the VDI infrastructure virtual machine, there appears the error prompt “installing the database abnormally” and the installation stop, click the “start” at the top left corner, but the reinstallation can’t take effect.

Alarm Information

Open the logs with the current time name in the catalog where the master installed, such as:
Then we can find the following error information:
2012-05-19 02:04:17,201 DEBUG VDSLib.InvokeRMT [5] C:\AutoInstall\Server\VDesktop6000.exe /i DBMaster-01  /language zh-CN
2012-05-19 02:04:17,845 INFO VDesktopInstaller.Flowpage [1] DBMaster-01:checking the parameters
2012-05-19 02:04:19,450 INFO VDesktopInstaller.Flowpage [1] DBMaster-01:initializing the installation file of the database...
2012-05-19 02:04:19,455 INFO VDesktopInstaller.Flowpage [1] DBMaster-01:installing the database software...
2012-05-19 02:04:33,813 INFO VDesktopInstaller.Flowpage [1] DBMaster-01:checking if the appointed “SQL SERVER” service is existing
2012-05-19 02:04:34,013 INFO VDesktopInstaller.Flowpage [1] DBMaster-01:the process of the database installation is abnormal
2012-05-19 02:04:34,014 INFO VDesktopInstaller.Flowpage [1] DBMaster-01: the process of the database installation is abnormal
2012-05-19 02:04:34,014 ERROR VDesktopInstaller.Flowpage [1] DBMaster-01:SQL SERVER appointed service isn’t existing, the process of installation is abnormal (ERRORCODE=I070067)
2012-05-19 02:04:34,014 DEBUG VDesktopInstaller.Flowpage [1] Executed failed : rmtexec.exe
2012-05-19 01:31:13,381 DEBUG VDesktopInstaller.Flowpage [1] Execute 'C:\AutoInstall\Server\VDesktop6000.exe' failed with error code '282'
2012-05-19 02:04:34,622 ERROR VDesktopInstaller.Flowpage [1] role DBMaster-01 install failed, return the error bit 282.

And there ejecting the error information as the following picture

Handling Process

Substitute the old serial number with the one of the data planning tool contained, or another valid serial number. The steps are as followed:
1. Open the configuration file in the catalog where the master installed: C:\SmartInstall\config\VDesktopConfig.xml
2. Substitute the serial number included in the <key> character segment with a valid one:
As the following table displayed:
<DBSlave-01 type="DBSlave" versionID="1" roleTagName="DBSlave-01">

Substitute the serial number included in “<Key>R649H-M7XMR-3K9M2-TPVGT-MB6W8</Key>” with a valid serial number
Notice: there are two locations needed to be substituted.
3. After have substituted, save and exit.
4. Reinstall:
Click the “” at the top left corner in the VDI assistant, then implement the reinstallation.

Root Cause

Check the detail error:
1. Open the logs with the name of the current time in the virtual machine of the database server, such as: C:\AutoInstall\server\log\ 2012-05-19.log
2. Confirm the cause of the error:
According to the time when the error happened in the above log (it is 2012-05-19 02:04:34), view the log, we understand that we can’t install successfully is caused by the serial number of the SQL Server isn’t valid. As the following displayed:
2012-05-19 02:04:34,462 Thread:[852] Priority:[INFO ] Class:VDS_management_studio.source.application.installation.DataBaseSetup Method:startCmd Line:0 result=The following error occurred:
The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging.

Therefore, according the above error information, we can conclude that this error is caused by the invalid serial number of the database.


After happening this error, check the detail error through the logs firstly, then take the corresponding measures to settle or avoid this error.