I went trough the forums history and the knowledge database.I  try all the effort to

configure the AD connection with the vCenter, but I still got error in the vCenter web client.

The Identity-source was set up ones with AD  and the other time  with LDAP settings. 

Both test was ok , but the domain users or groups didn't come up in the list in non of the cases.

I do not see any problem with  PTR records in the DNS or other DNS config.

Can you give me some idea what is the cause of this error in my environment?

I also configure SQL database.I use the MYDOMAIN\VMuser service account on vCenter.

DB_and _schema_creation_scripts_MSSQL  installed the VCDB and vpxuser on  SQL server 2012  to create the background for the VMware connections.

I 

i saw a vcenter . All account vsphere.local\xxx why all login account like that. Why they arent use ad account ?

Aloha,

I just upgraded to Windows 10 Pro. I am also using vSphere client 5.5.0 Build 1618071.

When managing vm's all is good and right with the world. But when I access

a vm console - either by the tab or opening a stand-alone console window the mouse

becomes very erratic on the vm desktop. Movement is unpredictable. Right clicking

on an icon sometimes opens the proper context sensitive menu. And when I do get

the menu, selecting the desired action is next to impossible.

Has anyone else experienced this and has a solution???

Mahalo,

           Bill

Hi, Quick question please which i cant seem to find a definitive answer for

When Cloning a vApp in the vSphere Client or the vSphere WC it seems to only be enabled when it is powered off.

Reading the vSphere VM admin guide it doesn't list that as a pre-req

Is there a way to clone a vApp while power on?

Cheers

Mike

I am stumped. At first, I was able to at least login to vsphere and do operations. The client would close like every 15 minutes so it got really annoying. Now I am stuck with no launch to vsphere. I must log into each host individually. ESXi hosts without a vsphere is so limited. Please advise.

Here is the /var/log/messages

vsphere-fmrif:~ # tail -f /var/log/messages
May 31 09:50:32  vsphere-fmrif watchdog-vpxd: [4773] Begin '/usr/sbin/vpxd', min-uptime =  30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file =  ''
May 31 09:50:32 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:50:34 vsphere-fmrif kernel: [   59.780777] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:50:40 vsphere-fmrif sshd[4944]: Accepted password for root from 128.231.212.117 port 51160 ssh2
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 12 seconds (quick failure 1) 134
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:45 vsphere-fmrif kernel: [   70.438974] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 2) 134
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:52 vsphere-fmrif kernel: [   77.370397] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 3) 134
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:58 vsphere-fmrif kernel: [   83.923261] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 4) 134
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:51:06 vsphere-fmrif kernel: [   91.720959] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:51:12 vsphere-fmrif auditd[3012]: Audit daemon rotating log files
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 8 seconds (quick failure 5) 134
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 6 seconds (quick failure 6) 134
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached

/var/log/warn

May 31 02:40:23 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:41:26 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:42:28 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:43:31 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:44:33 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:45:36 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:46:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:47:41 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:48:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:49:46 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:50:49 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:51:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:52:54 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:53:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:54:59 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:56:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:57:04 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:58:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:59:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:00:12 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:01:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:01:52 vsphere-fmrif portmap[25177]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:01:52 vsphere-fmrif portmap[25178]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:01:53 vsphere-fmrif portmap[25179]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:02:17 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:03:07 vsphere-fmrif portmap[25275]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:03:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:04:04 vsphere-fmrif portmap[25358]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:04:19 vsphere-fmrif portmap[25368]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:04:22 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:05:25 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:06:01 vsphere-fmrif portmap[25531]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:06:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:06:31 vsphere-fmrif portmap[25603]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:07:00 vsphere-fmrif portmap[25618]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:07:30 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:08:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:09:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:10:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:11:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:12:20 vsphere-fmrif portmap[26072]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:12:43 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:12:54 vsphere-fmrif portmap[26144]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:13:45 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:13:48 vsphere-fmrif portmap[26227]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:14:17 vsphere-fmrif portmap[26242]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:14:48 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:15:09 vsphere-fmrif portmap[26348]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:17 vsphere-fmrif portmap[26354]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:16:03 vsphere-fmrif portmap[26435]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:16:53 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:16:53 vsphere-fmrif portmap[26472]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:16:59 vsphere-fmrif portmap[26519]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:17:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:18:30 vsphere-fmrif portmap[26621]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:18:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:20:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:21:03 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:21:37 vsphere-fmrif portmap[26897]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:22:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:23:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:24:11 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:24:22 vsphere-fmrif portmap[27146]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:25:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:26:16 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:26:40 vsphere-fmrif portmap[27330]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:27:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:28:21 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:29:24 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:30:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:31:29 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:32:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:33:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:34:37 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:35:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1

