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>


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


Using the win2000’s AD domain of the site causes installing the ITA configuration of the Galax and DDC failed

Publication Date:  2012-11-20 Views:  84 Downloads:  0
Issue Description
The version of the cloud computing: R2C00SPC200
Build the VDESKTOP environment, after installing the ITA, we configure the information of the Galax and DDC failed, there prompts as the following:

Alarm Information
Handling Process
1. Check the IP ports of the ESC in the ITA’s Galax and DDC configuration, the domain account and the DDC’s IP are all correct.
2. According to the “” in the GPI manual, modify the tomcat’s login in domain account and password as to the ITA’s domain account and password. The problem is still on.
3. Collect the logs in the catalog “C:\ITA\logs\vDesktop\log\VDesktop\vDesktop.log” in the ITA, and then analyze them.
4. Open the “vDesktop.log” via the UE, check the “loadGalax()” and we find the Galax configuration is called normally.
2012-02-24 22:03:13.637  INFO  PROC  catalina-exec-39  1082  loadGalax():load galax config success。
5. Go on to check the “loadDDCConfig()” and we find the DDC configuration has called failed.
2012-02-24 22:03:49.872  ERROR  PROC  catalina-exec-39  1045  loadDDCConfig():load ddc config failed。
6. According to the log which recording the DDC configuration is called failed, track the erroe back to the source and we find it’s obtaining the DDC’s getSID failed:
2012-02-24 22:03:26.043  INFO  PROC  pool-1-thread-3  2767  getSIDByName():cmd /c powershell $cn='DDCWI';$adRoot='';C:/ITA/script/getSIDByCN.ps1
2012-02-24 22:03:49.872  ERROR  PROC  pool-1-thread-3  2787  getSIDByName():PowerShell:Exception.Exception has been thrown by the target of an invocation.
2012-02-24 22:03:49.872  DEBUG  PROC  pool-1-thread-3  2824  getSIDByName():[Exit].
2012-02-24 22:03:49.872  ERROR  PROC  pool-1-thread-3  1432  putDDCInfo():ddccn=DDCWI,getSID failed.
2012-02-24 22:03:49.872  DEBUG  PROC  pool-1-thread-3  1540  getDDCInfo():[leave]
2012-02-24 22:03:49.872  INFO  PROC  pool-1-thread-3  49  powershell execute result = {}
2012-02-24 22:03:49.872  ERROR  PROC  catalina-exec-39  171  updateDDCInfoTbl():ddcInfos is null.
2012-02-24 22:03:49.872  ERROR  PROC  catalina-exec-39  1281  initDgPoolInfo(): Fail because updateDDCInfoTbl() return false
2012-02-24 22:03:49.872  ERROR  PROC  catalina-exec-39  1045  loadDDCConfig():load ddc config failed
7. In the R2C00 version, configure the DDC information through ITA, each time to start the ITA, it will obtain the DDC’s SID according to the “C:/ITA/script/getSIDByCN.ps1”, and writes into the DB. But currently the problem is that there can’t acquire the SID in the AD domain via the script.
8. The ITA’s “getSIDByCN.ps1” script can acquire the SID, but it only supports the AD of the win2003 and win2008, we guess there isn’t the win2003 domain in the site.
9. Ask the site and the customer to confirm it, we get it is just the win2000 single domain.
10. The solution of the R2C00 version currently just supports the win2003, and the Microsoft doesn’t maintain the win2000, to settle the problem thoroughly, it requires the site use the win2003 AD domain, or rebuild a new win2003 AD domain.
11. A measure to avoid this problem is:
11.1 Make a spare of the “C:/ITA/script/getSIDByCN.ps1” file in the ITA.
11.2 Use the note to open the “C:/ITA/script/getSIDByCN.ps1” in the ITA: modify the “echo $strSID.Value” in the 31st column as to any SID value, such as: echo "SID123.
11.3 Delete the columns from the 5th to the 30th of the “C:/ITA/script/getSIDByCN.ps1” in the ITA.
11.4 The content of “getSIDByCN.ps1” after modifying is:
#$cn = "hostname"
#$domain = ""

echo "SID123"
trap [Exception]
  if ($printFlag -ne $true)
    echo  ("PowerShell:"+$_.Exception.Message)
11.5 Configure the Galax and DDC configuration through the ITA again, and then the configurations are successful.
12. After building the whole VDESKTOP and assigning the virtual machine, test the corresponding services and all of them are normal.

Root Cause
1. The information of the ITA’s DDC configuration option is incorrect.
2. The ITA’s tomcat account is incorrect.
3. It can’t support the AD domain.

1. If use the site’s AD domain while building the VDESKTOP environment, we need to known whether the AD domain is supported by the corresponding version.
2. The avoiding measure in the win2000’s AD currently just supports with the AD single domain but not for the multi-domain.
3. IF has taken the avoid measure to modify the “getSIDByCN.ps1” file, we should record it and deliver it to the site. While rebuilding the ITA, the modified “getSIDByCN.ps1” file is required.