The following symptoms and possible causes are visible to the user of the Conferencing client.
Symptom: The client displays the error Unable to connect to server.
Possible Cause:
The hostname of the XML Router does not resolve properly on the client machine.
Check \Documents and Settings\<user-name>\Application Data\meeting\zon.log (Win32) or ~/.meeting/zon.log (Linux) in the system drive of the client machine for lines containing the text Unable to resolve hostname.
The client concentrator, jadc2s, is not running.
Verify that the jadc2s process is running on all XML Router hosts.
Verify that port 5222 is in LISTEN state.
Look in /var/log/iic/jadc2s.log for more information.
The XML Router, jabberd, is not running.
Verify that the jabberd processes are running on all XML Router hosts.
Verify that a system component port is in LISTEN state.
Look in /var/log/iic/xmlrouter_error.log for more information.
The meeting controller is not running or not connected
Check \Documents and Settings\<user-name>\Application Data\meeting\zon.log (Win32) or ~/.meeting/zon.log (Linux) in the system drive of the client machine for lines containing the text err=-995, msg=Internal Timeout, code=-1000, id=rpc_controllerauth.
If Step A is true, check the meeting controller log files for more information and check the network connectivity between the meeting controller host and the XML Router host.
The address book is not running or not connected
Check \Documents and Settings\<user-name>\Application Data\meeting\zon.log (Win32) or ~/.meeting/zon.log (Linux) in the system drive of the client machine for lines containing the text “err=-995, msg=Internal Timeout, code=-1000, id=rpc_versionck”.
If Step A is true, check that the address book daemon is running. If it is, check the address book log files in /var/log/iic for more information and check the network connectivity between the address book host and the XML Router host.
Symptom: The client displays Contact data fetch failed in the Edit User dialog box status line.
Possible Cause:
The address book is not running or is not connected:
Check \Documents and Settings\<user-name>\Application Data\meeting\zon.log (Win32) or ~/.meeting/zon.log (Linux) in the system drive of the client machine for lines containing the text err=-995, msg=Internal Timeout, code=-1000, id=rpc_getdata23.
If you find this text, check that the address book daemon is running. If it is, check the address book log files for more information and check the network connectivity between the address book host and the XML Router host.