This post is regarding the failure to log in to the IVS Client, as the IVS Client version was inconsistent with the VCN server version. Please see how to tackle this below.
Problem description
A customer failed to log in to the IVS Client, as the IVS Client version was inconsistent with the VCN server version.
Problem analysis
The VCN server version is V001R002, but the IVS Client version was V001R003. So the system automatically directed to the matched version installation. However, it failed due to certain OCX issue.
Root cause
The IVS Client version was inconsistent with the server version.
Solution description
Downloaded the IVS Client installation software from the VCN server.
Successfully installed the IVS Client and logged in with a VMU float IP.
