vapi std errors: invalid element type
invalid_element_typeerror indicates that the server was unable to fulfil the request because an element of a specific type cannot be a member of particular group.
This error could be reported, for example, if an attempt is made to put an element into the wrong type of container.
- Attempt to put a virtual machine into a folder that can only contain hosts.
- Attempt to attach a SCSI virtual disk to an IDE port.
- A parameter has a value that is not of the expected type. The vapi.std.errors.invalid_argument error would be used instead.
<ns0:Error xmlns:ns0="http://vmware.com/vapi/rest/base" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
|messages||localizable_message||Stack of one or more localizable messages for human error consumers.
The message at the top of the stack (first in the list) describes the error from the perspective of the operation the client invoked. Each subsequent message in the stack describes the "cause" of the prior message.
|data||object||Data to facilitate clients responding to the operation reporting a standard error to indicating that it was unable to complete successfully.
Operations may provide data that clients can use when responding to errors. Since the data that clients need may be specific to the context of the operation reporting the error, different operations that report the same error may provide different data in the error. The documentation for each each operation will describe what, if any, data it provides for each error it reports. The vapi.std.errors.argument_locations, vapi.std.errors.file_locations, and vapi.std.errors.transient_indication structures are intended as possible values for this field. vapi.std.dynamic_ID may also be useful as a value for this field (although that is not its primary purpose). Some services may provide their own specific structures for use as the value of this field when reporting errors from their operations.Optional. Some operations will not set this field when reporting errors.