Discovery of multiple vCenters failing due to "Timeout trying to read from https://IPaddress/sdk" errorIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Run discovery to vCenters failing due to "Timeout trying to read from https://<IP-address>/sdk" error Check the ECC queue payload input that involves the following topics: VMWarevCenterNetworksProbeVMWarevCenterDatastoresProbeVMWarevCenterVMsProbeVMWarevCenterClustersProbe All return: <result error="Timeout trying to read from https://<IP-address>/sdk"> <output/> </result> Release London Cause Customer is using external credentials. The probe times out before credential returns. Resolution Add a parameter "vcenter_timeout" to probe "VMWare - vCenter Datacenters". The default value is 30000 milliseconds (30 seconds). Increase the value to accommodate the timeout. Documentation: vCenter probes and probe parameters