Upgrading Network Clients to V12 - manual intervention may be required
|Date:||1 February 2010|
|Product/Release:||Visual LANSA V12 network clients|
|Abstract:||Network client issues due to missing Visual C++ 2008 Redistributable|
|Submitted By:||LANSA Technical Support|
The LANSA online guide states the following:
Network Clients do not need to be upgraded as they will be upgraded automatically through their server upgrade.
A manual Network Client upgrade is not required because once the server is upgraded to V12, the next time you start a network client pointing to this server environment, the required changes are implemented automatically on the network client. However, there are situations where the automatic upgrade of the network client doesn't complete and manual intervention is required. If the IDE is started from the network client and unexpected behaviour is generated, the most likely reason is that the Microsoft Visual C++ 2008 Redistributable is not available on this PC. Examples of unexpected behaviour would be:
- User logged in as partition security office but can't open any objects.
- Open option is grayed out.
- Running system init and an x_run.exe application error is generated or the imports fail.
The following manual task should be performed if unexpected bahaviour is experienced when attempting to start Visual LANSA on a Network Client for the first time after the Network Client Server has been upgraded to Version 12.
- Open Windows Explorer.
- Open the mapped drive to the server machine.
- Open the Tools directory located underneath the server configuration's installed directory. (For example, K:\LANSAV12\Tools, where K: is the mapped drive.
- Run NetworkClientUpgradePrerequisites.exe.
- A Command Window may be displayed while the prerequisites are installed. A message will be displayed when the installation is complete.
Once NetworkClientUpgradePrerequisites has ended, run Visual LANSA on the Network Client again. Visual LANSA will launch and will complete the upgrade of the Network Client.
Note: this problem may also occur if the Microsoft Visual C++ Redistributable is installed on this network client PC but is an older version.
If a new V12 Network Client is being installed on a PC, this manual intervention is not required as the Microsoft Visual C++ 2008 Redistributable is installed during the network client install. An important step as part of the Network client install is mapping the servers directory to a proper mapped drive rather than an UNC path. This is required to avoid potential errors such as host monitor issues or compile failures due to compiler path being the UNC (\\) path to the server.
If you have current Network Clients using UNC paths, the Visual LANSA automatic upgrade will allow you to continue to use these paths. However, it is strongly recommended that you install new Network Clients using a mapped drive.