com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: A specified parameter was not correct: metricId Please see the server log to find more detail regarding exact cause of the failure.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by sc10n
, 1 year ago
Client received SOAP Fault from server: A specified parameter was not correct: metricId Please see the server log to find more detail regarding exact cause of the failure.
via Talend Open Integration Solution by Hitesh Vekaria, 1 year ago
Client received SOAP Fault from server: Cannot create a secure XMLInputFactory Please see the server log to find more detail regarding exact cause of the failure.
via Stack Overflow by Jayant Ahirrao
, 5 months ago
Client received SOAP Fault from server: A general system error occurred: Authorize Exception Please see the server log to find more detail regarding exact cause of the failure.
via Stack Overflow by Uchenna Nwanyanwu
, 2 years ago
Client received SOAP Fault from server: Soap Exception From Server Please see the server log to find more detail regarding exact cause of the failure.
via Stack Overflow by robyp7
, 1 year ago
Client received SOAP Fault from server: Cannot find dispatch method for {} Please see the server log to find more detail regarding exact cause of the failure.
via Oracle Community by user13756783, 1 year ago
Client received SOAP Fault from server: No payload. Expecting payload with { http://fatcaWs.xxxxx.it/ }Opwebmethod1 element Please see the server log to find more detail regarding exact cause of the failure.
com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: A specified parameter was not correct: metricId Please see the server log to find more detail regarding exact cause of the failure.
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:190)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:136)
at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:250)
at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:201)
at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:288)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:116)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.proxy.$Proxy38.queryPerf(Unknown Source)
at com.vmware.ee.statsfeeder.AbstractStatsFeeder.getPerfStats(AbstractStatsFeeder.java:148)
at com.vmware.ee.statsfeeder.StatsRetriever$1.run(StatsRetriever.java:186)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
16 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.