If you made changes to your installed vSphere 6.5 vCenter on Windows at C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\plugin-packages\ you may have messed up the setup, I can't help you more on this without seeing the while virgo log. The important thing is that you should not touch any existing folder in \plugin-packages. The proper way to install a plugin is through a vCenter extension as described in the SDK doc.
>The proper way to install a plugin is through a vCenter extension as described in the SDK doc.
The next version of our plug-in will use the proper way.But now,we need to use the copying ways.....
If I delete the logbrowser folder,the vsphere web client will work well....
please tell me if you placed the plugin-package.xml.unused in purpose...
The errors I see in your log are not related to logbrowser. Are you sure that just removing that directory solves your problem?
FYI, we disabled the logbrowser plugin in 6.5 GA but left the package there in case someone asks to use it (you just need to rename plugin-package.xml.unused to plugin-package.xml)
When the plugin-package file name is incorrect Virgo reports an error and skips the plugin, so the logbrowser bundle is never deployed in this case.