I recently installed a View Connection Server 5 on a clean installation of Windows 2008 R2 and am getting the following Event Viewer error for Active Directory Web Services:
Log Name: Active Directory Web Services
Source: ADWS
Event ID: 1202
Task Category: ADWS Instance Events
Level: Error
Keywords: Classic
User: N/A
Computer: vm-view-server.domain.com
Description: This computer is now hosting the specified directory
instance, but Active Directory Web Services could not service it. Active
Directory Web Services will retry this operation periodically.
Directory Instance: ADAM_VMwareVDMS
Directory Instance LDAP port: 389
Directory Instance SSL port: 636
When I do a fresh install of View Connection Server 4.6, I don't get this error at all. This problem was first noticed on my production View Connection Server 4.6 server after an upgrade to vCenter Server 5. Generally this error is related to the server not having a proper SSL certificate and can't communicate LDAP over SSL (port 636). The AD environment in my facility is also a CA authority, in turn requiring all LDAP communication to use SSL.
I know the production 4.6 server AND the fresh 5 connection servers are getting proper certs from the CA. I can see the certs are installed on the systems and can see them in the CA authority snap-in on the AD server. Also, other SSL communications on the network that use the same CA work fine.
My question is what would cause a fresh install of Windows 2008R2 and View Connection Server 5 to not communicate over SSL, but the same clone of the fresh install of WIndows 2008 R2 and View Connectio nServer 4.6 works perfectly?
This error was first notices when my users got SSL errors when launching the View Client. I built the fresh installations for testing and discovered View Connection Server 5 is having the same issues.
NOTE: This is on an secure network so the firewall has been completely disables on all Windows hosts. The virus scanners were removed for testing as well.
I opened a ticket with VMware but so far no resolution and no explanation. I've pretty much exhausted every link found on Google related to the above error.