appcert (WACK) blocked for some reason
As part of my build I'm running a powershell script that runs WACK (Windows Application Certification Toolkit). Then, this script parses the resulting report and let's the build fail in case there is a certification error. However, all of the WACK tests fail with the same message:
The test was blocked from execution. Please try re-running
the validation. If the test execution remains blocked then please
contact support.
I'm running exactly the same script on my local dev machine. Here, most of the tests PASS and only some tests FAIL.
So my actual question is: Do you have any idea of what might block this tool on your image (Visual Studio 2015)? I already connected to the build machine via RDP and tried to run WACK with elevated rights, without success. Running WACK directly via command line without the script didn't work either.
I attached the script that calls appcert.
- runAppcert.ps1 2.33 KB
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Stephan on 12 Dec, 2015 08:16 AM
One additional comment: The tests on my local dev machine fail with some real certification issues. So I'm not getting the same error message for any of the tests.
Support Staff 2 Posted by Feodor Fitsner on 12 Dec, 2015 10:23 PM
Is it possible that this tool works under desktop version of Windows only (e.g. Windows 10)?
On Azure there are VM images with Visual Studio 2015 for both Windows 10 and Windows Server 2012 R2. You can create two VMs and check that assumption.
3 Posted by Stephan on 18 Dec, 2015 10:10 AM
I opened a support ticket for that and got this as an answer:
"For the test execution blocked issue, the WACK team believes it is a bad installo. They recommend a re-install or repair of Visual Studio / SDKs"
I also found a post at MSDN forums where the user reinstalled the SDK and it worked then.
Following your advice I created a VM image on Azure with Visual Studio 2015 on Windows Server 2012 R2 without the SDK installed. I then installed the SDK, ran my powershell script and everything worked fine. All tests passed and I didn't receive this error message.
I then used RDP to connect to the Appveyor build worker, downloaded the Windows 10 SDK (build 10586) and installed this one over the existing. Nothing changed. Still got the same error message. I then tried a repair install. This time the installer asked me to restart Windows. As I can't do this for the Appveyor VM I'm stuck here.
Therefore my request: Could you please do a (clean) reinstall or repair of the Windows 10 SDK? I will give it another try then.
Support Staff 4 Posted by Feodor Fitsner on 18 Dec, 2015 05:59 PM
You should be able to restart build worker and then connect it with the same IP/credentials without any issues. Give it another try.
You're currently running builds on Pro environment. I'm wondering if you can try running your tests on Google Compute Engine environment and see if they do work there. Those build workers have re-built from scratch OS images. To run on GCE select
Visual Studio 2015 RCOS image (or set it in appveyor.yml) - this still will be VS 2015 RTM, but run on GCE.Also, would be nice if you can do a very simple app with few tests in a public repo, so I can play with it too.
Support Staff 5 Posted by Feodor Fitsner on 18 Dec, 2015 06:48 PM
Btw, I've checked appcert.exe tool with decompiler. While running tests it generates an XML report somewhere. You may try checking that XML for any extended messages that might help to troubleshoot.
Support Staff 6 Posted by Feodor Fitsner on 22 Dec, 2015 12:48 AM
We've repaired Windows 10 SDK (build 10586) on all build workers. Let me know how that worked.
7 Posted by graham chow on 02 Feb, 2016 07:12 PM
Hi Feodor, I had exactly the same issue - most tests giving me back "The test was blocked from execution. Please try re-running the validation. If the test execution remains blocked then please contact support.".
I re-installed visual studio, the sdk, repaired etc and nothing worked.
However good news. I uninstalled the windows driver kit (Windows Installer removed the product. Product Name: Windows Driver Kit. Product Version: 10.0.26639. Product Language: 1033. Manufacturer: Microsoft Corporation. Removal success or error status: 0.) and it started working again.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:03 AM.