Today I was working on problem related to VMware Update Manager pointing to wrong database and I managed to find the solution to this problem.
In my case SQL server was running on Windows Server 2008 R2 so I had to check 32 bit DSN located in %SystemRoot%\syswow64\odbcad32.exe
Of course DSN was pointing to correct database on correct DB server but VUM was still not working. Also it is important to mention that two days before vCenter Server was migrated from one host to another with vCenter Server version upgrade. I knew previous SQL database names so I knew what I was looking for. On new SQL server I created new databases – the one which was VUM referring to.
I didn’t know how to find root cause but colleague of mine suggested that it must be somewhere in VUM configuration file.
I did small Powershell (grep like) query which pointed me to configuration file.
Get-ChildItem -Filter *.* -Recurse | Select-String DBSTRING
When Powershell query finished I got results where DBSTRING was located. It was vci-integrity.xml file located in VUM installation folder – in my case C:\Program Files (x86)\VMwareInfrastructure\Update Manager.
After changing section in xml and restarting VUM service everthing worked fine.
<dbtype>SQL Server Native Client 10.0</dbtype>
Sadly after spending some time on this I found VMware KB kb.vmware.com/kb/101522.
My experience and skills have been proven by leading vendor certifications like AWS, Alibaba Cloud, VMware, and Microsoft. I contribute to IT community and I received VMware vExpert 2014 - 2017 and VMware vExpert NSX 2017 Award.
My blog wojcieh.net - was voted #43 in Top vBlog 2017 contest!
Do what you love, and you’ll never work another day in your life.
Latest posts by Wojciech Marusiak (see all)
- Top vBlog 2018 is there! - 20 November, 2018
- Zentyal – my new Homelab Swiss Army Knife - 10 October, 2018
- Send VMware backups to the cloud – Altaro Offsite Copies to an Azure Cloud Storage - 18 September, 2018