VMware Cloud Community
thomps01
Enthusiast
Enthusiast

Error whilst installing vCAC 6 - error MSB3073

Hi

I've been attempting to install the IAAS element of vCAC 6 for a few days now and it keeps failing at the same place.

I've configured a Windows 2008 R2 server, joined it to a domain and configured DNS, NTP etc

.NET 4.5 installed

IIS7 role installed

I ran the powershell script as per Kendrick colemans blog to enable all the correct bits

My SQL database server runs on another box and the install seems to be creating a database ok

The following is from the end of the vCACConfiguration log file. Any ideas would be welcome.

Warning: Non-zero return code. Command failed.

Info : 2014-04-14 01 33 07 893 PM :C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(563,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" MoveRegistrationDataToDB --FileName "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.data" -s "C3-SQLcluster01" -d "vCAC" -v" exited with code 1.

Info : 2014-04-14 01 33 07 893 PM :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (InitializeRepo target(s)) -- FAILED.

Info : 2014-04-14 01 33 07 893 PM :Build FAILED.

Info : 2014-04-14 01 33 07 893 PM :"C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (InitializeRepo target) (1) ->

Info : 2014-04-14 01 33 07 893 PM :(InitializeRepo target) ->

Info : 2014-04-14 01 33 07 893 PM :  C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(563,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" MoveRegistrationDataToDB --FileName "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.data" -s "C3-SQLcluster01" -d "vCAC" -v" exited with code 1.

Info : 2014-04-14 01 33 07 908 PM :    0 Warning(s)

Info : 2014-04-14 01 33 07 908 PM :    1 Error(s)

Info : 2014-04-14 01 33 07 908 PM :Time Elapsed 00:00:14.83

0 Kudos
9 Replies
VirExprt
Expert
Expert

Hello ,

this looks like your setup have trouble registering .NET framework and have some privileges issues with DB while DB write

If you can cleanup your failed install by cleaning all Folders created by vCAC on your IAAS component under Program Files

Delete the DB instance created and make sure you have your Account used for installation purpose have local admin privileges on IAAS server and Sysadmin privileges on DB server with all required ports open.

Repair .net 4.5 and reboot the machine

Run the following command “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -iru” and reset IIS

this should resolve your issue.

Br,

MG

Regards, MG
0 Kudos
paulfries
Contributor
Contributor

I am getting this exact same error. Going to try the fix mentioned by VirExpert here and will report back.

FYI, I have been pulling my hair out on this one. I have tried this on two separate freshly installed VMs. One 2008 R2 and one 2012 and get the same error. I've tried it both with a remote SQL and local.

0 Kudos
paulfries
Contributor
Contributor

Just an update. The above fix unfortunately did not work in my case.

I ended up installing a fresh image of 2008 R2, then making sure that I installed IIS before installing .NET. (I believe this was the key).

After that I ran the PS script from Kedrick Coleman, and executed the installer after confirming that the prereq check was all green.

The install went through without a hitch this time.

0 Kudos
gsaliensjr
Enthusiast
Enthusiast


I am going to try that approach.  Man, I hope that works.

0 Kudos
gsaliensjr
Enthusiast
Enthusiast

Followed your process but I am still getting the same error concerning ModelManager.  Is there something SQL related that could be the problem?

0 Kudos
gsaliensjr
Enthusiast
Enthusiast


Attaching a screenshot of error.  Also including some the log entries

________________________________

Info : 2014-04-19 02 56 33 133 PM :C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(528,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterUIPlugin -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\plugin.json" -v" exited with code 1.

Info : 2014-04-19 02 56 33 133 PM :Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (VARegistrationFinalSteps target(s)) -- FAILED.

Info : 2014-04-19 02 56 33 133 PM :Build FAILED.

Info : 2014-04-19 02 56 33 149 PM :"C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (VARegistrationFinalSteps target) (1) ->

Info : 2014-04-19 02 56 33 149 PM :(VARegistrationFinalSteps target) ->

Info : 2014-04-19 02 56 33 149 PM :  C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(528,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterUIPlugin -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\plugin.json" -v" exited with code 1.

Info : 2014-04-19 02 56 33 149 PM :    0 Warning(s)

Info : 2014-04-19 02 56 33 149 PM :    1 Error(s)model_manager_error.png

0 Kudos
Aronov
VMware Employee
VMware Employee

You got an error calling the VCAC-Config. You can either get details from the VCAC-Config log or re-run the command from a console window and check the exception details in the console

"C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" RegisterUIPlugin -f "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\plugin.json" -v"

0 Kudos
DonalB
Enthusiast
Enthusiast

Appreciate I'm posting on an old thread but in case anyone else get's stuck on this - I was getting the exact same issue with a vRA 6.2 install and the logs weren't really giving me any clue as to what was going on. Looooong story short - I had to specify the SQL Instance name along with the server name ; hadn't had to do this in previous installs which is why this was somewhat confusing. OS used was Win2012R2 for the IaaS machines and SQL 2014 Express for the SQL instance (it's a lab environment so not fussed about the SQL support). So whenever the database server was being asked for setting it to be <FQDN>\<SQLInstance> sorted this out. I had named the SQL instance VRSQL so the format looked like this <FQDN>\VRSQL

For further background, I was doing a distributed install so what threw another kink into it was that the first part of the Custom install is to create the database and using just the server name without the instance name worked fine for creating the database. But then putting only the server name in when installing the Primary IaaS Website & Model Manager in the next run of the installer would cause the same error as listed on this thread

Hope this helps someone else out, had a truly frustrating week trying to figure this out and in fairness it being something simple whilst making me feel a bit stupid is also a good thing as it isn't black magic! 😉

Cheers

DB

0 Kudos
GaryJBlake
VMware Employee
VMware Employee

This could be a red herring in the context of this issue as I can not see the error from higher up in the log file, but if any of the following are true:

- Info : 2014-01-13 07 43 32 679 PM :  System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

- Your are doing a distributed install with a Load Balancer

Make sure that the Load Balancer is configured so that monitoring is disabled for the Web Site until after the installation of the Web Site and ModelManagerData on the first node.

0 Kudos