Solved: vCAC 6.01 “You cannot perform that action because the system cannot connect to the provider at https://vcacserver:8281/vco/api/”

After a long long rest I dusted off the VMdamentals.com blog site and I’m ready to rock again! This time with an error in vCAC 6.01 that I could not get solved… But finally did 😉



“You cannot perform that action because the system cannot connect to the provider at https://vcac:8281/vco/api/”

This is the error that kept popping up everywhere. As soon as vCAC 6.01 touched vCenter Orchestrator this would

pop up. Strangely, there wasn’t all too much to change in the setup, as I was using the internal vCO engine embedded inside the vCAC appliance.

What to do if vCAC keeps spitting this error at you?

What to do if vCAC keeps spitting this error at you?

So what to do? First I asked Google. I found two possible answers:

  1. Kendrick Coleman had this blogpost;
  2. This VMware Communities discussion.

But neither pointed me to the solution. After banging my head for some time, I tried to simply test the vCO connection:

Oops. That should simply work...

Oops. That should simply work…

As you can see, simply testing the connection from the vCAC appliance to its own internal vCO workflow engine fails?!?!

So next I tried to simply point to the local vCO instance using the “external settings”:

Pointing the vCAC to an external vCO instance but actually pointing to it's own local vCO instance.

Pointing the vCAC to an external vCO instance but actually pointing to it’s own local vCO instance.

After checking, the connection was now successful! And as a result… The infamous error “You cannot perform that action because the system cannot connect to the provider at https://vcacserver:8281/vco/api/” disappeared.

Problem solved 🙂

Comments are closed.

Soon to come
  • Coming soon

    • Determining Linked Clone overhead
    • Designing the Future part1: Server-Storage fusion
    • Whiteboxing part 4: Networking your homelab
    • Deduplication: Great or greatly overrated?
    • Roads and routes
    • Stretching a VMware cluster and "sidedness"
    • Stretching VMware clusters - what noone tells you
    • VMware vSAN: What is it?
    • VMware snapshots explained
    • Whiteboxing part 3b: Using Nexenta for your homelab
    • widget_image
    • sidebars_widgets
  • Blogroll
    Links
    Archives