| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diagnose artifact failures in an Azure DevTest Labs virtual machine | Microsoft Docs |
Learn how to troubleshoot artifact failures in Azure DevTest Labs. |
devtest-lab,virtual-machines |
na |
tomarcher |
douge |
115e0086-3293-4adf-8738-9f639f31f918 |
devtest-lab |
na |
na |
na |
article |
08/18/2017 |
tarcher |
After you have created an artifact, you can check to see whether it succeeded or failed. Artifact logs in Azure DevTest Labs provide information that you can use to diagnose an artifact failure. You have a couple of options for viewing the artifact log information for a Windows VM:
- In the Azure portal
- In the VM
Note
To ensure that failures are correctly identified and explained, it's important that the artifact has the proper structure. For information about how to correctly construct an artifact, see Create custom artifacts. To see an example of a properly structured artifact, check out the Test parameter types artifact.
-
In the Azure portal, in your list of resources, select your lab.
-
Choose the Windows VM that includes the artifact that you want to investigate.
-
In the left panel, under GENERAL, select Artifacts. A list of artifacts associated with that VM appears. The name of the artifact and the artifact status are indicated.
-
Select an artifact that shows a Failed status. The artifact opens. An extension message that includes details about the failure of the artifact is displayed.
-
Sign in to the VM that contains the artifact you want to diagnose.
-
Go to C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\1.9\Status, where 1.9 is the Azure Custom Script Extension version number.
-
Open the status file.
[!INCLUDE devtest-lab-try-it-out]
- Learn how to add a Git repository to a lab.