Links not published yet but available. Currently downloading :smileygrin:
> Links removed <
Sorry guys, unless someone from VMware wants to overrule me I removed the links as this is not "Official GA" release.
Don Pomeroy
VMTN Forums User Moderator
Message was edited by: dpomeroy
There is a release document (although I'm not suggesting that this is the final release) with newer build numbers in a new forum mentioned in this thread -
I see what you mean. I guess the download game begins all over again, soon enough.
I'm downloading the new ones now, it appears only the build # for ESX has changed from last week.
Original builds posted last week:
ESX Latest Released Version: 3.5.0 - Released 12/03/07 - Build #64557
VirtualCenter Latest Released Version: 2.5 Released 12/03/07 - Build #64201
New updated builds posted this week:
ESX Latest Released Version: 3.5.0 - Released 12/10/07 - Build #64607
VirtualCenter Latest Released Version: 2.5 Released 12/10/07 - Build #64201
Eric Siebert
VMware Communities User Moderator
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
I hear you. I just finished the download. If it wasn't just past midnight, I would be loading it up to take it for a test run.
Download page has just been updated, I guess it's now official. Also the Release Notes link now works...
http://vmware.com/download/vi/vi3_patches.html
http://www.vmware.com/support/vi3/doc/vi3_esx35_vc25_rel_notes.html
Eric Siebert
VMware Communities User Moderator
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
so is there actually no change to VC? with last weeks downlad I am not able to connect to 2.5 after upgrading a 2.0 install, I even completely uninstalled, deleted database, rebooted, reinstalled, even tried the bundled mssql instead of my existing one. VC will not start during the install so the install never fully completes, but it will start manually though i cannot connect to it. This is on a physical Win2k3 server 32-bit where VC 2.0 worked fine.
My VC environment is so messed up I just want to start off new with this version. A new VC server pointing to a new database. Is it as easy as just managing the host from the new VC server? What do I lose by scrapping the DB? Do I lose resource pools, switches, etc? I suppose i could try it on a host with a couple of test VMs on it.
I had the same issue. It turns out the install removed the service account under which the account was running.
When I changed it back (to a user which could access the VC Database) all was fine...
Is there a link to the HCL for 3.5 I can't seem to find it.
tks
I'm not sure I understand. VC talks to the database via a TCP protocol and an MSSQL user account, service permissions should have nothing to do with it.
However, I had already tried changing the user account that the service runs from "system account" as to one that I run other services as and it did not help.
I don't understand it myself.
However, after the upgrade I was given an error about the service no starting, and subsequent restarts logged an event log (error code 0x2).
Changing the service account to one which had local admin rights (and admin rights on the SQL server) fixed it.
I'm due to change the account to a more appropriate and less privilaged account later tonight so work out which part of the change made the difference.
That's not to say your issue is the same as mine was though.
finally got it the finals all downloaded I've also just noticed that the build number on the add/remove for the VC components doesn't match the download, reinstalling again!
nope, still says "cannot establish initial connection" even though the service starts fine.
the only thing in the logs is:
The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Starting VMware VirtualCenter 2.5.0 build-64192.
To troubleshoot it, I used the shortcut that's added (to generate the log bundle zip). Reading through the collated logs gave me an insight into what was going on (I got something about an untrusted SQL connection for user ) which I took to mean it was attempting to use Integrated NTML authentication for a non-domain user
had a generic database error and no combination of config or crdentials would do anything useful eben though that worked for you. so i installed it all and tried again, this time using the mssql2k server I already have. 68 pages into the install pdf it finally tells me the user I made has to have db_owner on the msdb database as well as dbo on the database I created. what a pain! never had to do that before for any application.
I still get "a connection failure occured", though not I don't have a database error in the logs. I do have a new error though I have no idea what it means:
MOB started on pipe
.\pipe\vmware-vpxd-mob-pipe
-- BEGIN task-internal-3 -- -- vim.ServiceInstance.retrieveContent -- DB880B2B-6037-4455-A528-69B85E38C433
-- FINISH task-internal-3 -- -- vim.ServiceInstance.retrieveContent -- DB880B2B-6037-4455-A528-69B85E38C433
-- BEGIN task-internal-4 -- -- vim.SessionManager.GetCurrentSession -- DB880B2B-6037-4455-A528-69B85E38C433
-- FINISH task-internal-4 -- -- vim.SessionManager.GetCurrentSession -- DB880B2B-6037-4455-A528-69B85E38C433
-- BEGIN task-internal-5 -- -- vim.SessionManager.loginExtension -- DB880B2B-6037-4455-A528-69B85E38C433
-- FINISH task-internal-5 -- -- vim.SessionManager.loginExtension -- DB880B2B-6037-4455-A528-69B85E38C433
-- ERROR task-internal-5 -- -- vim.SessionManager.loginExtension: vim.fault.InvalidLogin:
(vim.fault.InvalidLogin) {
dynamicType = ,
msg = ""
}
so i called support.
turns out that if you have IIS installed and do a custom VC install to change the ports, it goes all to hell.
I stopped IIS, installed VC with the defaults, then I can stop the vmware web service and start IIS again and everything works, but I've yet to get the vmware web service working even after changing its ports in the config.