我在将 VMware vSphere Infrastructure 从 5.1.0.1123961 升级到 5.1.1474365 时遇到了问题。首先，我遇到了 VMware KB 2046318 中描述的问题（安装 vCenter Single Sign-On 失败，错误 20003 (2046318)）。问题总结如下：升级 SSO 后，SSO 服务器未启动，日志未写入，Windows UAC 不工作（因此，所有依赖于 UAC 的东西也不起作用）。按照 KB 2046318 中的步骤，我能够成功升级 SSO。
这是我目前所做的……
1. 使用“生成 vCenter Single Sign On 备份包”快捷方式创建 SSO 备份。
2.卸载 vCenter SSO
3. 关闭服务器上的所有 VMware 服务（VMware vSphere Server 的虚拟存储控制台、VMware Snapshot Provider、VMware USB 仲裁服务、VMware vCenter Inventory Service、VMware vCenter Orchestrator Configuration、VMware vCenter Orchestrator Server、VMware VirtualCenter Management Webservices、VMware VirtualCenter Server、VMware vSphere Profile-Driven Storage Service、VMware vSphere Update Manager Service、VMware vSphere Update Manager UFA Service）
4.重命名 C:\Program Files\VMware\Infrastructure\jre1 目录
5.以管理员身份运行 autorun.exe
6. 在恢复模式下在服务器上安装 Single Sign。VMware KB 2034928（备份和恢复 vCenter Single Sign-On (SSO) 5.1 配置 (2034928)）对此进行了描述。在安装过程中选择：“从备份中恢复已安装的 vCenter Single Sign On 实例”安装成功。
我注意到的是，查看https://vcenter.domain:7444/lookupservice/sdk。我收到 Tomcat HTTP 状态 404 错误（请求的资源不可用）。在正在运行的 SSO webservice 上，我看到 XML soap webservice 状态。
由于 Web 服务不可用，我无法安装/升级库存服务。lookupserver.log 告诉我数据库连接存在问题。但我被困在这里……
lookupserver.log 看起来像这样
[2014-06-30 15:27:49,345 DEBUG opID= ContainerBackgroundProcessor[StandardEngine[Catalina]] com.vmware.vim.lookup.impl.DbStorage] Successfully loaded JDBC driver for DB type:Mssql
[2014-06-30 15:27:49,376 DEBUG opID= ContainerBackgroundProcessor[StandardEngine[Catalina]] com.vmware.vim.lookup.impl.DbStorage] DB connection pool created
[2014-06-30 15:27:49,392 DEBUG opID= ContainerBackgroundProcessor[StandardEngine[Catalina]] com.vmware.vim.lookup.impl.DbStorage] Executing SELECT CONFIG_VALUE FROM LS_CONFIGURATION WHERE CONFIG_KEY = ?
[2014-06-30 15:27:49,407 DEBUG opID= ContainerBackgroundProcessor[StandardEngine[Catalina]] com.vmware.vim.lookup.impl.DbStorage] Error executing statement SELECT CONFIG_VALUE FROM LS_CONFIGURATION WHERE CONFIG_KEY = ?
java.sql.SQLException: Invalid object name 'LS_CONFIGURATION'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
ssoadminserver.log 如下所示
ssoAdmin 服务器日志
[2014-06-30 15:26:25,527 INFO opID= localhost-startStop-1 com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Establishing connection with the Castle server - target: LocalJvmAccessTarget
[2014-06-30 15:26:25,746 INFO opID= localhost-startStop-1 com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Connection with Castle server was successfully configured.
[2014-06-30 15:26:26,401 INFO opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.impl.KeepAlive] KeepAlive thread started.
[2014-06-30 15:27:25,676 ERROR opID= pool-3-thread-1 com.vmware.vim.vmomi.server.impl.ValidationStartTask] Failed to start activation validation 1 of 1, failing request
com.rsa.common.SystemException: Unexpected exception