vlho
Hot Shot
Hot Shot

VMware Client Integration Plugin 6.0 install failed - solution

Hi,

I tried install VMware Client Integration Plugin 6.0 for deploy new vCenter Server VA and I received this error:

There is a problem with this Windows Installer package.

A program run as part of the setup did finish as expected.

Contact your support personnel or package vendor.

On the background is a window with status:

Installing certificates and starting services...

In folder %TEMP% is log file vmmsi.log_<date_time>_Failed.log

Key data:

14:24:29:296]: Executing op: ActionStart(Name=CsdServiceInstall,Description=Installing certificates and starting service...,)

Action 14:24:29: CsdServiceInstall. Installing certificates and starting service...

MSI (s) (60:34) [14:24:29:306]: Executing op: CustomActionSchedule(Action=CsdServiceInstall,ActionType=3090,Source=C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe,Target=--install,)

CustomAction CsdServiceInstall returned actual error code 3 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (60:34) [14:24:29:936]: Note: 1: 1722 2: CsdServiceInstall 3: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe 4: --install

MSI (s) (60:34) [14:24:29:936]: Note: 1: 2205 2:  3: Error

MSI (s) (60:34) [14:24:29:936]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install

MSI (s) (60:34) [14:24:32:005]: Note: 1: 2205 2:  3: Error

MSI (s) (60:34) [14:24:32:005]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

MSI (s) (60:34) [14:24:32:005]: Product: VMware Client Integration Plug-in 6.0.0 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install

Unfortunately I couldn't find out the reason of error from this log.

After my extremely long researching I find out

that subprocess vmware-csd (creating keys and certificetes) logs into the folder C:\ProgramData\VMware\CIP\csd\logs

Example of the log file (csd_000x.log) in troublefree installation:

[2015-03-16 16:30:39] [INFO] Certificate registered!!!

