Error "One or more errors occurred" appears randomly during PowerCLI command execution.
search cancel

Error "One or more errors occurred" appears randomly during PowerCLI command execution.

book

Article ID: 402922

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When running powercli script to deploy the VM and apply configurations to the VM fails with below error:
  • However, on vCenter, we see a VM getting deployed successfully and the configurations are applied as well.
  • If we disconnect and reconnect to the vCenter using Connect-VIServer, the same script runs successfully without error.
  • In the /var/log.vmware/vapi/endpoint/endpoint.log:

YYYY-MM-DDTHH:MM:SS.175Z | INFO  | sso6                      | MasterSessionManagerImpl       | Created session [email protected] (internal id ######-####-####-####-######, token 469e1...)
YYYY-MM-DDTHH:MM:SS.175Z | INFO  | sso6                      | BaseSessionImpl                | Created session is valid until MM/DD/YY HH:MM AM
YYYY-MM-DDT0HH:MM:SS.660Z | INFO  | vAPI-I/O dispatcher-1     | SessionApiSecurityUtil         | Created child session with session manager com.vmware.cis.session for session [email protected] (internal id ######-####-####-####-######, token 469e1...).

YYYY-MM-DDTHH:MM:SS.210Z | INFO  | vAPI-I/O dispatcher-1     | SessionApiSecurityUtil         | Created child session with session manager com.vmware.cis.session for session [email protected] (internal id ######-####-####-####-######, token 469e1...).
YYYY-MM-DDTHH:MM:SS.704Z | ERROR | vAPI-I/O dispatcher-0     | SessionFacade                  | Unexpected error occurred while executing the call with session [email protected](internal id ######-####-####-####-######, token 469e1...) for method com.vmware.cis.tasks.list with uuid #####-####-####-####-#######.
com.vmware.vapi.endpoint.common.UnacceptableResponseException: Response size 28828179b is greater than allowed 7000000b
        at com.vmware.vapi.endpoint.api.ResponseSizeLimitingClient$ResponseSizeLimitingCallback.received(ResponseSizeLimitingClient.java:88) [vapi-endpoint-1.0.0.jar:?]
        at com.vmware.vapi.internal.protocol.client.rpc.http.handle.NioSingleResponseConsumer.responseCompleted(NioSingleResponseConsumer.java:56) [vapi-runtime.jar:?]
        at com.vmware.vapi.internal.protocol.client.rpc.http.handle.NioDecoratorConsumer.responseCompleted(NioDecoratorConsumer.java:45) [vapi-runtime.jar:?]
        at org.apache.http.impl.nio.client.MainClientExec.responseCompleted(MainClientExec.java:383) [httpasyncclient-4.1.4.jar:4.1.4]
        at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:172) [httpasyncclient-4.1.4.jar:4.1.4]
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:448) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:338) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) [httpasyncclient-4.1.4.jar:4.1.4]
        at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) [httpasyncclient-4.1.4.jar:4.1.4]
        at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) [httpcore-nio-4.4.13.jar:4.4.13]
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) [httpcore-nio-4.4.13.jar:4.4.13]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_402]
YYYY-MM-DDTHH:MM:SS.707Z | WARN  | vAPI-I/O dispatcher-0     | ApiMethodSkeleton              | Implementation method reported unexpected exception: com.vmware.vapi.std.errors.InternalServerError
com.vmware.vapi.std.errors.InternalServerError: InternalServerError (com.vmware.vapi.std.errors.internal_server_error) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vapi.endpoint.badGateway,
    defaultMessage = The endpoint, while acting as a gateway, received an invalid response from an upstream server it accessed while attempting to fulfill the request.,
    args = [],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = INTERNAL_SERVER_ERROR

Resolution

This issue is resolved in vCenter 8.0U3e.