/var/log/vmware/vpx/vpxd.log

 

From earlier:

vsphere-fmrif:~ # tail -f -n 100 /var/log/vmware/vpx/vpxd.log

Section for VMware VirtualCenter, pid=25488, version=5.0.0, build=build-455964, option=Release

 

------ In-memory logs start --------

2012-05-31T09:11:29.623-04:00 [7FFFF3B09700 info 'Hooks'] Hooks Initialized

 

------ In-memory logs end   --------

2012-05-31T09:11:29.633-04:00 [7FFFF3B09700 info 'Default'] Initialized channel manager

2012-05-31T09:11:29.641-04:00 [7FFFF3B09700 info 'Default'] Current working directory: /storage/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Log path: /var/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Initializing SSL

2012-05-31T09:11:29.645-04:00  [7FFFF3B09700 info 'Default'] Vmacore::InitSSL: doVersionCheck = true,  handshakeTimeoutUs = 120000000

2012-05-31T09:11:29.646-04:00 [7FFFF3B09700 info 'Default'] Changed working directory to /var/log/vmware/vpx

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Starting VMware VirtualCenter 5.0.0 build-455964

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Log directory: /var/log/vmware/vpx.

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] Account name: root

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:835] Calling: InfoDeclSchema(gDB)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'Default'] [Init:837] Calling:  VpxCallbackDesc::Init(MakeFunctor(this,  &ServerApp::RequestShutdown))

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:838] Calling: VpxCryptInit()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:839] Calling: VpxLRO::Init()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:840] Calling: VpxLroList::Init(ltud)

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 640 max LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved internal LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved blocker LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved short LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 8 reserved long LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 60-second minimum completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 200 maximum completed tasks

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second unregistered task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:841] Calling: VpxdCharacterizeThreadpool(ltud)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'ThreadPool'] [SetConfig] Thread info: IoMin: 2,  IoMax: 1990, TaskMin: 59, TaskMax: 1990, Max Thread: 3980, Keepalive:  61, thread kill: 600, max fds: -1

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:842] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )

2012-05-31T09:11:29.668-04:00  [7FFFF3B09700 info 'Default'] [Init:843] Calling:  VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)

2012-05-31T09:11:29.668-04:00 [7FFFF3B09700 info 'Default'] Registry Item DB 5 value is ''

2012-05-31T09:11:32.078-04:00  [7FFFF3B09700 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB]  Loaded schema and index information from DB

2012-05-31T09:11:32.099-04:00 [7FFFF3B09700 info 'Default'] [Init:844] Calling: VpxdDbSchemaHash::CheckSchema()

2012-05-31T09:11:32.100-04:00  [7FFFF3B09700 info 'Default'] [VpxdDbSchemaHash::CheckSchema]: schema  file: /usr/lib/vmware-vpx/VCDB_db2.sql

2012-05-31T09:11:32.104-04:00 [7FFFF3B09700 info 'Default'] [Init:845] Calling: VpxdDbMonitoring::Init()

2012-05-31T09:11:32.120-04:00 [7FFFF3B09700 info 'Default'] [Init:848] Calling: VpxdLdap::Init()

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Checking service ldap for running

2012-05-31T09:11:32.179-04:00 [7FFFF3B09700 info 'Default'] [Init:849] Calling: VpxResultFilter::Init()

2012-05-31T09:11:32.179-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:853] Calling: VpxdLock::Init(gDB)

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:854] Calling: VpxdMoLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:855] Calling: VpxdStateLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:856] Calling: VpxdMoDataTable::Init()

2012-05-31T09:11:32.184-04:00  [7FFFF3B09700 info 'Default'] [Init:858] Calling:  VpxdHeartbeat::Init(MakeFunctor(this, &ServerApp::RequestShutdown))

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:859] Calling: VpxdHostCnx::Init(gDB)

2012-05-31T09:11:32.189-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Pre-loading symbols...

