Duplicate node names in Network Client installs can cause various problems using LANSA
|Product/Release:||Visual LANSA V10.0|
|Abstract:||Duplicate node names in Network Client installs can cause various problems using LANSA|
|Submitted By:||LANSA Technical Support|
In Visual LANSA V10.0, there is a known issue with the Network Client Only installation whereby the client will use the node name of the server machine.
When installing multiple network clients, the end result will be that all network clients will have the same node name.
The symptoms of duplicate Node Names are:
- Unable to start connection in Host Monitor
- LII0136E lock messages when two users try to compile at the same time (even if they are compiling different objects)
- Instability when Object Locking is turned off (IDE may crash unexpectedly with LANSA.EXE error messages).
The fix for this is to manually change the Node Name for each of the Network Clients. This may be specific for each installation, so please contact your support vendor if you have any enquiries on changing the Node Name.
After changing the Node Name, you must ensure that you REFRESH the system definitions (by using Systems Initializations Dialog) on each of the Network Client. This will ensure that the change is registered into the database.