This issue occurs after you upgrade an ESX Server 2.x or 3.x system to ESX Server 3.5 Update 1, or after you perform a new installation of Update 1.