{"id":682,"date":"2013-12-29T02:12:36","date_gmt":"2013-12-28T18:12:36","guid":{"rendered":"http:\/\/blog.infinity.idv.tw\/index.php\/2013\/12\/29\/vcenter-service-status-and-hardware-status-plugin-errors-in-vsphere-5-1-plug-in-manager-not-working\/"},"modified":"2013-12-29T02:12:36","modified_gmt":"2013-12-28T18:12:36","slug":"vcenter-service-status-and-hardware-status-plugin-errors-in-vsphere-5-1-plug-in-manager-not-working","status":"publish","type":"post","link":"http:\/\/blog.infinity.idv.tw\/?p=682","title":{"rendered":"vCenter Service Status and Hardware Status plugin errors in vSphere 5.1 – Plug-In Manager not working"},"content":{"rendered":"

\u53c3\u8003\u6587\u737b\uff1ahttps:\/\/communities.vmware.com\/thread\/441057<\/a><\/p>\n

\u9032vSphere Client\u7684Plug-In\u6703\u51fa\u73fe\u9019\u6a23\u7684\u932f\u8aa4\u4e26\u7121\u6cd5\u555f\u7528<\/p>\n

=========<\/p>\n

vCenter Service Status<\/p>\n

VMware, Inc.<\/p>\n

5.1<\/p>\n

Disabled<\/p>\n

Displays the health status of <\/p>\n

vCenter services The following error occured while downloading the script plugin from https:\/\/10.10.10.15:8443\/healthui\/scriptConfig.xml: The client could not send a complete request to the server. (\u57fa\u790e\u9023\u63a5\u5df2\u95dc\u9589: \u50b3\u9001\u6642\u767c\u751f\u672a\u9810\u671f\u7684\u932f\u8aa4\u3002)<\/p>\n

=========<\/p>\n

\u89e3\u6c7a\u65b9\u5f0f\uff1a<\/p>\n

1.\u9060\u7aef\u9023\u7dda\u5230vSphere Server(Windows 2008 Server)<\/p>\n

2.\u8907\u88fd\u5099\u4efd\u6b64\u6a94\u6848\u4e00\u4efdC:\\Program Files\\VMware\\Infrastructure\\tomcat\\conf\\server.xml\uff0c\u9632\u932f\u8aa4\u53ef\u6539\u56de\u539f\u8a2d\u5b9a\u3002<\/p>\n

3.\u5c07\u4e0b\u5217\u5b57\u4e32<\/p>\n

<Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP\/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"><\/Connector><\/p>\n

\u6539\u6210\u4e0b\u5217\u5b57\u4e32<\/p>\n

<Connector SSLEnabled="true" acceptCount="100" ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP\/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"><\/Connector><\/p>\n

4.\u91cd\u555fWebManagement \u670d\u52d9(VirtualCenter Management Webservices service)<\/p>\n

5.\u518d\u9032vSphere client\u5f8c\u679c\u7136 <\/p>\n

\"clip_image001[5]\"<\/a><\/p>\n

\"clip_image002[5]\"<\/a><\/p>\n

\"clip_image004[5]\"<\/a><\/p>\n

==================<\/p>\n

\u539f\u6587:<\/p>\n

Let me guess, you are using a proxy or Windows XP?  VMware will tell you its an OS issue and to refer you to http:\/\/support.microsoft.com\/kb\/948963<\/a> .<\/p>\n

My fix was restoring the original Tomcat server config, comparing what changed, and putting it back.  I take no responsibility if this breaks something else, but it fixed my problem (which is exactly the same error you seem to be having — missing hardware status tab \/ 2 errors in the plug-in).<\/p>\n

Backup and edit this file:  C:\\Program Files\\VMware\\Infrastructure\\tomcat\\conf\\server.xml<\/p>\n

Locate this line:<\/p>\n

<Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP\/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"><\/Connector><\/p>\n

Replace it with this:<\/p>\n

<Connector SSLEnabled="true" acceptCount="100" ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP\/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"><\/Connector><\/p>\n

Restart the WebManagement service to take effect.<\/p>\n

I basically restored the missing ciphers (RC4\/SSL\/3DES) that were present in VCenter 5.0.  It’s probably less secure, but it fixes the issue.  To the VM developers who though SSO was a brilliant idea and the QA testers who made 5.1 possible… I really really hate you.<\/p>\n","protected":false},"excerpt":{"rendered":"

\u53c3\u8003\u6587\u737b\uff1ahttps:\/\/communities.vmware.com\/thread\/441057<\/p>\n

\u9032vSphere Client\u7684Plug-In\u6703\u51fa\u73fe\u9019\u6a23\u7684\u932f\u8aa4\u4e26\u7121\u6cd5\u555f\u7528<\/p>\n

=========<\/p>\n

vCenter Service Status<\/p>\n

VMware, Inc.<\/p>\n

5.1<\/p>\n

Disabled<\/p>\n

Displays the health status of <\/p>\n

vCenter services The following error occured while downloading the script plugin from https:\/\/10.10.10.15:8443\/healthui\/scriptConfig.xml: The client could not send a complete request to the server. (\u57fa\u790e\u9023\u63a5\u5df2\u95dc\u9589: \u50b3\u9001\u6642\u767c\u751f\u672a\u9810\u671f\u7684\u932f\u8aa4\u3002)<\/p>\n

=========<\/p>\n

\u89e3\u6c7a\u65b9\u5f0f\uff1a<\/p>\n

1.\u9060\u7aef\u9023\u7dda\u5230vSphere Server(Windows 2008 Server)<\/p>\n

2.\u8907\u88fd\u5099\u4efd\u6b64\u6a94\u6848\u4e00\u4efdC:\\Program Files\\VMware\\Infrastructure\\tomcat\\conf\\server.xml\uff0c\u9632\u932f\u8aa4\u53ef\u6539\u56de\u539f\u8a2d\u5b9a\u3002<\/p>\n

3.\u5c07\u4e0b\u5217\u5b57\u4e32<\/p>\n

<Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[46],"tags":[447],"_links":{"self":[{"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=\/wp\/v2\/posts\/682"}],"collection":[{"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=682"}],"version-history":[{"count":0,"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=\/wp\/v2\/posts\/682\/revisions"}],"wp:attachment":[{"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=682"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=682"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.infinity.idv.tw\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=682"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}