2012-05-31T09:11:32.190-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Done pre-loading symbols.

2012-05-31T09:11:32.196-04:00 [7FFFF3B09700 info 'Default'] [Init:861] Calling: VpxdVmomi::Init()

2012-05-31T09:11:32.198-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.200-04:00 [7FFFF3B09700 info 'Default'] [Init:862] Calling: QueryServiceProviderHelper::Init()

2012-05-31T09:11:32.201-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Initializing QueryServiceProviderHelperImpl

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Starting with generation number: 5230290

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'Default'] [Init:863] Calling: ServiceDirectory_Init()

2012-05-31T09:11:32.240-04:00  [7FFFF3B09700 info 'Default'] [ServiceDirectory] Local instance UUID:  DB25B17D-3703-4779-BAFB-845B64AC33AA

2012-05-31T09:11:32.245-04:00 [7FFFF3B09700 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 2578 ms

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] [VpxdMain] Failed to initialize: Name or service not known

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 info 'Default'] Wrote uptime information

2012-05-31T09:12:32.701-04:00 [7FFFF3B09700 info 'Default'] Forcing shutdown of VMware VirtualCenter now

and the process itself

vsphere-fmrif:~ # service vmware-vpxd status
vmware-vpxd is stopped
tomcat is stopped
vsphere-fmrif:~ # service vmware-vpxd start
Waiting for embedded DB2 database to startup: .success
Cleaning session lock table: success
Verifying EULA acceptance: success
Shutting down ldap-server..done
Starting ldap-server..done
Starting vmware-vpxd: success
Waiting for vpxd to initialize: ....failed

Hello Guys,

It's a brand new server with Windows 2008 R2 installed from scratch with all updates.  vCenter Single Sign-On, Web Client, and Inventory Service gets installed with no issues but during the installation of vCenter Server, it gives and error with the following message:

The wizard was interrupted before vmware vcenter could be completely installed. Refer to the log files vim-vci-msi.log.  I have also attached the log file it refers to.  I have already tried KB article 2013922 http://goo.gl/tTjBMQ but no change. I don't see anything obvious that could cause the installation to fail.  Thanks for your help.

I'm trying to add an "Active Directory as an LDAP server" Identity Source on our 5.5 vcsa and keep receiving the following message even though there's no Identity Source listed in Administration->Single Sign-On->Configuration->Identity Sources

"Type or value exists"

