Solved

vCenter 5.1 install fails on W2008 R2 Enterprise in SSO installed

Posted on 2014-11-02
10
828 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 121
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 121
ID: 40418627
This is Windows 2008 R2 ?

This is not a re-install of vCenter Server or SSO ?
0
Building an interactive eFuture classroom

Watch and learn how ATEN provided a total control system solution including seamless switching matrix switch, HDBaseT extenders, PDU, lighting control to build an interactive eFuture classroom.

 

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 121
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

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

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

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
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 install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
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…

691 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