Unable to install vCenter Server 4.1

[unixweb]

I have vCenter Server running on a physical blade server (Win2008 Ent R2) all 64bit. No issues in the past updating with U1 or U2. Now trying to update to 4.1.

Database is SQL Express and no issues. On this round I try to run the install of vCenter Server and get an error 1719 that it cannot find the windows installer. Bear in mind I have upgraded twice with U1 and U2 with no issues. Same permissions etc.

Any thoughts what could be giving me the windows installer error message?

Thanks.

[rebootuser]

Hi unixweb. Is the installer file name/path specified, i.e. of the file required?

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

[pcerda]

Hi

can you install another msi file? This look like a Windows issue, not of the vCenter Server. Try this links:

- http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/1bd351e9-cc2e-4e99-84f9-e9c203f...

- http://blogs.technet.com/b/askperf/archive/2007/07/13/troubleshooting-a-windows-installer-issue.aspx

In the other hand, Have you check the md5sum of the ISO file of vCenter?

Try check the ISO file or download it again, then try install vCenter Server.

Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[angchief]

Here are the steps I followed to resolve this issue.

(1) uininstalled vCenter, Orchestrator, etc. along with deleting the VMware Folder in Program Files.

(2) Also deleted all the registry keys. Reinstalled fresh vCenter but same issue. I created a new account for the ODBC connections to eliminate the special characters.

(3) Followed the steps for the conversion of SQL Express 2005 to MS SQL 2005: http://get-admin.com/blog/?p=646

(4) I had created a 64 bit DSN for vCenter Server and 32 bit for Update Manager: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101040... . However, we continued to get the extension problem: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102479...

(5) Then went in to make changes to the ADAM portion of VMware that communicates to AD. You can view at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102479... and ADSI edit - http://communities.vmware.com/thread/277791

Solution:

(1) There is an issue with the vCenter 4.1 installer. We were careful to use a local administrator account for all installs (vCenter, Converter, VUM) on both vCenter and SQL).

(2) The caveat is that the installer also searches the vCenter database and uses the administrator rights assigned – whoever designed this should be shot!

(3) You have to go into the permissions of vsphere (vCenter) and edit those as the default permissions give administrators “read only” rights.

(4) Now vCenter Server is happy, we have converter installed along with VUM and the updates are working.

For the new SQL database follow the work at:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100438... and http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100399...

[idle-jam]

thanks for sharing