2016-02-02 13:50:15,284 WARN   [LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.LinuxLdapClientLibrar

y, error code: 20

2016-02-02 13:50:15,284 ERROR  [IdentityManager] Failed to add identity provider for tenant [vsphere.local]

2016-02-02 13:50:15,284 ERROR  [ServerUtils] Exception 'com.vmware.identity.interop.ldap.AttributeOrValueExistsLdapException: Type or v

alue exists

LDAP error [code: 20]'

com.vmware.identity.interop.ldap.AttributeOrValueExistsLdapException: Type or value exists

LDAP error [code: 20]

        at com.vmware.identity.interop.ldap.LdapErrorChecker$20.RaiseLdapError(LdapErrorChecker.java:298)

Testing the LDAP settings are successful and I'm using the same procedure that worked for adding SSO to another vcsa.

Is there a CLI way to check/remove SSO Identity Sources that don't show on the Web GUI?

Hello everyone,

I have an open ticket with PSS about this but while I wait for them to investigate may get an answer here.

The problem is that when I click on a cluster in web client, I am able to see a list of hosts but as soon as I click on a host to manage it, the host disappears. I have to refresh the page from cluster view to get it back. We have done an inventory database reset with no luck. I also tried with different browsers and users and nothing improved.

Has anyone else experienced this? I am running appliance v6 u1b

Thank you

FYI,

we have a training setup where we run plenty of VCSAs for labs, and it happened the other day that the storage decided to go south.

Not bad, just in the midle of a course

When I was trying to restart everything, several of the VCSAs did complain about disks not having been cleanly unmounted, and forced me into single mode to do file system checks. That's where fun starts.

The root account now has the new VCSA shell tied to it, and it won't run in single user mode because some SO (shared object library aka DLL) was not available.

I had to trick grub into running /bin/sh to get access. Then LVM would not like the state of things, so ended up changing root's shell, rebooting into single user, fsck, then back to normal.

Not nice to discover in a real (i.e. production) DC.

-Carlos

I'm not sure if this is a VMware related question or if it would be better suited for a Microsoft or Security forum.

I managed to successfully install the Root Self-Signed certificate via GPO and now when you go to https://<fqnd> there are no warnings regarding the certificate. Since we've had many iterations of vCenter installed in our organization (and thus system names have changed), I'd like to have an internal CNAME setup that would always be vcenter.whatever.com. That way we could change the name of the server and not have to repoint everyone to the new location. The problem I encountered is, the root self-signed cert doesn't get recognized or applied when you go to the CNAME, only the actual FQDN.

I don't quite understand certificates yet but I'm guessing you need to assign additional addresses to be trusted by this cert somewhere?

Thanks,

. When I try to login to the vCenter Server Appliance as administrator@vsphere.local the interface accepts my credentials and then just keeps loading and reloading the vmware logo over and over.  It looks like it’s going to work and take me in, but never does.  I can login as root with no problems, however.  Any thoughts?

Hi,

I got question regarding "side-by-side" upgrade and/or migration from Windows Server 2008 R2 VM with vCenter Server 5.5 with SQL Express and Update Manager to new fresh Windows Server 2012 R2 VM that will act as vCenter Server 6.0.

How do I perform this upgrade?

Please keep in mind that I'm working with vDS all over the hosts, so "workarounds" like that are problem to me: https://www.reddit.com/r/vmware/comments/3ro29j/side_by_side_upgrade_of_vcenter_of_55_to_6/

Thanks!

In vCenter 6.0 with Platform Services Controller 6.0, I realize that the new "Enhanced Linked Mode" is enabled by default when you join a 2nd PSC/SSO node to an existing PSC/SSO domain.  This is great when vCenter Standard Edition is used at both sites in a multisite setup.  However, vCenter Essentials does not support Enhanced Linked Mode per VMware documentation:

"Enhanced Linked Mode requires the vCenter Server Standard licensing level, and is not supported with vCenter Server Foundation or vCenter Server Essentials."

My question is:  In the case of the Primary Site running vCenter Standard, and the DR Site running vCenter Essentials, each with their own External Platform Services Controller, does VMware support joining the two Platform Services Controllers together into a single SSO domain?  Or must they each be completely isolated into their own separate SSO domains?  The reason I ask is that using products like vSphere Replication and SRM are much easier when both sites are joined to the same SSO domain (fewer pop-ups asking for credentials).  Also, it would be nice to be able to set up "multisite" SSO in advanced, so the customer can seamlessly upgrade from vCenter Essentials to vCenter Standard in the future with just a license key swap (rather than rip and replace the PSC nodes and re-point vCenter).  However, since VMware does not support Enhanced Linked Mode with vCenter Essentials, and Enhanced Linked Mode is enabled automatically when two PSC nodes join the same SSO domain, I suspect it is not supported to do this.  Does anyone know the "official" answer on this?

Bill

I have two 5.5 vCenters in Linked Mode.  A PROD and a DEV.  I want to upgrade DEV to 6.0u1b.  After the upgrade, can I re-link PROD 5.5 to the DEV 6.0 instance?  This does not seem to be documented anywhere.

Also, the PROD 5.5 environment has a couple ESXi4 servers.  If I link PROD back to DEV, how will vCenter 6.0 treat the ESXi4 systems if they're under a different vCenter?

I have installed VC 6.0 fresh in the os and pointed to the old SQL -VCDB .In the vsphere client i can login but all the host in the cluster showing in disconnected state.

what could be the reason.

Regards

Maniee.

Hello,

I'm trying to import an OVA file and I get the error:

"A vCenter Server resource is missing or invalid.  Either the resource was modified while the operating system was running or the server is experiencing a general problem"

This OVA file is from Cisco, it's called Prime.  I had to install another OVA file from Cisco just now and that was fine.

Is it a resourse issue on the reource pool, not sure where to look.

Thanks

All,

Learning vSphere from scratch, to do some dev against the vSphere Server. 

Just trying to get the samples to build and run. They build without any errors or warnings on VS2013 (upgraded to .Net4) and the simpleclient can connect to ESXi server with the -ssodisable option, but when I run any of them that try to get a token from the SSO, the code exceptions out with an error

Acquiring Bearer token

System.Web.Services.Protocols.SoapException: Unsupported nested context '{http://schemas.xmlsoap.org/ws/2004/08/addressing}Address'

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response,

Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at STSService.Issue(RequestSecurityTokenType RequestSecurityToken)

   at AcquireBearerTokenByUserCredentialSample.AcquireBearerTokenByUserCredential.GetToken(String[] args) in c:\Users\<snip>\Documents\SDK\vSphereSDK\ssoclient\dotnet\cs\samples\AcquireBearerTokenByUserCredentialSample\AcquireBearerTokenByUserCredential.cs:line 151

Has anyone come across this error before?

Searching for this error gets me no results at all! I'm not sure what it even relates to, is it an XML error (its well formed I've checked), a VMWare error or a web service error, from TomCat? Something to do with the certificates perhaps? No concept of a 'context' in XML, unless its referring to a namespace? 

