Comments on: Heads Up! vCloud Automation Center 6.0 installation fails

By: magander3

magander3 — Fri, 25 Apr 2014 07:08:58 +0000

In reply to Ashwini Rao. Ok thanks. i'll see if i can find something related to this error. Post a comment if you make any progress.

By: Ashwini Rao

Ashwini Rao — Thu, 24 Apr 2014 09:19:38 +0000

Hi Magnus,
I am using .Net 4.5, and below is the error message.

Error : 2014-04-24 02 40 13 083 PM :C:Program Files (x86)VMwarevCACServerConfigToolEncryptionKeyToolDynamicOps.Tools.EncryptionKeyTool.exe
Error : 2014-04-24 02 40 13 083 PM :Error: Encrypting passphrase failed.
Error : 2014-04-24 02 40 13 083 PM :Updated configuration file C:Program Files (x86)VMwarevCACServerModel Manager WebWeb.config successfully.

Thanks and Regards,
Ashwini Rao

By: magander3

magander3 — Thu, 24 Apr 2014 09:02:25 +0000

In reply to Ashwini Rao.

Ok. Can you post the log file or at least the error?
You are using .Net Framework 4.0 and not .Net Framework 4.5.1 ?

//Magnus

By: Ashwini Rao

Ashwini Rao — Thu, 24 Apr 2014 08:59:00 +0000

Hi,
I am using vCAC 6.0.1 and I have used the simple passphrase with no special characters.

Thanks and Regards,
Ashwini Rao

By: magander3

magander3 — Thu, 24 Apr 2014 08:52:57 +0000

In reply to Ashwini Rao.

Hi,
what version are you using? Version 6.0 had problem with special characters in the password. See e.g. the following blog post http://magander.se/2014/02/11/password-complexity-problem-in-vcloud-automation-center-6-0/

//Magnus

By: Ashwini Rao

Ashwini Rao — Thu, 24 Apr 2014 07:33:20 +0000

Hello,
When I am trying to install the vCAC IaaS server-Manager, all the prerequisites turn into green and all the test says it is ok and it even begins the installation but fails in between with the error “Encrypting Paasphrase Failed” tried changing the passphrase couple of times but it is still the same. Has anyone faced this issue before? Can anyone help me on this?

Thanks and Regards,
Ashwini Rao

By: vCloud Automation Center 6.0 SP1 released | VCDX56

vCloud Automation Center 6.0 SP1 released | VCDX56 — Fri, 14 Feb 2014 07:04:56 +0000

[…] is still no support for .Net 4.5.1. I wrote a blog post about that as well, which you can find here, a while […]

By: vCloud Automation Center – vCAC 6.0 – Proof of concepts – lessons learned | bmspeak

Thu, 16 Jan 2014 14:34:47 +0000

[…] IIS was then restarted with the IISRESET command and the vCAC Prerequisite Checker ran smoothly thereafter. VCDX56 – Magnus Andersson has described it in more detail here. […]

By: magander3

magander3 — Tue, 14 Jan 2014 06:33:39 +0000

In reply to JJ. Thanks for sharing the info JJ

By: JJ

JJ — Mon, 13 Jan 2014 22:04:30 +0000

.net 4.5.1 is not supported by vCAC 6.0. Please disable the auto upgrade to 4.5.1 in windows.

By: Viktor

Viktor — Mon, 13 Jan 2014 11:08:29 +0000

I’ve created a link back to your article.

By: VMware vCAC 6.0 installation tips - viktorious.nl - Virtualization & Cloud Management

Mon, 13 Jan 2014 11:08:01 +0000

[…] Important: when running Windows Update you will probably automatically install Microsoft .NET 4.5.1 on the Windows server. I faced some problems, that were not directly traceable: after removing .NET 4.5.1 and installing .NET 4.5 the problems disappeared. Note that prerequisite checker that is included in the installation process will not report any messages on this, although the installation will fail. .NET 4.5 is available here. This problem was also reported by Magnus Anderson at vcdx56.com. […]

By: magander3

magander3 — Mon, 13 Jan 2014 10:58:20 +0000

In reply to akismet-658dded5f70e97dfeeddaaf6d80e9d9b. Good summary, thanks for sharing.

By: akismet-658dded5f70e97dfeeddaaf6d80e9d9b

akismet-658dded5f70e97dfeeddaaf6d80e9d9b — Mon, 13 Jan 2014 10:49:44 +0000

Exactly ran into the same problem! Summarized some best practices and other issues I’ve faced here: http://www.viktorious.nl/2013/12/19/vcac-6-0-installation-tips/.

I think Windows Update for 2008R2 will automatically install 4.5.1.

By: magander3

magander3 — Mon, 13 Jan 2014 09:52:17 +0000

No problem, glad it solved your problem.

By: Nuno Fernandes (@nmiguelrf)

Nuno Fernandes (@nmiguelrf) — Mon, 13 Jan 2014 09:20:30 +0000

worked perfectly 🙂 thank you for sharing the info, nice week