Solved

vCenter 5.1 install fails on W2008 R2 Enterprise in SSO installed

Posted on 2014-11-02
10
776 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
  • 7
  • 3
10 Comments
 
LVL 118
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 118
ID: 40418627
This is Windows 2008 R2 ?

This is not a re-install of vCenter Server or SSO ?
0
 

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
Complete Microsoft Windows PC® & Mac Backup

Backup and recovery solutions to protect all your PCs & Mac– on-premises or in remote locations. Acronis backs up entire PC or Mac with patented reliable disk imaging technology and you will be able to restore workstations to a new, dissimilar hardware in minutes.

 
LVL 118
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

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

It Is not possible to enable LLDP in vSwitch(at least is not supported by VMware), so in this article we will enable this, and also go trough how to enabled CDP and how to get this information in vSwitches and also in vDS.
Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

746 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now