Error message: Error creating VM. Operation 'CreateVM CustomizationOp' failed. Error executing customization script.. Error message: Set-NetworkAdapter The network "Name of the NetworkAdapter" doesn't exist on the host. . Error Code: -1

Root Cause:

The value for the Network may be incorporated with a wrong value. For example, you may provided Network Adapter which is not listed/available in VCenter.  

Resolution:

Navigate to 

WAP Admin Portal --> VConnect--> Connections--> Choose a Connection for the list--> Templates--> Choose a Template from the list --> Provide the appropriate value (available in VCenter) for the parameter 'NetworkName'

• Related Articles

• Error creating VM. Operation 'CreateVM DeployFromTemplateOp' failed. Exception: No space available in datastore 'Name of the Datastore'. Free space required: XX GB

  Root Cause: By default, VConnect would take certain amount (say 100 GB) of space for creating a VM. To change this, search for the value of 'IsSelectDataStoreUsingRealFreeSpace' in the 'AppSettings' Table,  it would be set as 'True' (by default), ...

• Exception: Attempted to divide by zero

  Error Details: “Failed due to non-retryable error. Error message: Error creating VM. Operation ‘CreateVM FinishCreateVMOp’ failed. Exception: Attempted to divide by zero.” Step 1: Run the SQL query to get the ComputeInstance have value as 0 for ...

• Creating & Uploading a new Pricing Profile

  Follow the steps to upload a new Pricing Profile: 1. Download the Azure Stack Meters.xlsx file 2. Fill the sheet with required values (to be filled by Client) 3. Ensure the file should have Sheet1 only. Remove the sheet 2, sheet 3 etc., 4. Save the ...

• POC Deployment - List of Items to be checked for proper deployment

  When we are deploying for the Customers as a fresh instillation, there are a few items that we may need to cross check before proceeding further. Below i have mentioned some of the items in the flow. 1. Making sure that all the installers are ...

• Object not found in vSphere

  The Unique ID for the VM may got differ between VMRuntime & VMConfigs Table which would not allow to perform the Power Options of a VM. To resolve this, update the value of UniqueId of VM in VMRuntime & VMConfigs table. 1. Check VM ID in PowerShell ...