VMWare VCenter COnverter 6.3,6.4 installation issue in windows server

[jiigmey]

I tried installing both the 6.3 and 6.4 version in my windows server 2012 but failed with error message "Could not start the service"

I checked the documentation of this version and could not find any OS version support requirement. 

Also the available discussions on this community on this issue did not help to solve my problem

[pcgeek2009]

Are you trying to push a remote install or a local? Either way, try running the process as the local administrator or right-click and select "run as administrator". You could also see if UAC is enabled. I have seen that cause an issue before. 

[jiigmey]

I have tried running as administrator as well. Giving same error

[pcgeek2009]

So as a test, i just successfully installed 6.3 on a Windows Server 2012R2 system. Are there any errors registered in the event viewer for the application install. I have seen issues were the event ID or wording of the issue can point to the solution. I did use the FQDN for the name, and <servername>\administrator for the account. I have found using the local admin istrator account works best. 

[jiigmey]

HI thanks for responding. Could you explain in more detail, i couldn't get your point. I am also trying from local Administrator user

[pcgeek2009]

I was mainly verifying that it would successfully install and convert a 2012 server. Therefore, there is something specific about the server you are trying to install. If you look at the event viewer on the 2012 server you are trying to install, are there any error messages under "Applicaiton" that are specific to the converter install. That should shed some light on the issue if there are event ID's with the failure messaged. 

[jiigmey]

this is the error generated when i try to install: Windows Installer installed the product. Product Name: VMware vCenter Converter Standalone. Product Version: 6.3.0.20575345. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603.

[pcgeek2009]

There is a VMware KB article on the software failure with 1603. One part is that it think the app is already installed on the system. The other part is a set of permissions. 

https://learn.microsoft.com/en-US/troubleshoot/windows-server/application-management/msi-installatio...

Another option would be to change the timeout period by editing the registry. 

To change the service timeout period:

Step 1: Click the Start button, then click Run, type regedit, and click OK.

Step 2: In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

Step 3: Select Control Folder, look at right-hand the ServicesPipeTimeout entry, right-click that entry and then select Modify.

Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value 32 bit, then typing ServicesPipeTimeout, and clicking Enter.

Step 4: Modify the ServicePipeTimeout value,

Click Decimal, enter the new timeout value = 180000 OR 300000 ( In Milliseconds ) and then click OK.

[plamen_d]

Hello

Can you try installing again and look up for the installation logs? They are "%TEMP%\vminst.log" and "%TEMP%\vmconvservermsi.log"; the latter might not be present but the former should.

[jiigmey]

This error is being generated: 