I've created two set ups of vSphere 5.5.  One on the corporate VM system and one on my departments XenServer, both suffer the same problem. Been concentrating on my XenServer install due to corporate firewall issues on the corporate VM system.  Both systems have separate vSphere Servers, with the rest of the servers (SSO, Web Client etc) grouped together on one machine, both are connected to the corporate domain.  I've enabled HTTP on the vSphere server so I can see the message transfers more easily and both HTTPS and HTTP get the same error.   There are two ESXi servers. One is 5.1 and the other is 5.5.  There are PTR records in the DNS and a reverse look up works just fine, so I believer there is a reverse look up zone.

I do have some exceptions in my SSO log, not sure they are related.  I think there is a KB to sort this problem, include the SSO log.  There are a lot of logs, not sure which ones are relevant to the problem.

2014-10-08 18:06:58,132 ERROR  [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: Group [VCOAdministrators] could not be found for tenant [vsphere.local]'

com.vmware.identity.idm.InvalidPrincipalException: Group [VCOAdministrators] could not be found for tenant [vsphere.local]

    at com.vmware.identity.idm.server.IdentityManager.findGroup(IdentityManager.java:3178)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)

    at sun.rmi.transport.Transport$1.run(Unknown Source)

    at sun.rmi.transport.Transport$1.run(Unknown Source)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.Transport.serviceCall(Unknown Source)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

I've attached the whole log. 

I have migrated around 40 virtual machines from one virtual center to new virtual center along esxi host.

now i am having a duplicate MAC address problem. some times my old vcenter takes a MAC address from a new vcenter.

how this can happen and how to stop it.

any other way instead of changing the MAC address of virtual machines attached with my new virtual center.

Thanks

After I upgraded my VCSA 6.0 to 6.0u1, I can't login to the vSphere Web Client. 

How to upgrade from VCSA 5.x & 6.x to VCSA 6.0 Update 1? | virtuallyGhetto

Adobe Flash clock animation spins for a little while, then it give the error in the attached screenshot. "An internal error has occurred - Index '0' specified is out of bounds." Happens in IE10 and Chrome.

It is a standalone PSC and I can login to the https://<vcsa>:5480 appliance management and it looks healthy. I can deploy a new VCSA from scratch, but it would be nice if I could fix it.

Any suggestions would be appreciated!

I'm attempting to either install or upgrade a vCenter Server appliance to version 6.

I've tried installing it from scratch on an ESXi 6 host.

I've tried installing it from scratch on an ESXi 5.5 host.

I've tried upgrading an existing appliance running VSA 5.5.0.30200 Build 3255668.

The two ISO images I've mounted to run the install process with:

VMware-VCSA-all-6.0.0-3040890.iso

VMware-VCSA-all-6.0.0-2800571.iso

I've tried turning off my anti-virus program and the built-in Windows 7 firewall on my computer.

I've tried running the installation from a VM on the same subnet as the host server.

I've tried IE11, Fire Fox 43 and Firefox 44

In all cases, the progress indicator for authenticating to the host server shows "validating" for 3-4 minutes before showing a "Connection timed out" message.

One of the recent discussions on this tracked their issue to NTP settings on the VCSA:

https://communities.vmware.com/message/2498305#2498305

My NTP server is DNS-resolved and has a PTR entry

I'm at a loss as to what my next steps should be.

Is there a log on the host server that would show the authentication attempts by the install/upgrade program?