VMware Cloud Community
schepp
Leadership
Leadership
Jump to solution

start workflows in webviews - XMLHttpTransport Error: 500 Internal Server Error when trying to contact vCenter

Hey all,

I'm using the latest vCO version (5.5.2.1951762)

I have a deployment workflow that runs fine when started from the vCO client and also from vSphere Web Client.

When I try to run the same workflow from a webview (custom one as well as the default weboperator), I get the following error message as soon as I try to expand the vCenter in the tree view to select some object for an attribute:

Error: XMLHttpTransport Error: 500 Internal Server Error(type: error) 'err'


I've also tried other workflows, that generate drop down menues for template selection with a predefined array of VC:VirtualMachine objects. As soon as I start these workflows, I get the same error.

It doesn't matter if the workflow runs as Dialog or not.



So basicly vCO doesn't seem to be able to browse the vCenter Server inventory or something.

Tried to run the workflows with normal users and also with users that are part of the vCO admin group.

Logfile from /var/log/vmware/vco/app-server/server.log attached.

Any idea?

Regards

Tim

0 Kudos
1 Solution

Accepted Solutions
5 Replies
tschoergez
Leadership
Leadership
Jump to solution

Can you open an SR with VMware Support?

You might have hit a bug in the vCO platform. make sure to send them the exact information about the versions of vCO that you are using.

Cheers,

Joerg

schepp
Leadership
Leadership
Jump to solution

Hi Joerg,

I'm on a bug-hitting-spree, doh Smiley Wink

I'll open another SR.

Thanks

Tim

0 Kudos
JMC13
Contributor
Contributor
Jump to solution

Had the same issue,  its a bug and got a patch.  open a support case

igaydajiev
VMware Employee
VMware Employee
Jump to solution

We have already this issue reported and we are in process of publishing  kb article containing the fix.

it should be available until the  end of the week. Will provide the link once it is publicly available.

To verify that the issue is the same you can check vCO server log file for error messages similar to :

ch.dunes.vso.sdk.SDKTypeConvertor_server$1 cannot be cast to ch.dunes.model.dunes.DunesObject

0 Kudos
igaydajiev
VMware Employee
VMware Employee
Jump to solution

0 Kudos