Problem after upgrade vCenter Server patch 1

[uma_kits]

I install vCenter Server 4 on Windows 2008 Standard x64 SP2. After I upgraded vCenter to patch 1. I found some issue on vCenter as below:

1. Can't use search function in VC

Error: "Could not acquire an authentication ticket for the query service: https://servername:8443/vws"

2. Can't show information in Hardware Status tab

Error: "Do not have permission for this command."

3. Can't show information in vCenter Service Status

Error: "Cannot access the health service"

I must uninstall vCenter and reinstall vCenter without patch 1 because it didn't have rollback function for vCenter patch 1.

Has anyone found issues like me?

[ICT-Freak]

Got this error too after installing patch 1. I fixed it by (re)moving VcCache-default-0.XhiveDatabase.DB. See http://ict-freak.nl/2009/09/10/vsphere-you-do-not-have-permission-to-run-this-command/ for more info.

[uma_kits]

I had tried to solve this problem from your solution by rename file extension (VcCache-default-0.XhiveDatabase.DB). But It didn't work for me. I think that vCenter Patch 1 solve only VMware HA function for IP Address class A. Thus I uninstall vCenter and fresh install vCenter again.

[uma_kits]

After I update vCenter Server to update 1 (Launch 19 Nov), It can help me to solve bug on patch1.

[cfp2000]

Hi!

I had the same problem but with vSphere 4.0.0.

the solution for me was to start VMware VirtualCenter Management Webservices...I don't know why, but somehow the service had stopped or never started after the last reboot of the vCenter Server.

[uma_kits]

Hi cfp2000

I have found a website that may be help you solve your issue.

vCenter Server Service does not start automatically

http://www.vladan.fr/vcenter-server-service-does-not-start-automaticaly

I had this issue with vCenter Server on my home lab. Virtual Center starts before the SQL database it depends on. I found a solution in a KB on VMware’s website.

This article provides steps to prevent the race condition from occurring. VirtualCenter service does not start after reboot.

First I checked log files of vCenter here: C:\Windows\Temp\VPX

I suppose that VirtualCenter Server service can be started manually with no problems. This is my case….

You need to add a dependency to the VirtualCenter service so that it waits for SQL Express remedies this.

To create a service dependency:

1. Click Start > Run. Type services.msc and press Enter.

2. Locate the SQL instance for VirtualCenter. For example, SQL Server (SQLEXP_VIM).

3. Open the SQL Express instance and note the Service Name. For example, MSSQL$SQLEXP_VIM .

4. In the Run dialog, type Regedit.exe and press Enter. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd

5. Double-click the DependOnService key and add the Service name using the name identified in step 3.

6. Go back to the Services Panel and open the SQL Server properties.

7. On the Dependencies tab, verify the VMware VirtualCenter service is listed as depending on the SQL service instance.