App Layering 4.1 - Failed to Create Layer, 'A specified parameter was not correct. url'
Article ID: CTX223690
Updated On:
Description
When attempting to create a layer, the error below is displayed:
Failed to execute the script: vCenter returned an unexpected failure => Fault Code: 'ServerFaultCode' FaultMessage: 'A specified parameter was not correct. url' Details: {"attributes":{"xsi:type":"InvalidArgument"},"invalidProperty":"url"}
Resolution
To solve this, you must upgrade ESXi to 5.5. ESXi 5.1 is not supported. Or, if you have multiple ESXi hosts in your system, some of which are running 5.5, specify a 5.5 host in the Connector configuration.
The "AcquireGenericServiceTicket failed: A specified parameter was not correct. .url'" error is a known issue when there is a version mismatch between vCenter 5.5 and ESXi 5.1. The ELM is sending commands to vCenter 5.5, however, when we are redirected to the ESXi for the file upload, it does not understand the 5.5 commands we are sending. When creating a layer or layer version, much of the communication goes through vCenter. App Layering requires vSphere 5.5, so as long as vCenter is 5.5, that much works. However, when it's time to actually upload the VMDK for the layer, a "service ticket" is granted by vCenter to talk directly to an ESXi host. You get this error if your ESXi host is not also at version 5.5 or above. If, for instance, your ESXi host is still 5.1, App Layering will generate this failure because the commands we send are not implemented in 5.1, only 5.5 and above.
Problem Cause
You can see the specific failure in the vSphere Connector log in unidesk-vsphere-connector.log.json.log (in a log export), like this:[2017-05-05T09:22:10.708Z] INFO: UploadVmdk/26379 on localhost.localdomain: Upload execute parameters (dsPath=Some_Layer-2017-05-05_09-22-07.391, reqNum=633) vmdk: /mnt/repository/Unidesk/Packaging Disks/Some_LayerBoot.vmdk [2017-05-05T09:22:10.709Z] INFO: UploadVmdk/26379 on localhost.localdomain: Uploading sparse: /mnt/repository/Unidesk/Packaging Disks/Some_LayerBoot.vmdk => Some_Layer-2017-05-05_09-22-07.391/Some_LayerBoot-tmp.vmdk (reqNum=633) [2017-05-05T09:22:10.710Z] INFO: UploadToDatastore/26379 on localhost.localdomain: Uploading Some_LayerBoot.vmdk (23472832512 bytes) to https://esx_host1/folder%2FSome_Layer-2017-05-05_09-22-07.391%2FSome_LayerBoot-tmp.vmdk?dcPath=ha-datacenter&dsName=dataStore (reqNum=633) [2017-05-05T09:22:10.747Z] ERROR: VsphereClient/26379 on localhost.localdomain: (reqNum=633) SOAP command 'AcquireGenericServiceTicket' failed: [ServerFaultCode] A specified parameter was not correct. url [2017-05-05T09:22:10.749Z] ERROR: UploadToDatastore/26379 on localhost.localdomain: (reqNum=633) Failure occurred while uploading the file: vCenter returned an unexpected failure => Fault Code: 'ServerFaultCode' FaultMessage: 'A specified parameter was not correct. url' Details: {"attributes":{"xsi:type":"InvalidArgument"},"invalidProperty":"url"}
The "AcquireGenericServiceTicket failed: A specified parameter was not correct. .url'" error is a known issue when there is a version mismatch between vCenter 5.5 and ESXi 5.1. The ELM is sending commands to vCenter 5.5, however, when we are redirected to the ESXi for the file upload, it does not understand the 5.5 commands we are sending. When creating a layer or layer version, much of the communication goes through vCenter. App Layering requires vSphere 5.5, so as long as vCenter is 5.5, that much works. However, when it's time to actually upload the VMDK for the layer, a "service ticket" is granted by vCenter to talk directly to an ESXi host. You get this error if your ESXi host is not also at version 5.5 or above. If, for instance, your ESXi host is still 5.1, App Layering will generate this failure because the commands we send are not implemented in 5.1, only 5.5 and above.
Additional Information
https://www.unidesk.com/support/learn/4.0.8/set_up/get_started_deploy_release_notes_co4/welcome_platform_support_co4
Was this article helpful?
Yes
No
Powered by