vieInstUtil: 01/04/24 10:14:52 VMDumpProperties
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::DumpProperties::========== MSI properties
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ALLUSERS]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[AdminUser]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[AppDataFolder]=C:\Users\Administrator\AppData\Roaming\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[CommonAppDataFolder]=C:\ProgramData\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ComputerName]=ATMWEBSERVERDC-
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[INSTALLDIR]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[Installed]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[INSTALLLEVEL]=100
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[Intel]=6
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[Intel64]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ISSCHEDULEREBOOT]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[LogonUser]=Administrator
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MSIARPSETTINGSIDENTIFIER]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MSIDISABLERMRESTART]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiLogFileLocation]=C:\Users\ADMINI~1\AppData\Local\Temp\2\vmconvservermsi.log
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiLogging]=voicewarmupx
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiNTProductType]=3
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PhysicalMemory]=16290
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MSIRESTARTMANAGERCONTROL]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiRestartManagerSessionKey]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MSIRMSHUTDOWN]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiRunningElevated]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MsiSystemRebootPending]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[MSIUSEREALADMINDETECTION]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PackageCode]={EC90933E-2215-4BD2-B917-32771D662253}
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PackagecodeChanging]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PATCH]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PersonalFolder]=C:\Users\Administrator\Documents\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[PhysicalMemory]=16290
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[Privileged]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProductCode]={D1DFB9B2-F23D-4DF9-9A84-4600BE6E72D6}
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProductLanguage]=1033
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProductName]=VMware vCenter Converter Standalone
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProductState]=-1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProductVersion]=6.3.0.20575345
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProgramFilesFolder]=C:\Program Files (x86)\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ProgramFiles64Folder]=C:\Program Files\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[REBOOT]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[REINSTALL]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[REINSTALLMODE]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[RemoteAdminTS]=1
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[REMOVE]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ROOTDRIVE]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[ServicePackLevel]=0
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[SETUPEXEDIR]=C:\Users\Administrator\Documents
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[SourceDir]=C:\ProgramData\VMware\Installer\{EC90933E-2215-4BD2-B917-32771D662253}\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[SystemFolder]=C:\Windows\SysWOW64\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[System64Folder]=C:\Windows\system32\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[SystemLanguageID]=1033
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[TARGETDIR]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[TempFolder]=C:\Users\ADMINI~1\AppData\Local\Temp\2\
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[Template]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[TerminalServer]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[UILevel]=5
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[UpgradeCode]={5756DE24-DEB6-4027-8BF5-C0A14A553895}
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[UPGRADINGPRODUCTCODE]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[UserLanguageID]=1033
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[USERNAME]=Windows User
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[VersionMsi]=5.00
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[VersionNT]=603
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[VersionNT64]=603
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[WindowsBuild]=9600
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::DumpProperties::========== Custom properties
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[OLDVERSIONFOUND]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[OLDPRODUCTFOUND]=
vieInstUtil: 01/04/24 10:14:52 VMInstMsi::GetPropertyString::[NEWPRODUCTFOUND]=
vieInstUtil: 01/04/24 10:14:52 VMDumpProperties::done Res: 0
vieInstUtil: 01/04/24 10:14:52 --------------- CA exec: VMCheckRebootPending
vieInstUtil: 01/04/24 10:14:52 VMCheckRebootPending
vieInstUtil: 01/04/24 10:14:52 VMInstFileReboot::NeedRebootFile::Checking for reboot state (file)
vieInstUtil: 01/04/24 10:14:52 VMInstFileReboot::NeedRebootFile::Checking for reboot file: C:\Users\ADMINI~1\AppData\Local\Temp\2\vmreboot.tmp
vieInstUtil: 01/04/24 10:14:52 VMInstDir::FileExists::File: C:\Users\ADMINI~1\AppData\Local\Temp\2\vmreboot.tmp
vieInstUtil: 01/04/24 10:14:52 VMInstDir::FileExists::File: C:\Users\ADMINI~1\AppData\Local\Temp\2\vmreboot.tmp The system cannot find the file specified. Res: 2
vieInstUtil: 01/04/24 10:14:52 VMInstDir::FileExists::done Res: 0
vieInstUtil: 01/04/24 10:14:52 VMInstFileReboot::NeedRebootFile::done Res: 0
vieInstUtil: 01/04/24 10:14:52 VMInstRegReboot::NeedRebootReg::Checking for reboot state - registry
vieInstUtil: 01/04/24 10:14:52 VMInstReg::OpenKey:🔑 SOFTWARE\VMware, Inc\NeedReboot Error: 2
vieInstUtil: 01/04/24 10:14:52 VMInstReg::GetKeyValue::Cannot open key value HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc\NeedReboot Error: 2
vieInstUtil: 01/04/24 10:14:52 VMInstRegReboot::NeedRebootReg::done (registry) Res: 0
vieInstUtil: 01/04/24 10:14:52 VMCheckRebootPending::NO PENDING REBOOT
vieInstUtil: 01/04/24 10:14:52 VMCheckRebootPending::done Res: 0
vieInstUtil: 01/04/24 10:15:04 --------------- CA exec: VMDisableCloseMenu
vieInstUtil: 01/04/24 10:15:04 VMDisableCloseMenu
vieInstUtil: 01/04/24 10:15:04 VMInstMsi::GetPropertyString::[ProductName]=VMware vCenter Converter Standalone
vieInstUtil: 01/04/24 10:15:04 VMDisableCloseMenu::Error: 0
vieInstUtil: 01/04/24 10:15:04 VMDisableCloseMenu::done Res: 0

[pcgeek2009]

You may need to install or re-install the C++ Redistributable software. If it is installed, uninstall, reboot, then install again. 

Download Visual C++ Redistributable for Visual Studio 2015 from Official Microsoft Download Center

[navina]

Could be because of Group policies as well.
Is the Server domain joined?

[virtualqc]

disable antivirus when doing the installation

[jiigmey]

I am still not able to install it. I have created a new vm with fresh 2012R2 server. Still getting Could not start the service error

[pcgeek2009]

On the new machine, can you post the logs from the failed install?

[jiigmey]

I have tried installing 6.4 version in new windows 2019. Got the same error: 

Windows Installer installed the product. Product Name: VMware vCenter Converter Standalone. Product Version: 6.4.0.21710069. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603. 

[Preeti-P]

HI,

Error 1603 can be caused by several reasons like :

- Windows Installer is trying to install an application that is already installed.

- The installation folder of the application is encrypted.

- There are insufficient permissions to access the location where the software is being installed.

- Short file name creation is disabled.

- Conflicts with other software or services that are running on the computer.

- Conflicts with antivirus or other security software.

- Corrupted Windows Installer.

- Corrupted installation package.

- Unable to access install files in case of a web installer due to network and firewall blocks.

Please check the machine for above causes, and could you please try this:

1) Uninstall pre-installed Converter

2) Clean the installed locations  (C:\ProgramData\VMware\VMware vCenter Converter Standalone and C:\ProgramData\VMware\VMware vCenter Converter Standalone Client)

3) Reboot the machine

4) Install converter again