?
Solved

vCenter 5.1 install fails on W2008 R2 Enterprise in SSO installed

Posted on 2014-11-02
10
Medium Priority
?
841 Views
Last Modified: 2014-12-09
Hi,

Am trying to install vCenter 5.1 on a fresh Windows 2008 R2 Enterprise box.  It fails with the following:
The call to SRSetRestorePoint API failed. Returned status: 0. GetLastError() returned: 127

Any suggestions?

Thanks!

--Ben
0
Comment
Question by:Ben Conner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 3
10 Comments
 
LVL 123
ID: 40418608
If you look through the setup log, does it show any other errors ?
0
 

Author Comment

by:Ben Conner
ID: 40418624
Nothing with 'failed' in it; there were some errors when it was looking for stuff under c:\documents and settings\, but there was nothing under there.  Not sure why it was nosing around there to start with.  The only other things I saw with 'error' in them were strings getting loaded in the SQL Express database it uses.

--Ben
0
 
LVL 123
ID: 40418627
This is Windows 2008 R2 ?

This is not a re-install of vCenter Server or SSO ?
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:Ben Conner
ID: 40418631
Correct.

--Ben
0
 

Author Comment

by:Ben Conner
ID: 40418637
Scratch that.  I had initially tried to install vCenter 5.5; ran into a problem I didn't recognize, so I dropped back to 5.1.  The 5.5 install threw some weird errors:

CustomAction VM_IsVCREDIST64Installed returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action VM_IsVCREDIST64Installed, entry: VmSetupIsVCREDIST64Installed, library: C:\Users\ADMINI~1.LOC\AppData\Local\Temp\1\MSI4E8D.tmp
MSI (c) (08:CC) [12:30:51:639]: Product: Simple Install -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action VM_IsVCREDIST64Installed, entry: VmSetupIsVCREDIST64Installed, library: C:\Users\ADMINI~1.LOC\AppData\Local\Temp\1\MSI4E8D.tmp
MSI (c) (08:CC) [12:30:51:639]: Doing action: FatalError
Action 12:30:51: FatalError.
Action start 12:30:51: FatalError.
Action 12:30:51: FatalError. Dialog created
Action ended 12:30:56: FatalError. Return value 2.

Coudn't sort those out so I just tried to drop back to 5.1.

--Ben
0
 
LVL 123
ID: 40418650
do you have a

C:\ProgramData\VMware\

folder?
0
 

Author Comment

by:Ben Conner
ID: 40418653
No.

--Ben
0
 

Author Comment

by:Ben Conner
ID: 40418691
Decided to search for 'invalid' and got back this:

Action 14:34:13: VM_InstallCastle. Configuring vCenter Single Sign On. It will take few minutes...
MSI (s) (E0:04) [14:34:13:070]: Executing op: CustomActionSchedule(Action=VM_InstallCastle,ActionType=9217,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (E0:04) [14:34:13:070]: Creating MSIHANDLE (19023) of type 790536 for thread 2820
MSI (s) (E0:64) [14:34:13:070]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIEEFF.tmp, Entrypoint: VMExecuteSSOCommand
MSI (s) (E0!98) [14:34:14:802]: Creating MSIHANDLE (19024) of type 790531 for thread 2712
Error 29102.An invalid argument was provided.
MSI (s) (E0!98) [14:35:11:493]: Product: vCenter Single Sign On -- Error 29102.An invalid argument was provided.

Did try to see what was in the .tmp file.  Doesn't exist now.

--Ben
0
 

Accepted Solution

by:
Ben Conner earned 0 total points
ID: 40481325
Just doing some cleanup on EE; was never able to get 5.1 installed.  I finally did get 5.5 installed so that is close enough, I guess.

Thanks for the effort on this one!  Much appreciated...

--Ben
0
 

Author Closing Comment

by:Ben Conner
ID: 40488456
Other solutions didn't work; found a workaround instead.
0

Featured Post

How Blockchain Is Impacting Every Industry

Blockchain expert Alex Tapscott talks to Acronis VP Frank Jablonski about this revolutionary technology and how it's making inroads into other industries and facets of everyday life.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to delpoy the vCenter Server Appliance and how to configure its network settings Deploy OVF: Open VM console and configure networking:
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question