Troubleshooting

NoteThe workarounds described below apply mainly to Windows®.

Application qizxserver fails to configure Qizx XML Server.

This could be a problem of insufficient privileges.
When you run qizxserver, you must have enough privileges to read and write any file or directory belonging to the distribution of Qizx XML Server.
You'll need to have the privileges of an administrator if you want qizxserver to open the server port in Windows built-in firewall or to run Qizx XML Server as a Windows native service.
The cure is generally to re-run qizxserver but this time, with the privileges of an administrator.
On Windows XP, suffice for your user account to be an administrator account.
On Windows Vista and subsequent versions, not only your user account must be an administrator account but also, you need to right click on the icon of qizxserver and pick "Run as Administrator" from Windows popup menu.

Qizx XML Server is up and running, but qizxserver sees it as being stopped (the Stop button is disabled, the Configure and Start buttons are enabled).

Here's what happens: when you choose the server port, a shutdown port is automatically chosen for you. This shutdown port is the first free port nearby the server port. For example, if the server port is 8080, the shutdown port will often be 8079, 8081 or 8082. This shutdown port is probed to determine whether Qizx XML Server is running. This issue occurs when qizxserver picks a free shutdown port and when, once started, Qizx XML Server fails to open it.
First you need to stop Qizx XML Server by hand in order to reconfigure it.
If Qizx XML Server is running as a Windows® native service, stop the service by using Windows Service Administrative Tool. Alternatively execute net stop "qizxserver" using a command prompt.
If Qizx XML Server is running as a normal program, terminate it using the Windows Task Manager.
Now you need to re-run qizxserver in order to reconfigure Qizx XML Server. This time, choose a server port belonging to a very different range. For example, if the first time you have chosen 49152, this time choose 10000.

I can connect to Qizx XML Server from my machine (my machine is the one which is running Qizx XML Server), but my coworkers cannot connect to Qizx XML Server from their machines.

First try to connect using the IP address of the server rather than its host name. That is, specify something like http://192.168.1.96:8080/foo/bar rather than something like http://speedo:8080/foo/bar.
On Windows, the IP address of your machine may be determined as follows: open a command prompt, type ipconfig /all then press Enter. This command prints a lot of information on the console. Look for "IP Address".
On Windows, host names are often resolved to IP addresses using the NetBIOS name resolution rather than using a real DNS. When this is the case, there may be interoperability problems between machines running Windows XP and machines running Windows Vista/7 belonging to the same local network.
If specifying an IP address does not solve the problem, then a firewall running on your machine is almost certainly blocking the port which has been chosen for the server.
On Windows, re-run qizxserver as an administrator, stop Qizx XML Server, reconfigure it, and this time make sure to select option "Yes, do it now".
If you are using a firewall other than Windows built-in one, then you are on your own to open a port in this firewall.

My coworkers can connect to Qizx XML Server from their machines, but this connection is quite slow (takes more than 1 minute to be established).

Try to connect using the IP address of the server rather than its host name. That is, specify something like http://192.168.1.96:8080/foo/bar rather than something like http://speedo:8080/foo/bar.
On Windows, the IP address of your machine may be determined as follows: open a command prompt, type "ipconfig /all" then press Enter. This command prints a lot of information on the console. Look for "IP Address".
If doing this solves the problem, then the culprit is the NetBIOS name resolution which can be quite slow. You may consider switching to a hosts file based resolution or to a real DNS.