FAQs
Why is it necessary to install a Visual C++ Redistributable package?
This package is required for a good behavior of both Web client and Windows client of HOPEX. It contains runtimes that enable to execute C++ component of the HOPEX kernel (mainly .dll files). Microsoft now recommends to install these runtimes through a separate installer package.
How to get the package Visual C++ Redistributable for Visual Studio 2015?
You can download it from Microsoft web site.
Search 'Visual C++ Redistributable for Visual Studio 2015' (offline installer, 32-bit version). The expected file is 'vc_redist.x86.exe'.
If HOPEX is installed, you can also find this package in the following folder:
<HOPEX installation>\Install\vc_dedist
Ex: C:\Program Files (x86)\MEGA\HOPEX V2R1\Install\vc_dedist
It is recommended to run vc_redist.x86.exe as an Administrator.
Why is it necessary to tinstall a Visual C++ Redistributable package?
The offline installer can be found at this address:
If you want to download it from that location, make sure to download the 32 bits' version, file “vc_redist.x86.exe”.
Moreover, once the HOPEX application is installed, you will be able to find it in the folder “<installation folder>\Install\vc_dedist”.
How to track an installation error?
If an installation error persists after a second try and no reason can be found, contact MEGA Technical support. An installshield log can be requested.
To generate such a log, you can use a /levw command line parameter.
Example:
msiexec /package "\\Srv001\Master\HOPEX\DISK1\HOPEX V2R1.msi" /passive /levw "C:\tmp\ScriptInstall.log"
Understanding the logfile generated by this command requires an expertise.
How to disable SMB 2.0?
SMB 2.0 can be disabled on the client side or on the server side.
If the file server is dedicated to HOPEX, it is recommended to disable SMB 2.0 on the server side. See the following web page:
How can I create a HOPEX Environment in RDBMS Storage (Oracle, SQL Server)?
After upgrade of a HOPEX installation from version X to version Y, when a user Z runs HOPEX, the version is version X (and not version Y)!
This is a known issue with Citrix deployment (XenApp). The version of the programs is cached by Citrix. As long as a user has a session that is disconnected, he cannot see the new version.
Ask users to exit with logoff. In Citrix administration console, disconnect inactive users for the application corresponding to HOPEX.