NameTracer Pro - Common ASP Sample Page Setup Issues

Setting up ASP Sample pages for Nametracer on recent Windows Operating Systems (namely, Windows 2008, Windows 7, etc).

1. INSTALLING IIS

First thing to do is to check whether or not IIS is installed on the machine.

Information about IIS, downloads and Installation help can be found on the IIS Website. Click Here

2. INSTALLING CLASSIC ASP

Nametracer uses Classic ASP pages rather than ASP.NET, so the next step is to check whether or not classic ASP is installed on the machine.

2.1 Installing Classic ASP on Windows Vista or Windows 7 Client

• Click Start, and then click Control Panel.
• In Control Panel, click Programs and Features, and then click “Turn Windows Features on or off”.
• Expand “Internet Information Services”, then “World Wide Web Services”, then “Application Development Features”.
• Select ASP, and then click OK.  

2.2 Installing Classic ASP on Windows Server 2008 or Windows Server 2008 R2

• Click Start, point to Administrative Tools, and then click Server Manager.
• In the Server Manager Hierarchy pane, expand Roles, and then click Web Server (IIS).
• In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
• On the Select Role Services page of the Add Role Services Wizard, select ASP.

• If the “Add role services” required by ASP dialog box appears, click “Add Required Role Services” – Please note that this page appears only if you have not already installed the ISAPI Extensions role service on your server.

• On the Select Role Services page, click Next.
• On the Confirm Installation Selections page, click Install.
• On the Results page, click Close.

3. CONVERTING & MANAGING NAMETRACER APPLICATION

• Navigate to the Nametracer folder in the IIS Manager.
• Right click and select “Convert to Application”. In the “Add Application” dialog box click on “Select…” button
• From the drop down Application Pool, Select “Classic .Net AppPool” and Click on OK.
• Click OK again

Your NameTracer ASP Sample Pages should now be ready to use. Please continue if you are now getting error messages when performing the search

4. COMMON ERRORS/ISSUES IDENTIFIED

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

4.1. SOAP Toolkit not installed - “Library not registered” or Object required error
The ASP Classic pages rely on the Microsoft SOAP Toolkit. If the MS SOAP Toolkit is not installed, after entering the search information you will get one of the following errors “Automation error Library not registered” or “Object required [2147221982]” will be thrown:

Automation error Library not registered. [-98275] @ IDTrace:CanSearch

OR

Error: Object required [2147221928] @ Microsoft VBScript runtime error

To resolve this you would need to install Microsoft SOAP Toolkit 3.0 from the following location:
http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4088-9753-86F052EC8450&displaylang=en

Once installed, navigate to the Microsoft SOAP Toolkit Version 3 program from your Start Menu (under Programs) and Click on WSDL Generator. You should expect to see a Welcome WSDL generator page as shown in the figure below:

If you are using recent versions of Windows operating systems (such as 2008, Win 7 or higher) you might get dependencies error along the following lines:  

This is commonly seen because SOAP Toolkit has not registered the following .ocx files (mscomctl.ocx, mscomct2.ocx, comdlg32.ocx) as they may be missing from either C:\Windows\System32 or C:\Windows\SysWOW64 folders.
To overcome this issue, download the 3 .ocx files (just type in Google) and copy them to C:\Windows\System32 and C:\Windows\SysWOW64 folders.

Next, you need now unregister and register these files so that they can be picked up by the WSDL Generator:

To unregister:

32bit Machine: start > run > regsvr32 -u <nameof.ocx>

64bit Machine: start > run > regsvr32 -u <nameof.ocx>
& start > run > regsvr32 -u <C:\Windows\SysWOW64\nameof.ocx>

To register:
32bit Machine: start > run > regsvr32 <nameof.ocx>

64bit Machine: start > run > regsvr32 <nameof.ocx>
& start > run > regsvr32 <C:\Windows\SysWOW64\nameof.ocx>

4.2 IIS User - Permissions error on Sample Pages
Sometimes you might get Permissions Error. This is very common when using ASP Classic Sample pages through IIS. To overcome this issue, follow the following steps:
• Open IIS Admin and browse to the ASP sample pages directory:

• Right click on the Nametracer ASP directory icon and select “Properties”. Select the Directory Security tab in the ASP properties dialog box, and click the “Edit” button in the “Anonymous access and authentication control” frame (as shown in the figure below):

• An “Authentication Methods” dialog will be shown. Using the “Browse” button you need to add the IUSR_<MACHINENAME> user, and check the “Allow IIS to control password” , as shown below:

This should resolve the permission issue.

4.3 “IDTrace must be successfully initialised” error - Setting the Server Address
Sometimes if the Server address or port has been changed in the ini files but not in the constants.asp page, then you may see an error message along the following lines:

This error message can also be generated if the Server has stopped and/or not has been started. To resolve this error, check the constants.asp file in the ASP Sample code installation directory and ensure that the server details are correct in CONTROL_WSDL_URN.

If you are still having issues please also read the following document  -"Common Issues with ASP Classic" Click Here