Troubleshooting Windows HCK Setup
This article contains information to help you to troubleshoot Windows Hardware Certification Kit (Windows HCK) installation and setup issues.
In this topic:
Cannot browse \\<controller-name>\HCKInstall\ on Studio or Client computer
Cannot change or repair Windows HCK by using Control Panel
Cannot install HCK.AddLoggerEntries: Access is denied
Cannot install the Windows HCK Client
Cannot install or remove the Windows HCK Controller
Client installation fails with error "This app can't run on your PC”
Error: Failed to connect to database. Failed to connect to OM.
Error: SQL client components are required for this operation
Troubleshooting Windows HCK Client installation
Cannot browse \\<controller-name>\HCKInstall\ on Studio or Client computer
If you cannot browse to the HCKInstall folder from the Windows HCK Studio or Client, review the setup and configuration information in the Step 1: Install Controller and Studio on the test server topic.
Cannot change or repair Windows HCK by using Control Panel
If you try to change or repair the Windows HCK by using Control Panel, you receive an error message that the repair failed. To change or repair your Windows HCK installation, use Control Panel to uninstall Windows Hardware Certification Kit, and then reinstall the Windows HCK See Step 1: Install Controller and Studio on the test server.
Cannot install HCK.AddLoggerEntries: Access is denied
In rare cases, Windows HCK setup might fail just before it completes. If you look at the Windows HCK Controller log, CA AddLoggerEntries appears with an Access is denied error. If this happens, run HCKSetup.exe again to see if the Windows HCK installs successfully. If setup fails again, see Windows HCK Support for instructions about how to contact Support. Include the *HCKControllerx86_en_us.log file from the %temp%\hck folder.
Cannot install the Windows HCK Client
If you cannot install the Windows HCK Client, review the installation info in the Step 2: Install Client on the test computer(s) topic and make sure that you follow these instructions.
If you still cannot install the Windows HCK Client, locate these Client log files in the %TEMP% folder. See Windows HCK Support for information about how to contact Support, and share the following client log files with Microsoft Support:
WLKInstall.log
Windows Hardware Certification Kit Client_Install.log
Windows Driver Testing Framework (WDTF) Runtime Libraries_Install.log
Application Verifier x64 External Package_Install.log
WPTx64_Install.log
Cannot install or remove the Windows HCK Controller
If you encounter issues installing the Windows HCK Controller, confirm the following:
The operating system uses the English language (en-us) version of Windows Server 2008 R2 x64 or Windows Server® 2012 and is not running as a domain controller.
The system language is set to US English. To do this, click Region and Language in Control Panel, click the Administrative tab, click Change system locale, and then select English (United States).
If you cannot install or remove the Windows HCK Controller, review the controller log file that is located in the %temp%\HCK folder.
.gif)
To review the Windows HCK Controller log file
At a command prompt, type %HomeDrive%, and then press Enter.
Type cd %temp%\HCK, and then press Enter.
Type dir *HCKControllerx86_en_us.log, and then press Enter.
Open the log file in a text editor such as Notepad.
Note
If more than one file ends in HCKControllerx86_en_us.log, open the newest file. To open the log file in Notepad from the command line, type Notepad, the full file name, and then press Enter.
Search for return value 3 to see which action failed. Error information is located a few lines above the string return value 3.
MSI (s) (F4:74) [18:58:28:187]: Executing op: ActionStart(Name=CreateStandaloneEnterprise,,) MSI (s) (F4:74) [18:58:28:187]: Executing op: CustomActionSchedule(Action=CreateStandaloneEnterprise,ActionType=17409,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files (x86)\Windows Kits\8.0\Hardware Certification Kit\Controller\WTTStandaloneEnterpriseSetup.exe" "TEST-SERVER" "DTMJobs" "C:\StandaloneEnterprise") MSI (s) (F4:48) [18:58:28:187]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI9E59.tmp, Entrypoint: CAQuietExec CAQuietExec: Standalone Enterprise setup started by user TEST-SERVER\Administrator 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 (x86)\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\DTMJobs.mdf' because it already exists. Change the file path or the file name, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related 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 (x86)\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\DTMJobs.mdf' because it already exists. Change the file path or the file name, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related 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 CustomAction CreateStandaloneEnterprise returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (F4:74) [18:58:30:137]: User policy value 'DisableRollback' is 0 MSI (s) (F4:74) [18:58:30:137]: Machine policy value 'DisableRollback' is 0 Action ended 18:58:30: InstallFinalize. Return value 3
If the *HCKControllerx86_en_us.log file includes Error while creating new data store 'Jobs', complete these steps:
CAQuietExec: Error Message : Cannot create file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\DTMJobs.mdf' because it already exists. Change the file path or the file name, and retry the operation.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
****
Delete these files from the C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA folder:
DTMJobs.mdf
DTMJobs_Log.ldf
Reinstall the Windows HCK Controller. For info on how to do this, see Step 1: Install Controller and Studio on the test server
Client installation fails with error "This app can't run on your PC”
The system returns an error “This app can’t run on your PC” if you try to install Windows HCK Client software on a computer that is running Windows 8 RT. This is not a supported platform; however, you can install Windows HCK Client software on a computer that is running Windows RT 8.1.
Error: Failed to connect to database. Failed to connect to OM.
If you get an error message that states Failed to connect to database. Failed to connect to OM when you start Windows HCK Studio, make sure that your user account is added to the Windows HCK Controller. For instructions on how to add your user account to the Windows HCK Controller, see “Configure additional user accounts” in Install a remote HCK Studio.
Error: SQL client components are required for this operation
This error occurs when you attempt to install the full version of HCK (HCK Controller + Studio option), after you first downloaded the HCK product on a separate machine that already has the HCK Studio only option installed.
Workaround: Uninstall the HCK Studio Only version and try downloading and reinstalling the full HCK version again.
Related topics
Troubleshooting the Windows HCK Environment