VMware Cloud Community
adolfomenendez
Contributor
Contributor
Jump to solution

After power outage, VMs will not restart and Vsphere Client is unable to be access/manage to re/start VMs on physical server.

After power outage, VMs will not restart and Vsphere Client is unable to be access/manage to re/start VMs on physical server.

Get error message...

[    :startup :W: 1] 2016-06-09 14:41:36.562  Log for vSphere Client Launcher, pid=4532, version=5.0.0, build=build-455964, option=release
[    :QuickInf:W: 6] 2016-06-09 14:42:20.421  Set the dll search path to C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\5.0
[    :QuickInf:W: 6] 2016-06-09 14:42:24.281  Load Shared DLLs: C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\5.0
[    :startup :W: 6] 2016-06-09 14:42:41.406  Log for vSphere Client, pid=4532, version=5.0.0, build=build-455964, option=release, user=root, url = https://192.168.10.200/sdk
[    :ShowExcp:W: 6] 2016-06-09 14:42:42.406  Error: An internal error occurred in the vSphere Client.

Details: The type initializer for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

Contact VMware support if necessary.

System.TypeInitializationException: The type initializer for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

   at VirtualInfrastructure.Utils.ClientsXml.FetchIfClientsXmlExists(String serviceUrl)

   at VirtualInfrastructure.LoginUtils.LoadMatchingVI(String serviceUrl)

   at VirtualInfrastructure.LoginUtils.CreateNewService(String serviceUrl, ClientSpec clientSpec, Boolean waitForTopology, Assembly& viAssembly)

   at VMware.Vim.Client.VimClient.StartUp(Dictionary`2 specMap, String[] arguments, LoginEventHandler handler)

   at VpxClient.UI.InitializeVimClient(Dictionary`2 specMap, String[] arguments)

   at VpxClient.UI.StartUpIfNotMultiVcSecure(Dictionary`2 specMap, SecureString password, String[] arguments, LoginEventHandler handler, String dllPath, List`1 listOfVcUrls)

System.TypeInitializationException: The type initializer for 'VirtualInfrastructure.Utils.TypedXmlSerializer`1' threw an exception.

   at VirtualInfrastructure.Utils.TypedXmlSerializer`1..ctor()

   at VirtualInfrastructure.Utils.ClientsXml..cctor()

System.IO.IOException: The process cannot access the file 'C:\Documents and Settings\XXXXUSERNAMEXXXX\Local Settings\Temp\nyhn4bev.dll' because it is being used by another process.

...

   at System.Xml.Serialization.XmlSerializer..ctor(Type type)

   at VirtualInfrastructure.Utils.TypedXmlSerializer`1..cctor()

   --- End of inner exception stack trace ---

   --- End of inner exception stack trace ---

Reply
0 Kudos
1 Solution

Accepted Solutions
adolfomenendez
Contributor
Contributor
Jump to solution

After numerous unsuccessful attempts trying the Vsphere client to connect, the client finally connected and was able to power on all the VMs. Thanks to Luciano Patrao for looking into it. To all in the community, peace out...

View solution in original post

Reply
0 Kudos
2 Replies
LucianoPatrão
Jump to solution

Hi,

Do you have vCenter?? Or just ESXi hosts??

Because if you have vCenter you should check vCenter services. If not, you need to connect to the ESXi host using vSphere Client.

Can you ssh your ssh hosts??

Because what I look that logs, or errors that seems to be a vSphere Client issue.

Can you provide more information about your environment

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
adolfomenendez
Contributor
Contributor
Jump to solution

After numerous unsuccessful attempts trying the Vsphere client to connect, the client finally connected and was able to power on all the VMs. Thanks to Luciano Patrao for looking into it. To all in the community, peace out...

Reply
0 Kudos