VMware Cloud Community
Pixxxx
Contributor
Contributor
Jump to solution

After vSphere client upgraded to 4.1 error received on ESXi 3.5.0 host

Dear all,

I have two hosts:

     a)  Dell PowerEdge 2950 (8 core x 2,659 GHz + 24GB of RAM) hosting "ESXi 3.5.0, 184236"

     b)  Dell PowerEdge R710 (8 core x 2,393 GHz + 12GB of RAM) hosting "ESXi 4.1.0, 348481"

starting from the first connection using vSphere client to the new 4.1 host, I'm receiving a lot of client ClassFactory Exceptions trying to edit Guest machines on the 3.5.0 ESXi host

may be that:

1. the new client is not totally compatible with the old ESXi 3.5.0?

2. I have to restart the management interface of the ESXi 3.5.0?

3. something else?

another question:

3. if I restart management interface or httpd service on the ESXi 3.5.0 host, the Guest machines will be affected by the restart activities?

Thanks in advance

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
idle-jam
Immortal
Immortal
Jump to solution

1) yes it is not compatible, you will still need to use the old vi3 client

2) should not be

3) restarting of management agent will not affect the VM

View solution in original post

0 Kudos
2 Replies
idle-jam
Immortal
Immortal
Jump to solution

1) yes it is not compatible, you will still need to use the old vi3 client

2) should not be

3) restarting of management agent will not affect the VM

0 Kudos
Pixxxx
Contributor
Contributor
Jump to solution

right, the new client is not totally compatible

the old vi3 correctly manage the old ESXi host

thanks

0 Kudos