In a new 2-tier install of Capital Essentials or VeSys, users are getting a "Could not connect..." popup error when launching a client application. This can happen when the software is installed as a single tier or standalone installation. That means the install set includes both client and server side software. A single tier installation does not accept remote connections. To allow remote client connections you must edit the Manager configuration file and change the connection mode from "local" to "remote".
On the server machine, edit the <install folder>\config\managerprops.xml file.
Find this section:
<!-- CORBA Name Service configuration -->
<iorconnection mode="local" url="file:///${capitalessentials.temp}/ns.ior"/>
Change to:
<!-- CORBA Name Service configuration -->
<iorconnection mode="remote" url="file:///${capitalessentials.temp}/ns.ior"/>
Restart the Capital Manager Essentials Windows service.
On the server machine, edit the <install folder>\config\vesysmanagerprops.xml file.
Find this section:
<!-- CORBA Name Service configuration -->
<iorconnection mode="local" url="file:///${chs.temp}/ns.ior"/>
Change to:
<!-- CORBA Name Service configuration -->
<iorconnection mode="remote" url="file:///${chs.temp}/ns.ior"/>
Restart the VeSys Manager Windows service.
Note: If this error appears in a single-tier installation, try to stop and re-start the Manager Windows service from the Windows Start menu.