Hi all,
i am desperatly trying to install my vCenterServer 4.1 on a Windows2008 Standard SP2 x64 machine (4GBRam, 70GBHD) dual proc.
i use the embedded 2005 SQL express db as default. Installation terminates "successfully", but vmservices do not start ...
I checked DSN, seems to be ok, connection successfully.
I also tried installing the x64 native SQL client as mentioned in the doc ... no success.
Now, i really do not have any idea on how to get this up and running :smileycry:
do you have any event log errors? IIS is not installed on the box?
How did you create the DSN?
Try the x64 : %systemdrive%\Windows\System32\Odbcad32.exe
or
x86: %systemdrive%\Windows\SysWoW64\Odbcad32.exe
And see if anything of those work ..
- Kenth
No, no IIS installed, it's a blank Win2008 only connected to the domain.
Which logs to you need? vmware, sql, event viewer?
Thanks
look at the system and application logs on the vCenter Host OS.
Does this happen after rebooting the server?
Can you start the vCenter Service manually?
Maybe http://kb.vmware.com/kb/1007669 solves the issue.
André
Hi Kenth,
i used the first method to create the system DSN. as it is state in the manual to have a 64 bit DSN ...
Hi André,
it never starts, it's a fresh install. also manually it's not possible.
i'll try the procedure in KB ... thanks.
Ok ..
If you look at the DSN (system DSN!) what version of the driver does it have?
-Kenth
System Log: Server error 2 (0x2)
Applications Log: VMServer failed to initialize
that's it
in the vpxd.log file on the vCenter, does it have any "username error or password errors"?
You can try to reset the db password by running in a command prompt
vpxd.exe -p
Its located in your vcenter installation folder (on the vcenter server ofcourse )
-Kenth
..and you followed the KB article linked by a.p. This seems to me to be the fix, but....
no vpxd.log on the server ...
i checked all dependencies, and all looks good (even in the regedit, the values are OK).
delayed startup doesn't help too.....
i checked the event logs (windows application).
i can see, that it starts the VIM_VCDB, but i never see a "successfull" ...
that's strange, because i can connect to the DB with the odbc tool (connection successfull).
... it still can't conect to the DB :smileycry::smileyangry:
right now i am a little bit lost with all the infos of using a 64 Bit DSN.
do i have to configure the nativ client on the ...\system32\odbc32.exe or
on the WOW64 ...
this Windows box is not a domain controller correct? Have you installed any additional roles? Is starting from scratch an option. Maybe run you vCenter Server as a VM?
..and \system32\odbc32.exe is the correct one. Or simply go to Admistrative tools ODBC, system DSN. use SQL Native Client. That will be the proper DSN Setup.
Hi,
no, it's not a DC and no optional roles have been installed.
Uninstalling is an option, actually, i did it already 3 times
Installing as VM might be an option, but i am not sure about the pros and cons?
What do you think?
Even ESX experts were not able to get this up and running ...
So the solution was to use Windws Server 2003 64bit ... and it works!