Knowledge Base

On web server side, there is a new configuration item into the web.config file of the GraphicalData service called “MachineName” which is empty by default. If it is empty, we don’t change the behavior and it works like before, otherwise the local IP in this configuration is used to bind the .net remoting callback port.

Different situations in which you have to modify this file:

• The webservices are installed on a machine with more than one network interface and the communication between webserver and backend server is only possible on one of the interfaces
• Logon and loading of WebVue works but then you never see the start mimic, only the “loading circle of death”
• You have checked that the backend can reach port 8091 on the webserver
  • The command “telnet <ip of webserver> 8091” can be used for the test
• The Log files of GraphicalData are empty

If all of this is true, the MachineName should be set in the web.config file of the GraphicalData webservice.

On backend side, a configuration file can be used to add the machineName (Case sensitive, it si really machineName, lower case m and upper case N). It is called PropertyServer.config and can be found in the BIN directory of PcVue. To add the name or the local IP, it must be modified like that:

How to know if the machineName must also be configured on backend side:

• The backend is installed on a machine with more than one network interface and the communication between backend and the webserver is only possible on one of the interfaces
• Logon and loading of WebVue works but then you never see the start mimic, only the “loading circle of death”

If all of that is true, the machineName should also be set in the PropertyServer.config file found in the BIN directory of PcVue.

Additional information:
The webScheduler should normally also work in these conditions. But if it is not the case then you must check that this line is present in the file web.config of C:\inetpub\SV Website\WebScheduler :

<httpRuntime targetFramework=”4.8″ />