Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

vCAC Designer (cloudutil.exe) will not launch after upgrading to 6.1

$
0
0

After recently upgrading from 6.0.1 to 6.1, we are unable to launch the vCAC Designer GUI (cloudutil.exe). The error shown when launching the Designer client is as follows:

 

DesignerError.png

 

We've tried the following already without success:

 

  1. We have a ticket open with support. A sev 1 for two weeks now. The ticket is with engineering. Substantial amounts of logs have been provided to support.
  2. The Designer was upgraded as part of the 6.1 install. We followed the procedure of uninstalling the old Designer client, downloading the new one from the IaaS VAMI, and installing it.
  3. We receive the same error regardless of what client or server the Designer client is installed on. We've tried it on the IaaS server itself (Windows Server 2008 R2 SP1), and from several client machines (WIndows 7 SP1).
  4. We are using self-signed certs. Not that it should matter as it was working prior to the 6.1 upgrade with self-signed certs, but we've validated the cert is in the trusted store on all machines where the client is attempting to run from.
  5. We've tried removing the client, making sure the client directory no longer exists, and reinstalling the client.
  6. Also tried running the client installer 'as administrator'.
  7. Validated the client installer (DesignCenter-Setup.exe) is not 'blocked' by right clicking on it-->properties-->unblock.
  8. Tried running the Designer client (cloudutil.exe) in various compatibility modes.
  9. We are able to run query commands from the CLI using cloudutil.exe. This confirms it is able to talk to the back end. We can even list all our stubworkflows and see the various revisions of them, but you can't edit/view the stubworkflows using the CLI (this needs to be fixed on a separate note.....).

 

We noticed the DynamicOps.Repository assembly in the error references Version 6.0.0.0 after the upgrade. Some assemblies don't get upgraded/replaced as part of the upgrade it appears so it's possible this is normal, but it stood out.

 

Unrelated to this, we are having an issue with one specific stub workflow after upgrading as well and have a separate post open regarding it here Stub workflow WFStubBuildingMachine fails after upgrading to 6.1

 

Because we can't get into the Designer client, we aren't able to troubleshoot it, which means we are down hard. We'd prefer not to roll back even though we have good backups, as if no one else is experiencing this issue then VMware will likely not get to the root of it and we won't be able to upgrade to 6.1 down the road with confidence.

 

Has anyone seen this or anything similar? Even if you haven't, do you have any suggestions to try?


Viewing all articles
Browse latest Browse all 9859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>