How to resolve common configuration issues with Client/Server products

Document type: Tech doc  
Associated product(s): Product name: Pro Version: 4.0 + Implementation: API , Standalone
Views: 406  |  Created: 7 years agoLast updated: 7 years ago

<< More documents like this

Summary

A list of all common issues with QAS Client/Server products and how to resolve them.

Problems with TCP/IP Connection

Commonly Encountered QuickAddress TCP/IP Error Messages

Solution

Problems with TCP/IP Connection

One of the most common configuration issues with QAS Client Server products is in making a TCP/IP connection. This can be caused by a number of factors which will be discussed in more detail below, however there are some basic settings that should be verified before these more complex issues are investigated. These are:

Check that the Server daemon is running. This can be verified in a number of ways:

1. When the server starts, a Process ID number is displayed on the screen.

Use the command ps to display process statistics. This command is implemented as follows:

ps –f –l –u<username>

This will list all the users processes and some of the attributes of these process as shown below:

F S USER PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD

40801 S romanur 8858 1 2 61 20 895 1896 1fd67c 17:56:39 pts/1 0:00 ./qanstdp

241801 S romanur 9608 7559 0 60 20 7a9 120 17:52:52 pts/1 0:00 -ksh

200001 R romanur 9883 9608 5 62 20 5ce 132 17:56:46 pts/1 0:00 ps -f -l

The statistics above show the state of the process qanstdp and confirms that the process is running and clocking up processor time. The number 2 under the “C” column indicates the CPU utilisation. The larger the number the more CPU intensive is the process.

2. Ensure that the normal connection between the client and the server is sound. This can be achieved by running other software which is common to both the client and the server. Alternatively the PING command can be used to try connecting to the HOST, where the server resides.

The syntax for using PING is as follows :

ping <hostname>

where hostname is the name of the server you want to connect to.

You should get a similar response to below for a successful connection using PING :

Pinging 150.150.100.240 with 32 bytes of data:

Reply from 150.150.100.240: bytes=32 time=2ms TTL=64

Reply from 150.150.100.240: bytes=32 time=1ms TTL=64

Reply from 150.150.100.240: bytes=32 time=1ms TTL=64

Reply from 150.150.100.240: bytes=32 time=1ms TTL=64

If PING fails then the problem is with the System setting. Possible problems here are that network protocols such as TCP/IP have not been properly installed or there are real network problems between the server and the client. In this instance it may be necessary to have a network analysts trouble-shoot the network.

If PING proves to be successful, it indicates that the network is sound.

3. The next area to examine would be to double check that the Dotted IP numbers in the INI file setting “ServerAddress=” are correct and that the Port number is the same for the server and client. If this fails it may be worth trying to change the port number on the server and the client and then re-starting the QuickAddress Network Server.

Another diagnostic test that one can perform is to verify that the server is running correctly by running telnet. This is done by specifying the port number that the server is running on in the port number text box. If you get “QAS1” appearing on the screen, termed as a handshake, the port number is valid and the server is listening. If the handshake fails then it indicates that there are problems and the server is not listening, consequently there will be no connection.

Some servers may have multiple network cards, thus they will have individual IP addresses and this could sometimes cause a problem. If multiple network cards exist then the ServerAddress setting in the INI file should be edited to read

ServerAddress=Any

If all the above possible solution fixes fail then kernel logging facility can be implemented by including the following lines in the relevant product INI file:

LogTrace=1

LogFile=<filename>

LogErrors=True

4. Another utility which can be used in troubleshooting such connection problems is netstat. This indicates whether a connection is established or not with a particular port number. This is implemented in the command line of Windows /UNIX environments as follows:

netstat –a

Commonly Encountered QAS TCP/IP Error Messages

There are two types of errors which you might encounter when QAS Client/Server Products are running. These are:

1. Errors generated by the Names Server and sent to the Names Client.

2. Errors arising in the network communication between the Names Server and Names Client, thus stopping these programs from initialising or communicating.

(Under Windows NT, the error values returned are positive values, rather than negative)

Error -9291 ("Bad IP number format")

