coDiagnostiX Knowledge Base

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Synergy Troubleshooting ======
Frequently asked questions and troubleshooting information

===== General =====

==== Check network ====

  * If a local server is used, check if the host on which the server is installed can be reached by both, the DWOS machine and the coDiagnostiX machine, by using the ping command.
  * Check if ping works with the IP address and the host name.
  * Consider modifying the hosts file (''C:\Windows\System32\drivers\etc'') on all hosts.
  * Try to temporarily disable the firewall.

==== Check if the network stack is running ====

See “How can I use DWOS Synergy locally without being connected to a network” below.

==== Delete coDiagnostiX' Synergy server cache ====

  * Delete the LiveLinkServers.xml file on the coDiagnostiX host (''C:\ProgramData\coDiagnostiX\coDiagnostiX.App'').

==== Check Synergy server configuration ====

  * Check if Dental Wings Synergy Service is running in the Service management
  * Check the Synergy servers’ configuration. Open the configuration UI by starting ''DWSynergySrv.exe'' (''C:\ProgramData\coDiagnostiX\DWSynergySrv'').
  * Check if RabbitMQ service is running.
  * Check if the RabbitMQ web interface is reachable (See Windows Firewall settings below).

===== Step by step instructions =====

==== No receivers are listed when sharing an order in DWOS ====

DWOS is unable to find a RabbitMQ server. See chapter “Local Server”.

  * Check if you are able to connect to the host running the RabbitMQ server.
  * Check firewall settings. See chapter RabbitMQ server installation instructions.
  * Check proper installation of the Synergy Server. See chapter Notes.
  * If the server is on the same machine as DWOS check if you are connected to a network nevertheless.

==== No shared orders are listed in coDiagnostiX ====

  * Share an order from DWOS.
  * Restart coDiagnostiX.
  * See FAQ item No receivers are listed when sharing an order in DWOS
  * Does coDiagnostiX know your DWOS Synergy Server?
  * Check the file LiveLinkServer.xml in coDiagnostiX’ configuration directory for a server that matches your Synergy Servers parameters.
  * If not: DWOS Synergy’s zeroconf implementation uses TCP broadcast messages. If this is not available in your particular network, the server configuration has to be done manually. See chapter “Manual configuration” on page 3.
  * Is the DWOS Synergy Server able to communicate with RabbitMQ?
  * Restart the DWOS Synergy Server service.
  * Run DWSynergySrv.exe and check the configuration GUI.
  * Check firewall settings. See chapter RabbitMQ server installation instructions on page 5.

==== After receiving an implant, DWOS’ implant setup dialog doesn’t show any implants ====

If the implant setup dialog’s 3D view appears to be empty, DWOS’ database is probably corrupted.

==== How can I use DWOS Synergy locally without being connected to a network ====

If the computer was not connected to a network since Windows was booted, most probably communicating over the loopback address (localhost, 127.n.n.n) will not work properly. Hence, Synergy won’t work as well.
Currently, there are two solutions:
  * Connect to a network, at least temporarily. As soon as the machine has been connected to a network, communication will work. Even after the computer has been disconnected again.
  * Install Microsoft’s virtual loopback network adapter and assign an IP address to it. See {{:tech:loopbackadapterhowto.pdf|}} for steps.

==== How can I share a planning from coDiagnostiX ====

Currently, shares can only be placed by DWOS.

==== How can I connect to a share with DWOS ====

Synergy supports connections between DWOS and coDiagnostiX only. It is not possible to connect two instances of DWOS or coDiagnostiX.

==== RabbitMQ server installation instructions ====

Everything below is done automatically by the Synergy Server installer. However, if problems occur this might help solving them.

=== RabbitMQ server installation ===

  - Download erlang installation win64 binary or win32 binary (91.9 MB) and install.
  - Download RabbitMQ server installation rabbitmq-server-3.2.3 (3.6 MB) and install.
  - Open start ‘menu > RabbitMQ > RabbitMQ Command Prompt (sbin dir)’ or Search ‘RabbitMQ…’ and open RabbitMQ Command Prompt (sbin dir).
  - In the command prompt type: ‘rabbitmq-plugins enable rabbitmq_stomp’ and hit enter (enables the stomp plugin, which is required for coDiagnostiX).
  - Optional: hit the up arrow to bring back the last command and change it to ‘rabbitmq-plugins enable rabbitmq_management’ and hit Enter (enables the management plugin, required for web-interface).
  - Check the RabbitMQ service installation and restart it.
    * Open start menu, search for ‘Services’ or ‘Dienste’ and open it.
    * If installed correctly, there will be a service with the name ‘RabbitMQ’ running.
    * Right-click > restart or select and choose restart on the left side.

=== RabbitMQ web-interface ===

The web-interface is available if everything is installed and the management plugin is enabled.
  - Open a browser of your choice.
  - Enter [[http://localhost:15672|'localhost:15672']] in the address bar.
  - Enter the current default login: ‘guest’ password: ‘guest’.

The web-interfaces shows the current traffic, and under queues the specific channels for DWOS and coDiagnostiX can be monitored.

=== Windows Firewall settings ===

If the RabbitMQ server needs to be reached from another PC the corresponding ports need to be opened.
  - open start menu, search for ‘Firewall’ open ‘Windows-Firewall’
  - open ‘Advanced Settings’ or ‘Erweiterte Einstellungen’
  - select ‘Inbound Rules’ or ‘Eingehende Regeln’ on the left
  - click ‘New Rule..’ or ‘Neue Regel...’ on the right side
  - choose ‘Port’ and click ‘Next >’
  - choose ‘TCP’ (should be already) and ‘Specific local ports’
  - or ‘Bestimmte lokale Ports’ and enter the required ports:
    - 61613 (for coDiagnostiX, if its on another PC)
    - 5672 (for DWOS, if its on another PC)
    - 15672 (for the RabbitMQ-server-web-interface, if required from another PC)
  - so you will end up with something like ‘61613, 61615, 5672, 15672’ and click ‘Next >’
  - choose ‘Allow the connection’ or ‘Verbindung zulassen’ and click ‘Next >’
  - select the required Profiles and click ‘Next >’
  - and a name f.e. ‘RabbitMQ’ and you are done

If done correctly, the server will now be reachable from other clients. If port 15672 was added to the rule the web-interface should also be reachable from other PCs ‘<IP-address>:15672’.