NameTracer Pro - Common Issues with ASP Classic

Document type: Tech doc  
Associated product(s): Product name: NameTracer Version: 5.0 + Implementation: Web APIOS: Windows
Views: 179  |  Created: Last yearLast updated: 9 weeks ago
Countries: United Kingdom United Kingdom 

Summary

Below are some common issues that may be encountered when setting up the ASP Classic sample pages:

1. SOAP Toolkit not installed - “Library not registered” error

The ASP Classic pages rely on the Microsoft SOAP Toolkit. If the MS SOAP Toolkit is not installed, after entering the search information an error “Automation error Library not Registered” will be thrown:

Solution

Installing the Microsoft SOAP Toolkit will resolve the error:

http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4088-9753-86F052EC8450&displaylang=en

2. IIS User - Permissions error on Sample Pages

When serving the ASP Classic sample pages through IIS, the Internet User Guest account needs to have permissions on the ASP sample page directory. Failing to set permissions will result in a permissions error, or a browser logon popup dialogue

Solution

Set the IUSR to have permission on the directory containing the ASP sample pages:

1) Open IIS Admin and browse to the ASP sample pages directory:

2) Right click on the ASP directory icon and select “Properties”. In the ASP properties dialogue go to the “Directory Security” tab, and hit “Edit” in the “Anonymous access and authentication control” panel:

3) This should result in an “Authentication Methods” dialogue shown below. Using the “Browse” button you need to add the IUSR_<MACHINENAME> user, and check the “Allow IIS to control password” , as shown below:

3. “IDTrace must be successfully initialised” error - Setting the Server Address

If the Server address or port is changed, the constant used by the ASP sample pages will also need to be updated. If the Server is running on a different port or address, then you may see an error message as follows:

This error message may also be generated if the Server has stopped / has not been started.

Solution

Edit the constants.asp file in the ASP Sample Code installation directory. The constant that points to the Server location is CONTROL_WSDL_URN:

const CONTROL_WSDL_URN = "http://Robinmxp:7500/tracer.wsdl"

You can check the WSDL location is correct by entering the address into your web browser. If it is correct, it will display the WSDL in XML format.


Was this document helpful?

What can we do to improve this information?