{"id":4606,"date":"2014-08-20T14:10:25","date_gmt":"2014-08-20T13:10:25","guid":{"rendered":"http:\/\/vmdamentals.com\/?p=4606"},"modified":"2014-08-20T14:19:23","modified_gmt":"2014-08-20T13:19:23","slug":"solved-vcac-6-01-you-cannot-perform-that-action-because-the-system-cannot-connect-to-the-provider-at-httpsvcacserver8281vcoapi","status":"publish","type":"post","link":"https:\/\/www.vmdamentals.com\/?p=4606","title":{"rendered":"Solved: vCAC 6.01 &#8220;You cannot perform that action because the system cannot connect to the provider at https:\/\/vcacserver:8281\/vco\/api\/&#8221;"},"content":{"rendered":"<blockquote><p>After a long long rest I dusted off the VMdamentals.com blog site and I&#8217;m ready to rock again! This time with an error in vCAC 6.01 that I could not get solved&#8230; But finally did \ud83d\ude09\n<\/p><\/blockquote>\n<p><BR><br \/>\n<strong>&#8220;You cannot perform that action because the system cannot connect to the provider at https:\/\/vcac:8281\/vco\/api\/&#8221;<\/strong><\/p>\n<p>This is the error that kept popping up everywhere. As soon as vCAC 6.01 touched vCenter Orchestrator this would <!--more--><\/p>\n<p>pop up. Strangely, there wasn&#8217;t all too much to change in the setup, as I was using the internal vCO engine embedded inside the vCAC appliance.<\/p>\n<div id=\"attachment_4630\" style=\"width: 570px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/vcac-vco-error011.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-4630\" src=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/vcac-vco-error011-560x86.png\" alt=\"What to do if vCAC keeps spitting this error at you?\" width=\"560\" height=\"86\" class=\"size-large wp-image-4630\" srcset=\"https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/vcac-vco-error011-560x86.png 560w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/vcac-vco-error011-270x41.png 270w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/vcac-vco-error011.png 877w\" sizes=\"auto, (max-width: 560px) 100vw, 560px\" \/><\/a><p id=\"caption-attachment-4630\" class=\"wp-caption-text\">What to do if vCAC keeps spitting this error at you?<\/p><\/div>\n<p>So what to do? First I asked <a href=\"http:\/\/lmgtfy.com\/?q=You+cannot+perform+that+action+because+the+system+cannot+connect+to+the+provider+at+https%3A%2F%2F\" title=\"Let me Google That for you\" target=\"_blank\">Google<\/a>. I found two possible answers:<\/p>\n<ol>\n<li>Kendrick Coleman had <a href=\"http:\/\/kendrickcoleman.com\/index.php\/Tech-Blog\/vcac-error-connecting-to-vco-api-fixed.html\" title=\"Kendrik Coleman blog post on vCAC error\" target=\"_blank\">this<\/a> blogpost;<\/li>\n<li><a href=\"https:\/\/communities.vmware.com\/message\/2353694\" title=\"VMware communities discussion\" target=\"_blank\">This<\/a> VMware Communities discussion.<\/li>\n<\/ol>\n<p>But neither pointed me to the solution. After banging my head for some time, I tried to simply test the vCO connection:<\/p>\n<div id=\"attachment_4619\" style=\"width: 570px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/Cannot-connect-to-vCO.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-4619\" src=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/Cannot-connect-to-vCO-560x277.png\" alt=\"Oops. That should simply work...\" width=\"560\" height=\"277\" class=\"size-large wp-image-4619\" srcset=\"https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/Cannot-connect-to-vCO-560x277.png 560w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/Cannot-connect-to-vCO-270x133.png 270w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/Cannot-connect-to-vCO.png 768w\" sizes=\"auto, (max-width: 560px) 100vw, 560px\" \/><\/a><p id=\"caption-attachment-4619\" class=\"wp-caption-text\">Oops. That should simply work&#8230;<\/p><\/div>\n<p>As you can see, simply testing the connection from the vCAC appliance to its own internal vCO workflow engine fails?!?!<\/p>\n<p>So next I tried to simply point to the local vCO instance using the &#8220;external settings&#8221;:<\/p>\n<div id=\"attachment_4627\" style=\"width: 570px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/external-to-internal-vco1.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-4627\" src=\"http:\/\/vmdamentals.com\/wp-content\/uploads\/2014\/08\/external-to-internal-vco1-560x316.png\" alt=\"Pointing the vCAC to an external vCO instance but actually pointing to it&#039;s own local vCO instance.\" width=\"560\" height=\"316\" class=\"size-large wp-image-4627\" srcset=\"https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/external-to-internal-vco1-560x316.png 560w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/external-to-internal-vco1-270x152.png 270w, https:\/\/www.vmdamentals.com\/wp-content\/uploads\/2014\/08\/external-to-internal-vco1.png 1125w\" sizes=\"auto, (max-width: 560px) 100vw, 560px\" \/><\/a><p id=\"caption-attachment-4627\" class=\"wp-caption-text\">Pointing the vCAC to an external vCO instance but actually pointing to it&#8217;s own local vCO instance.<\/p><\/div>\n<p>After checking, the connection was now successful! And as a result&#8230; The infamous error &#8220;You cannot perform that action because the system cannot connect to the provider at https:\/\/vcacserver:8281\/vco\/api\/&#8221; disappeared.<\/p>\n<p>Problem solved \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After a long long rest I dusted off the VMdamentals.com blog site and I&#8217;m ready to rock again! This time with an error in vCAC 6.01 that I could not get solved&#8230; But finally did \ud83d\ude09 &#8220;You cannot perform that action because the system cannot connect to the provider at https:\/\/vcac:8281\/vco\/api\/&#8221; This is the error [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[594,5],"tags":[595,596,597,599,598,600],"class_list":["post-4606","post","type-post","status-publish","format-standard","hentry","category-software-defined","category-vmware","tag-vcac","tag-vcac-6-01","tag-vcac-v6-01","tag-vcenter-orchestrator","tag-vco","tag-you-cannot-perform-that-action-because-the-system-cannot-connect-to-the-provider-at"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4606"}],"version-history":[{"count":13,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4606\/revisions"}],"predecessor-version":[{"id":4631,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4606\/revisions\/4631"}],"wp:attachment":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4606"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}