Pro Web Application Error: Failed To Create an API Instance -4551

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

<< More documents like this


When installing and testing Pro Web software you may come across a -4551 error. This will usually happen when you run the test harness.


The “failed to create an API instance -4551” error means that the initialization of the objects when starting the API was not successful.


There are a number of settings you need to check:

1. Port Settings

You need to ensure that you are using a free port (not being used by any other service) and that both the client and server are using the same port. You can check the settings for the server port by navigating to the installation directory for pro web and locating a file called qawserve.ini (see figure 1).

Figure 1 - screenshot of qawserve.ini file

This file contains the server settings and data and pasting configurations. Open the file and ensure that the port number is correct. The default port number is 2021 but if this is already in use you may need to try a different port.

You will also need to check the port settings on the client side. In the installation directory there is a file called qaworld.ini (see figure 2).

Figure 2 - screenshot of qaworld.ini file

2. QuickAddress Service

The service is required to provide the connection between the server and the client. In Windows, you can view the status of the service by going to Start à Run and type in ‘Services.msc’. This window lists all the services:

Figure 3 - screenshot of local services

Find the Pro Web service you are using and ensure that it is running. N.B. The service needs to be restarted for changes to the configuration/data files to take effect.

To start the service in Unix, navigate to the apps directory for the Pro Web installation and run the executable qaswvd:

$ ./qaswvd&

3. Data Sets

You need to ensure that the data has been installed and is in the correct directory. In Windows, you can check this by going to the Administration Console and then looking at Current Data from the menu on the left. Look at the data in the table and make sure that it is correct and not out of date.

Figure 4 - screenshot of Admin Console - current data view

In Unix, you can use the command-line management utility wvmgmtd:

$ wvmgmtd datalistread current <Server>:<Port>

4. Licence Keys

Next you need to check the licence key has been added. In Windows, open the Configuration Editor and navigate to the licence information. Click on the Licences button which will open the licence manager. Make sure the correct licence has been added in the Licence Manager list box. If you have any expired evaluation licence keys please remove them.

Figure 5 - screenshot of Configuration Editor - Database Information view

In Unix, locate the qalicn.ini and check the licence keys listed in there.

5. Restart service

You need to restart the service when you make any changes to the configuration. In Windows, you can do this by going to Start à Run and type in ‘Services.msc’. Find and highlight the service you want and then right click and select restart.

In Unix, you will need to kill the qaswvd process and then start it again.

Was this document helpful?

What can we do to improve this information?