vCenter 5.1 install fails on W2008 R2 Enterprise in SSO installed

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
Ben ConnerCTO, SAS developerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you look through the setup log, does it show any other errors ?
0
Ben ConnerCTO, SAS developerAuthor Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This is Windows 2008 R2 ?

This is not a re-install of vCenter Server or SSO ?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Ben ConnerCTO, SAS developerAuthor Commented:
Correct.

--Ben
0
Ben ConnerCTO, SAS developerAuthor Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
do you have a

C:\ProgramData\VMware\

folder?
0
Ben ConnerCTO, SAS developerAuthor Commented:
No.

--Ben
0
Ben ConnerCTO, SAS developerAuthor Commented:
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
Ben ConnerCTO, SAS developerAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ben ConnerCTO, SAS developerAuthor Commented:
Other solutions didn't work; found a workaround instead.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.