Error 29101. Could Not Connect To Vcenter Single Sign On
Contents |
Determining the Cause of a Lookup Service Error vCenter Single Sign-On installation displays an error referring to the vCenter Server or the vSphere Web Client. Problem
Error 29702 Unable To Configure Log Browser Windows Service
vCenter Server and Web Client installers show the error Could not contact Lookup vm ssoreg log location Service. Please check VM_ssoreg.log.... Cause This problem has several causes, including unsynchronized clocks on the host machines, firewall blocking, and server certificate assertion not verified and thumbprint not matched services that must be started. Solution1Verify that the clocks on the host machines running vCenter Single Sign-On, vCenter Server, and the Web Client are synchronized. 2View the specific log file found in https://kb.vmware.com/kb/2062921 the error message. In the message, system temporary folder refers to %TEMP%. 3Within the log file, search for the following messages. The log file contains output from all installation attempts. Locate the last message that shows Initializing registration provider... Message Cause and solution java.net.ConnectException: Connection timed out: connect The IP address is incorrect, a firewall is blocking access to vCenter Single Sign-On, or vCenter Single https://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.security.doc/GUID-B8D60389-AF95-4368-8AB2-D282CBE0C4A9.html Sign-On is overloaded. Ensure that a firewall is not blocking the vCenter Single Sign-On port (by default 7444) and that the machine on which vCenter Single Sign-On is installed has adequate free CPU, I/O. and RAM capacity. java.net.ConnectException: Connection refused: connect IThe IP address or FQDN is incorrect and the vCenter Single Sign-On has not started or has started within the past minute. Verify that vCenter Single Sign-On is working by checking the status of vCenter Single Sign-On service (Windows) and vmware-sso daemon (Linux). Restart the service. If this does not correct the problem, see the recovery section of the vSphere troubleshooting guide. Unexpected status code: 404. SSO Server failed during initialization Restart vCenter Single Sign-On. If this does not correct the problem, see the Recovery section of the vSphere Troubleshooting Guide. The error shown in the UI begins with Could not connect to vCenter Single Sign-on. You also see the return code SslHandshakeFailed. This is an uncommon error. It indicates that the provided IP address or FQDN that resolves to vCenter Single Sign-On host was not the one used when you installed vCenter Single Sign-On. In %TEMP%\VM_ssoreg.log, find the line that contains t
installed a new vCenter 5.5 server in a environment without a domain and DNS server. During the deployment of vCenter Single Sign On I received this error message: Error 29101 Could not connect to vCenter Single Sign On. Make sure that the Lookup Service URL http://blog.vmpros.nl/tag/vcenter-5/ points correctly to the vCenter Single Sign On instance you installed. If vCenter Sign On is installed with an IP address, make sure the IP address is specified in the URL. Solution: Select: “Use FQDN instead of IP address http://www.derekseaman.com/2013/10/vsphere-5-5-install-pt-11-install-web-client.html to configure vCenter Single Sign-On” sanderdaemsSander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBCMore Posts - Website connect to Follow Me: Categories: VMware Tags: 5, Error, Error 29101, FQDN, Sigle Sign On, URL, vCenter 5, VMware VMware: The operation is not allowed in the current connection state of the host March 22nd, 2012 sanderdaems 5 comments Today I want to install Windows 8 in my test lab, after creating a new virtual machine and power-on the VM I received warning error message: Failed to find a host for powering on the virtual machine. The following faults explain why the could not connect registered host is not compatible The operation is not allowed in the current connection state of the host. Weird, both ESXi 5.0 hosts are powered on, my vCenter VM is running on the same machine which I want to power on the new virtual machine.. also strange is.. there's no CPU (0 MHz) and no Memory usage (0,00 MB) activity at this host, check the screenshot below Double check..: Jup.. there are two running servers at esx01.vmpros.lan Solution: After disconnecting the ESXi host from vCenter and reconnect the host I was able to power on virtual machines, also my CPU/Memory activity is back sanderdaemsSander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBCMore Posts - Website Follow Me: Categories: VMware Tags: Activity, Connection State, Host, Power on, vCenter 5, VMware, vSphere 5 VMware: View–Error 1920. Service VMware View Composer (svid) failed to start January 9th, 2012 sanderdaems 10 comments Today I was installing VMware View in my homelab, after trying to install VMware View Composer 2.7 I received this error message: Error 1920. Service VMware View Composer (svid) failed to start. Verify that you have sufficient privileges to start system services. Solution: After creating a new ODBC connection to my SQL server I still can’t finish the installation, the insta
Client October 15, 2013 by Derek Seaman 18719 Commentshttp%3A%2F%2Fwww.derekseaman.com%2F2013%2F10%2Fvsphere-5-5-install-pt-11-install-web-client.htmlvSphere+5.5+Install+Pt.+11%3A+Install+Web+Client2013-10-15+13%3A14%3A47Derek+Seamanhttp%3A%2F%2Fwww.derekseaman.com%2F%3Fp%3D1871 The web client is the new and strongly preferred mechanism to manage your vSphere environment. In fact, the Windows VI client now comes up with a big warning that it's going the way of the dodo bird when you launch it. I suspect in vSphere 6.0 the Windows VI client as we know it will not exist. Yes, today SRM and parts of VUM still need the Windows client. So we will be installing it later on. Remember the web client is the only way to modify hardware v10 VMs. In this post we will install the web client and replace the SSL certificates with trusted ones, by using the VMware certificate tool. Installation and SSL certificate replacement is straight forward. There is one installation gotcha that I elaborate on below. Getting IE 10 on Windows Server 2012 can be a bit frustrating to get working with the web client, so I'll go over that as well. Blog Series SQL 2012 AlwaysOn Failover Cluster for vCenter vSphere 5.5 Install Pt. 1: Introduction vSphere 5.5 Install Pt. 2: SSO 5.5 Reborn vSphere 5.5 Install Pt. 3: vCenter Upgrade Best Practices and Tips vSphere 5.5 Install Pt. 4: ESXi 5.5 Upgrade Best Practices and Tips vSphere 5.5 Install Pt. 5: SSL Deep Dive vSphere 5.5 Install Pt. 6: SSL Certificate Template vSphere 5.5 Install Pt. 7: Install SSO vSphere 5.5 Install Pt. 8: Online SSL Minting vSphere 5.5 Install Pt. 9: Offline SSL Minting vSphere 5.5 Install Pt. 10: Update SSO Certificate vSphere 5.5 Install Pt. 11: Install Web Client vSphere 5.5 Install Pt. 12: Configure SSO vSphere 5.5 Install Pt. 13: Install Inventory Serv