none
WLK1.5无法安装公司- 哪位高手指点下可能是什么问题? RRS feed

  • 質問

  • 我们正在从1.4升级到1.5版.在升级前1.4版成功删除.
    WLK1.5版本成功下载,可是安装时所有COMPONENTS都是NOT INSTALLABLE状态, 会是什么原因?
    DTM CONTROLLER 是WINDOWS SERVER 2003.
    看了下DTM项不可安装的详细信息是: INCOMPATIBILITY INSTALLED: MICROSOFT WTT INSTALLATION (OR WLK COMPONENT LEVERAGES CORE WTT FEATURES

    万分感谢!
    2010年2月23日 22:02

回答

  • 看看安装日志WLK-DTMControllerInstall.log. 。这个日志在系统的临时文件夹里。

    Troubleshooting DTM Controller Issues

    Transaction log grows too large

    Details: It is possible that the SQL transaction log can grow too large to be usable. This is because the transaction log is designed to continue to grow in size as long as there is available disk space to contain it.

    Solution: To solve this problem, you must reduce the size of the transaction log. For information about how to manually reduce the size of the transaction log, see  DTM Database Options and Maintenance Best Practices on WHDC.

     

    Sqlservr.exe pegging CPU: increased time taken to process tests

    Details: If you have more than one or two active logo submissions running at one time, it might take longer than expected for tests to get scheduled and run as well as CPU of the DTM Controller getting pegged by Sqlservr.exe.

    Solution: You might need to upgrade the hardware you are running DTM Controller on. If you typically run several submissions at the same time, upgrade your DTM Controller system to a minimum of quad processor with at least 2Ghz and 4G RAM.

     

    Unsupported Scenarios

    The following scenarios are not supported by the DTM Controller. If you have one of the following scenarios set up on your DTM Controller, you will encounter problems. Use the suggested workaround to resolve the issue.

    • If you change the name of the computer after you install DTM Controller.
      Workaround: Uninstall and reinstall DTM Controller.
    • If you installed DTM Controller while the computer was connected to a DOMAIN, you might have problems if you remove the computer from the domain and make the computer a member of a WORKGROUP.
      Symptom: You receive the following error message: SQL server does not exist or access denied.
      Workaround: Uninstall and reinstall DTM Controller.

     

     

    Troubleshooting General Issues (including Kitsetup)

    “Microsoft Windows Logo Kit” is left behind in “Add or Remove Programs” after uninstall

    Details: You might notice that after you uninstall WLK features from your system by using Kitsetup that Microsoft Windows Logo Kit is still listed in Add or Remove Programs.

    This can be caused by a momentary loss of communication between the computer and Kitsetup.exe program (for example, if you removed the WLK DVD before the WLK was completely uninstalled, or if the installation location was from the network or a connection was lost).

    Solution: Use Kitsetup.exe to install DTM Controller and then to uninstall DTM Controller. Completing this sequence allows Add or Remove Programs to be clear of Microsoft Windows Logo Kit. Open Add or Remove Programs and next to Microsoft Windows Logo Kit click Change. When Kitsetup.exe opens, click DTM Controller, and then click Apply. After DTM Controller is installed, select to remove it by un-selecting DTM Controller, then click Apply.

     

    Unable to browse \\<controller-name>\DTMInstall\ from Studio or Client machine

    Details: If you are unable to browse the DTMInstall directory from the DTM Studio or DTM Client, review the information in the Install.htm.

    You might also need to allow an Internet Connection Firewall Exception for File and Printer Sharing. You allow an exception by placing a check-mark next to the item in the Windows Firewall Exceptions tab.

     

    Installation or Uninstallation fails (example using DTM Controller)

    Details: If you are trying to install or uninstall DTM Controller and you get a failure, you can check the setup logs to find information that might help you to determine the reason for the failure. You can find the setup logs in the %temp% folder.

    To navigate to the %temp% folder and read the setup logs:

    1. Click Start, and then click Run.
    2. Type cmd.exe, and press Enter.
    3. Type %HomeDrive%, and press Enter.
    4. Type cd %temp%, and press Enter.
    5. Type dir *.log, and press Enter.
      In this list, you should see a file named WLK-DTMControllerInstall.log.
    6. To review this log file, type notepad WLK-DTMControllerInstall.log and press Enter.
    7. Type dir *.log, and press Enter.
      In this list, you should see a file named WLK-DTMControllerUninstall.log.
    8. To review this log file, type notepad WLK-DTMControllerUninstall.log and press Enter.
    9. Search for return value 3 to discover what custom action failed. The specific error will be located a few lines above the returned value.

       

    If you get the error message Setup Ended Premature and you look in the WLK-DTMControllerInstall.log for return value 3 and notice the following message, follow the subsequent steps to recover from this problem.

    ERROR MESSAGE:
    MSI (s) (7C:0C) [16:43:52:429]: Executing op: CustomActionSchedule(Action=CreateStandaloneEnterprise,ActionType=17409,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files\Microsoft Driver Test Manager\Controller\WTTStandaloneEnterpriseSetup.exe" "[YOUR_COMPUTER_NAME]" "DTMJobs" "C:\StandaloneEnterprise")
    MSI (s) (7C:B4) [16:43:52:429]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI47B.tmp, Entrypoint: CAQuietExec
    CAQuietExec:  Standalone Enterprise setup started by user [DOMAIN]\[USERACCOUNT]
    CAQuietExec:  Error::
    ************************************************************ERROR REPORT (Exception levels including inner exceptions. Level 0 denotes outermost exception)
    CAQuietExec:  
    CAQuietExec:  ------------START OF ERROR REPORT------------
    CAQuietExec:  
    CAQuietExec:  Level            : 0
    CAQuietExec:  Error Message    : Error while creating new data store  'DTMJobs' .
    CAQuietExec:  Source           : Void CreateEnterprise(Microsoft.DistributedAutomation.DSLink, Microsoft.DistributedAutomation.ServiceCollection, Boolean)
    CAQuietExec:  Inner Exception  : System.Runtime.InteropServices.COMException (0x80041432): Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DTMJobs_Data.mdf' because it already exists.
    CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.
    CAQuietExec:     at Interop.SQLDMO.Databases.Add(_Database Object)
    CAQuietExec:     at Microsoft.DistributedAutomation.SqlDataStore.SqlDataStoreSetup.CreateDeploymentDataStore(ServiceCollection serviceList, DSLink newDSLink)
    CAQuietExec:  Call Stack       :    at Microsoft.DistributedAutomation.SqlDataStore.SqlDataStoreSetup.CreateEnterprise(DSLink identityDSLink, ServiceCollection serviceList, Boolean standaloneInstall)
    CAQuietExec:     at Microsoft.DistributedAutomation.EnterpriseSetup.EnterpriseSetupHelper.CreateEnterprise(EnterpriseConfiguration enterpriseConfig, DSLink dsLink, String setupFilePath, Boolean standaloneInstall)
    CAQuietExec:     at Microsoft.DistributedAutomation.EnterpriseSetup.Tools.CMain.Main(String args)
    CAQuietExec:  Trace            : 
    CAQuietExec:  
    CAQuietExec:  Level            : 1
    CAQuietExec:  Error Message    : Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DTMJobs_Data.mdf' because it already exists.
    CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.
    CAQuietExec:  Source           : Void Add(Interop.SQLDMO._Database)
    CAQuietExec:  Inner Exception  : 
    CAQuietExec:  
    CAQuietExec:  --------------END OF ERROR REPORT------------************************************************************
    CAQuietExec:  Error 0x80070001: Command line returned an error.
    CAQuietExec:  Error 0x80070001: CAQuietExec Failed
    Action ended 16:44:39: InstallFinalize. Return value 3.

    1. Delete the following two files from C:\Program Files\Microsoft SQL Server\MSSQL\Data folder on the computer:
      DTMJobs_Data.mdf
      DTMJobs_Log.ldf
    2. Install the DTM Controller component again.

    http://www.microsoft.com/china/whdc http://ctcwhql.spaces.live.com/blog/
    2010年2月25日 5:42
    モデレータ
  • 借宝地一用~

    请教下,win7上的安装也是用WLK,vista用的是WDK.可以这样理解吗?


    WLK和WDK是两个东西。做测试都用WLK,做开发都用WDK。


    http://www.microsoft.com/china/whdc http://ctcwhql.spaces.live.com/blog/
    2010年3月25日 7:51
    モデレータ

すべての返信

  • 看看安装日志WLK-DTMControllerInstall.log. 。这个日志在系统的临时文件夹里。

    Troubleshooting DTM Controller Issues

    Transaction log grows too large

    Details: It is possible that the SQL transaction log can grow too large to be usable. This is because the transaction log is designed to continue to grow in size as long as there is available disk space to contain it.

    Solution: To solve this problem, you must reduce the size of the transaction log. For information about how to manually reduce the size of the transaction log, see  DTM Database Options and Maintenance Best Practices on WHDC.

     

    Sqlservr.exe pegging CPU: increased time taken to process tests

    Details: If you have more than one or two active logo submissions running at one time, it might take longer than expected for tests to get scheduled and run as well as CPU of the DTM Controller getting pegged by Sqlservr.exe.

    Solution: You might need to upgrade the hardware you are running DTM Controller on. If you typically run several submissions at the same time, upgrade your DTM Controller system to a minimum of quad processor with at least 2Ghz and 4G RAM.

     

    Unsupported Scenarios

    The following scenarios are not supported by the DTM Controller. If you have one of the following scenarios set up on your DTM Controller, you will encounter problems. Use the suggested workaround to resolve the issue.

    • If you change the name of the computer after you install DTM Controller.
      Workaround: Uninstall and reinstall DTM Controller.
    • If you installed DTM Controller while the computer was connected to a DOMAIN, you might have problems if you remove the computer from the domain and make the computer a member of a WORKGROUP.
      Symptom: You receive the following error message: SQL server does not exist or access denied.
      Workaround: Uninstall and reinstall DTM Controller.

     

     

    Troubleshooting General Issues (including Kitsetup)

    “Microsoft Windows Logo Kit” is left behind in “Add or Remove Programs” after uninstall

    Details: You might notice that after you uninstall WLK features from your system by using Kitsetup that Microsoft Windows Logo Kit is still listed in Add or Remove Programs.

    This can be caused by a momentary loss of communication between the computer and Kitsetup.exe program (for example, if you removed the WLK DVD before the WLK was completely uninstalled, or if the installation location was from the network or a connection was lost).

    Solution: Use Kitsetup.exe to install DTM Controller and then to uninstall DTM Controller. Completing this sequence allows Add or Remove Programs to be clear of Microsoft Windows Logo Kit. Open Add or Remove Programs and next to Microsoft Windows Logo Kit click Change. When Kitsetup.exe opens, click DTM Controller, and then click Apply. After DTM Controller is installed, select to remove it by un-selecting DTM Controller, then click Apply.

     

    Unable to browse \\<controller-name>\DTMInstall\ from Studio or Client machine

    Details: If you are unable to browse the DTMInstall directory from the DTM Studio or DTM Client, review the information in the Install.htm.

    You might also need to allow an Internet Connection Firewall Exception for File and Printer Sharing. You allow an exception by placing a check-mark next to the item in the Windows Firewall Exceptions tab.

     

    Installation or Uninstallation fails (example using DTM Controller)

    Details: If you are trying to install or uninstall DTM Controller and you get a failure, you can check the setup logs to find information that might help you to determine the reason for the failure. You can find the setup logs in the %temp% folder.

    To navigate to the %temp% folder and read the setup logs:

    1. Click Start, and then click Run.
    2. Type cmd.exe, and press Enter.
    3. Type %HomeDrive%, and press Enter.
    4. Type cd %temp%, and press Enter.
    5. Type dir *.log, and press Enter.
      In this list, you should see a file named WLK-DTMControllerInstall.log.
    6. To review this log file, type notepad WLK-DTMControllerInstall.log and press Enter.
    7. Type dir *.log, and press Enter.
      In this list, you should see a file named WLK-DTMControllerUninstall.log.
    8. To review this log file, type notepad WLK-DTMControllerUninstall.log and press Enter.
    9. Search for return value 3 to discover what custom action failed. The specific error will be located a few lines above the returned value.

       

    If you get the error message Setup Ended Premature and you look in the WLK-DTMControllerInstall.log for return value 3 and notice the following message, follow the subsequent steps to recover from this problem.

    ERROR MESSAGE:
    MSI (s) (7C:0C) [16:43:52:429]: Executing op: CustomActionSchedule(Action=CreateStandaloneEnterprise,ActionType=17409,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files\Microsoft Driver Test Manager\Controller\WTTStandaloneEnterpriseSetup.exe" "[YOUR_COMPUTER_NAME]" "DTMJobs" "C:\StandaloneEnterprise")
    MSI (s) (7C:B4) [16:43:52:429]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI47B.tmp, Entrypoint: CAQuietExec
    CAQuietExec:  Standalone Enterprise setup started by user [DOMAIN]\[USERACCOUNT]
    CAQuietExec:  Error::
    ************************************************************ERROR REPORT (Exception levels including inner exceptions. Level 0 denotes outermost exception)
    CAQuietExec:  
    CAQuietExec:  ------------START OF ERROR REPORT------------
    CAQuietExec:  
    CAQuietExec:  Level            : 0
    CAQuietExec:  Error Message    : Error while creating new data store  'DTMJobs' .
    CAQuietExec:  Source           : Void CreateEnterprise(Microsoft.DistributedAutomation.DSLink, Microsoft.DistributedAutomation.ServiceCollection, Boolean)
    CAQuietExec:  Inner Exception  : System.Runtime.InteropServices.COMException (0x80041432): Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DTMJobs_Data.mdf' because it already exists.
    CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.
    CAQuietExec:     at Interop.SQLDMO.Databases.Add(_Database Object)
    CAQuietExec:     at Microsoft.DistributedAutomation.SqlDataStore.SqlDataStoreSetup.CreateDeploymentDataStore(ServiceCollection serviceList, DSLink newDSLink)
    CAQuietExec:  Call Stack       :    at Microsoft.DistributedAutomation.SqlDataStore.SqlDataStoreSetup.CreateEnterprise(DSLink identityDSLink, ServiceCollection serviceList, Boolean standaloneInstall)
    CAQuietExec:     at Microsoft.DistributedAutomation.EnterpriseSetup.EnterpriseSetupHelper.CreateEnterprise(EnterpriseConfiguration enterpriseConfig, DSLink dsLink, String setupFilePath, Boolean standaloneInstall)
    CAQuietExec:     at Microsoft.DistributedAutomation.EnterpriseSetup.Tools.CMain.Main(String args)
    CAQuietExec:  Trace            : 
    CAQuietExec:  
    CAQuietExec:  Level            : 1
    CAQuietExec:  Error Message    : Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\DTMJobs_Data.mdf' because it already exists.
    CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.
    CAQuietExec:  Source           : Void Add(Interop.SQLDMO._Database)
    CAQuietExec:  Inner Exception  : 
    CAQuietExec:  
    CAQuietExec:  --------------END OF ERROR REPORT------------************************************************************
    CAQuietExec:  Error 0x80070001: Command line returned an error.
    CAQuietExec:  Error 0x80070001: CAQuietExec Failed
    Action ended 16:44:39: InstallFinalize. Return value 3.

    1. Delete the following two files from C:\Program Files\Microsoft SQL Server\MSSQL\Data folder on the computer:
      DTMJobs_Data.mdf
      DTMJobs_Log.ldf
    2. Install the DTM Controller component again.

    http://www.microsoft.com/china/whdc http://ctcwhql.spaces.live.com/blog/
    2010年2月25日 5:42
    モデレータ
  • 谢谢大侠回复.
    我去看了那个WLK-DTMControllerInstall.log 文件, 很长, 看不懂啊. 搜索RETURN VALUE 3, 一个也没有.换成RETURN VALUE 0, 搜出来好几个.日志太长了,无法贴在这里.请问还有什么别的方式可以发给您帮我看一下?再次感谢! 
    2010年2月25日 18:26
  • 借宝地一用~

    请教下,win7上的安装也是用WLK,vista用的是WDK.可以这样理解吗?

    2010年3月23日 14:19
  • 借宝地一用~

    请教下,win7上的安装也是用WLK,vista用的是WDK.可以这样理解吗?


    WLK和WDK是两个东西。做测试都用WLK,做开发都用WDK。


    http://www.microsoft.com/china/whdc http://ctcwhql.spaces.live.com/blog/
    2010年3月25日 7:51
    モデレータ