[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.

[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.

[2015-03-16 16:30:39] [INFO] Successful install of CSD protocol handler.

In my case log file ended:

[2015-03-16 16:30:39] [INFO] Certificate registered!!!

There were missing records about some modification of file hosts.

Reason:

Installer will fail, if the file hosts.bak exists there before running installation of VMware Client Integration Plugin 6.0 !

Solution:

Rename or delete file hosts.bak in folder C:\Windows\System32\drivers\etc\

Good Luck.

P.S.

Deacivate any antivirus before starting the installation of VMware Client Integration Plugin 6.0

29 Replies
DiVaio
Enthusiast
Enthusiast

Great post, I had the same problem on my workstation, thanks a lot! Smiley Happy

0 Kudos
vanree
Enthusiast
Enthusiast

Thanks for your post. I just experienced the same problem, the copy of hosts file failed.

I my case it was the Firewall process of McAfee causing the file to be locked and the only way around it was to un-install McAfee Firewall (SaaS version), even disabling all McAfee functions temporarily did not work.

Hope it helps someone else.

0 Kudos
GalNeb
Enthusiast
Enthusiast

I had a similar problem.  My Hosts file was too big for the installer/uninstaller to handle due to having SpyBot installed (441k in fact).  I trimmed it down to the basics and the installer/uninstaller ran ok then.  BTW, ran the SpyBot immunization after I was done and it put everything back into the hosts file automagically.  For those of you who don't know what I am talking about, SpyBot adds thousands of known sites with malware/spyware to the hosts file to block access to them.

Old enough to know better, young enough to try anyway
0 Kudos
radio_müsli
Contributor
Contributor

Hi there!

We are planning to deploy the VMWare Client Integration Plugin 6.0.0 to several dozen computers in our network. We are using Microsoft System Center Configuration Manager to manage our client (e.g. install software packages).

The problem we face with this installation (MSI extracted from VMware-ClientIntegrationPlugin-6.0.0.exe) is the following:
The installation of the MSI fails with error code 1603, if the MSI is installed in the windows SYSTEM user context (SCCM uses this context to install software packages). With a normal administrator user the MSI runs fine and exits with exit code 0.

In both cases (admin user, system user) the MSI is called as follows:
C:\Windows\system32\msiexec.exe /qn /i "VMware-ClientIntegrationPlugin-6.0.0.msi" /l*v "C:\ProgramData\Logs\VMWare_ClientIntegrationPlugin_6.0.0_i.log"


I investigated this issue and found this quiet similar problem here.


The described solution (rename hosts.bak, which exists sometimes, but not always) to this issue does not affect the result, so the problem remains the same. I tried to narrow the problem down with the following methods:


1. MSI verbose Logging (Please find these files attached)

  • VMWare_ClientIntegrationPlugin_6.0.0_i_2015-08-07_130518_system.log -> System Account
  • VMWare_ClientIntegrationPlugin_6.0.0_i_2015-08-07_130549_admin.log -> Administrator Account
    -> After the following line, the log file differs
    Executing op: CustomActionSchedule(Action=CsdServiceInstall,ActionType=3090,Source=C:\Program Files\VMware\Client Integration Plug-in 6.0\vmware-csd.exe,Target=--install,)


2. ProcMon Capture of "vmware-csd.exe"

As the verbose Logging led to a problem with "vmware-csd.exe" I captured all operations of it with ProcMon, one time with the system account (fails), the other time with the administrator account (success). (Please find "ProcMon_vmware-csd.exe_events_system+admin.xlsx" attached)@

Unfortunately I wasn't able to make any sense of the differences.

To reproduce this issue, you can use "psexec.exe -s -i cmd.exe" to run a CMD within system account context.

Is there a workaround to install this Plugin with the system account?

Any help or hints are much apprechiated!

Thanks,
Arno

0 Kudos
PeterVG
Contributor
Contributor

HI Arno,

did you find a solution to this problem? We are having the same issue...

Grtz, Peter

0 Kudos
admin
Immortal
Immortal

Hello-

Did anyone find a resolution to this issue?

Thank you-

0 Kudos
DaddyBurrito
Contributor
Contributor

I am also experiencing this problem. I am attempting to access from Server 2012 Datacenter and I am not using IE Enhanced Security Mode and I have added the Desktop Experience feature so Flash is working properly. I checked for the .bak file and it doesn't exist on this system. I am stuck and not sure how to proceed.

0 Kudos
admin
Immortal
Immortal

Hang tight big daddyburrito, Im working on a solution. When I have it, so will you!

0 Kudos
shooker
Contributor
Contributor

I had the same problem. What worked for me was ...

Navigated to:

C:\Windows\System32\drivers\etc

Deleted:

Hosts.back

Hosts.new

Changed Properties on "Hosts" [Removed Read Only]

Apply.

pastedImage_0.png

Run: VMware Client Integration Plugin 6.0 again

Success!

NTShad0w
Enthusiast
Enthusiast

hi mates,

VMware-ClientIntegrationPlugin-6.0.0.exe installer have some seriously bugs.

Host file can't bee too big (lol!!) and it's also "good" when it's not read-only and also its good idea to disable any AV/AS/AM software during install and also when you have  failed install, installer don't clean 2 files (hosts.new and hosts.bak) so you have to delete these files before next try.

Good luck mates, and for VMware stuff... Mates, try to take care what you send to a public for huge money as an expensive production product!!!!

best regards

NTShad0w

0 Kudos
KWKirchner
Enthusiast
Enthusiast

FWIW,

I just had an issue with the VCSA6 plug-in install that referenced the hosts file (said it was currently in use by another process).  Rebooted system and tried again. This time it was successful.

0 Kudos
gio_dim
Contributor
Contributor

shookershooker's solution works!!!

If host file is in "read only mode" installation fails.

You should also delete .bak .new hostfiles.

0 Kudos
chrisgierke
Contributor
Contributor

Thanks for posting this shooker

Exactly what I had to do as well to get the installation to complete.

0 Kudos
Max_Mustermann
Contributor
Contributor

Hello,

we are facing the same installation problem with the VMware Client Integration Plugin 6.0 when installing with system rights.

The solution deleting the hosts.bak-file didn't work.

Did anyone find a solution for this problem?

Thanks.

0 Kudos
jiggeLigge
Contributor
Contributor

Have been able to fix that.

Our VMware guru gave us a corresponding mst file.

The trouble maker was the casdservice. Firstly the common plugin will be installed and later on the mentioned service.

Everything is fine now. Please feel free to use the attachted mst file 🙂

Cheerio

0 Kudos
Arabum
Contributor
Contributor

@Hi

I made my own fix, I do not delete the CustoAction I do let it run separately. everything is installed and works also with system account.

 

And Uninstall works as well.

 

0 Kudos
Arabum
Contributor
Contributor

hi,

your uninstall dous not work.

Greetins

 

0 Kudos
djames06
Contributor
Contributor

Hey Jigge,

I'm using the (msiexec.exe -i c:ClientIntergrationPlugin.mst) enter and getting a error "This installation package could not be opened". This tells me the file is bad.

What did you do prior to installing it. What I'm I missing here?

Thanks

0 Kudos
vTardo
Contributor
Contributor

Hi Guys,

         I've run into this issue with several VMware products working in a "secure" ( Federal ) environment.  A lot of the former vCAC IaaS components suffered from this same issue.  I've gotten around it by doing this:

Attempt Install until you get the error ( Don't click "OK" yet 😞

Corrupt.png

2.  Open a command prompt or Powershell that has access to the user context you are running under:

SCREENIE.png

3.  Find the GUID that matches the time you attempted install ( in this case 26JUN at 1347PM ) and cd to that directory and XCOPY/COPY/ROBOCOPY the .msi file from the Directory to another location and use this MSI package to install instead.  ( I think VMware repackaged this to comply with SHA256 signatures, but that's total speculation on my part. )

0 Kudos