#Vmware vsphere 6.5 appliance error 500 windows#

This was repeated every 6 hours at 1:01 am, 7:01 am, 1:01pm, 7:01pm each day on both vcenter server hosts. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

The transaction log for database 'VIM_VCDB' is full.

#Vmware vsphere 6.5 appliance error 500 windows#

The 4GB datasize limit of this edition should not be a real limit for our usecases.Дў of them started showing the following 'transaction log'-full messages in the windows eventlog after having upgraded to vsphere 4.1 U2. They all are deployed using the MS SQL 2005 express-edition supplied with the vcenter server installer. Two of them running since 2 years now, without any problems. We have three different Vsphere 4.1 Essential Environments with 120 VMs on 3 vm-hosts each. The information to (really) get rid of the well known error message is allready available online but scattered over different places. Mybe someon else has some ideas what to check next.ДЄfter having struggled to solve the reason for above error-message over the past weeks, i want to share my experience and the solution. However changing that entry does not solve the problem because after a short period this entry is replaced automagically by ? - that's the question. We also found the nf file of SSO which still references the old DC by the following entry: Also all other AD dependent services like Exchange, SharePoint, DFS run without issue and do not indicate any problems.

Additionally we checked DNS by hand to ensure that no SRV or any other records are present which reference the old DC. We checked health of AD by running DCDIAG and BPA both not seeing any problems.

Taking a look at the imsTrace.log file of SSOServer we see the following line:Д¬aused by: : Unable to create managed connection :3268ДЄs we can see SSO still tries to contact the old dc now beeing a simple member server instead of the new one - the question is why? Instead of hijacking other one's thread having the same problem I decided to start a new thread, so sorry for double posting.ДЄfter promoting a new DC and demoting the old one we have the problem that VCenter 5.1a no longer starts.