This error occurs if the IP number specified when installing the Network Client is incorrectly formatted. This number should be in 'dotted quad' format - i.e. four numbers separated by dots (for example: 150.150.100.50).

Solution: Correct the formatting in QADDRESS.INI

Amend the ServerAddress= setting in the Client's configuration file to the correct IP number. Alternatively, you can specify a hostname in this setting instead of an IP address.

Error -9293 ("Couldn't listen to TCP/IP socket")

This error probably means that the port you have specified is already in use by another application.

Solution: Check the ServerPort setting

The ServerPort= setting in the Client's configuration file contains the port number which the Server is using to receive requests. Check that this setting corresponds with the ServerPort= setting in the Server's configuration file.

Error -9294 ("Couldn't bind TCP/IP socket (port in use?)")

This error could occur when the Server is started. The system believes that the port specified by the ServerPort configuration setting is unavailable or is already in use.

Such an error may be encountered if a copy of the Server is already running, or if a different program running on the Server machine has already claimed the port that the Names Server is looking for.

Error -9292 ("TCP/IP accept failure")

This error will occur if the connection between Client and Server has not been made. This might be due to a network problem.

Solution: Check the Server is running

Ensure that the QAS Network Server is loaded and running before trying to connect to it. Check that it hasn't crashed and that there are no broken network connections.

Check the Client configuration file

If the Server is running, then ensure that the ServerAddress= setting in the Client configuration file is correct, and that the ServerPort= setting corresponds with the equivalent setting in the Server configuration file.

Error -9296 ("TCP/IP timeout")

This error may occur if data transfer between Server and Client is not completed within the connection timeout period. This might be due to a broken connection or a high volume of network traffic.

Solution: Provide more specific search address information

Large amounts of data are transmitted if search results have many pick list items. If you specify more name and address information, the search will be narrower, meaning less data to return.

 

Error -9297 ("TCP/IP socket error")

This error appears when the Client has difficulty sending to a port, possibly because the Server has crashed or because the user does not have authorisation to use the specified port number.

Solution: Check whether the required port is available

Do you run the Server under UNIX? If so, then unless you are running the Server from an account with root privileges you must use port number 1024 or greater.

If you are a UNIX user, you can investigate "/etc/services" to check if any other service is using the port you've configured. Alternatively, you can use the netstat utility discussed above.

On NT, you can check the SERVICES file or also use netstat.

If the Server is definitely running, check that it hasn't crashed. Check that there are no broken network connections. Most importantly, ensure that the Server's name and port settings in the configuration file have been correctly specified.

 

Error -9298 ("Couldn't open TCP/IP connection")

This error occurs when starting a Client which cannot establish contact with the Server, either because the Server is not running or because the Server address and port number have been incorrectly specified.

 

Solution: Check the status of the server

- If the Server is NOT running:

To prevent this error, you must ensure that the Server is loaded and running before any Client attempts to connect to it.

- If the Server IS running:

Check that the Server hasn't crashed. Check that there are no broken network connections. Most importantly, ensure that the Server's name and port settings in the configuration file have been correctly specified.

 

Error -9299 ("Couldn't create TCP/IP socket")

This error occurs if the TCP/IP port specified is already in use or the user doesn’t have permission to use it.

Solution: Check if the requested port is available

If the Server is running under UNIX, then unless it is running from an account with root privileges, a port number of 1024 or greater must be used.

If you are a UNIX user, you can investigate "/etc/services" to check if any other service is using the port you've configured. Alternatively, you can use the netstat utility discussed above.

 

Error -9300 ("Dataset not present on Server")

This error occurs if a DataPlus data set specified in the Client configuration file is not in the Server configuration file.

 

Solution: Compare Client and Server configuration files

Make sure that the DataPlus data sets specified in the Client's configuration file are also in the Server's configuration file. The Client does not have to use every DataPlus set that is configured on the Server, but a data set must be on the Server before a Client can retrieve information from it.

Error -9301 ("Incorrect Client/Server protocol (old version?)")

This error might occur if the Client and Server have different release numbers (i.e. one has been upgraded and the other has not). In such circumstances it is necessary to contact Experian QAS Technical Support.

Was this document helpful?

What can we do to improve this information?