Troubleshooting Web Builder

This section provides tips for troubleshooting problems you may encounter with Web Builder.


Host cannot connect when you attempt to run a browser-based Web application

Host Integrator Servers in the Development Kit can run only five concurrent host sessions. If you don't use the Disconnect button to close a Web application connected to a host session and just close the browser, the session will persist its connection to the host from the Host Integrator Server and you can run out of available sessions. To close a session that is persisting its connection to the host, follow these steps:

  1. From the Administrative WebStation, go to the server status page for the Host Integrator Server that the Web application used for its host session by clicking Server > [name of server] > Server Status > Active Sessions.
  2. Click the session you want to close and click Close.
  3. Repeat step 2 for each session you want to close.

Partial screens are received from the host

If the Web application displays incomplete screens, use the Synchronization Properties tab to modify these settings that define how long Web Builder waits before displaying a new host screen:


Changing the default Host Integrator Web Server port number

By default, the Web Builder assumes that the Host Integrator Web Server is listening on port 8081. This port is known to be used by Network Associates' McAfee software (ePolicy Orchestrator "Agent Wake-Up Call" service). You must change either VHI or the McAfee product's configuration to avoid a port conflict.

To change this value, follow these steps:

  1. Open the file in the <VHI install folder>\lib\webbuilder\common folder, and change this line to match the port number used by your Host Integrator Web Server: servletcontainerport=8081
  2. Open the server configuration file, server.xml, found in the <VHI install folder>\tomcat\conf folder, locate the following lines, and change the "port=" line to the port you are using:

    <!-- Define a non-SSL HTTP/1.1 Connector on port 8081 -->
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
    port="8081" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" connectionTimeout="60000"/>

    Note: You only need to change the first instance of port="8081" in server.xml. It's not necessary to change the second instance for proxy.

  3. Stop and restart the server.


Data missing in the Web Builder log file

A log file is generated whenever Web Builder generates a project. When building Java projects, the Java compiler sends information to the log file on the first build, but not on any subsequent builds. Therefore, to generate output from the Java compiler, close and restart Web Builder, then rebuild the Java project.


HTML Markup Characters

Displaying data containing HTML markup characters may have varying results depending on the type of Web application you build and the browser used to display the application. Generally, Web applications convert HTML markup characters correctly, but terminal screen layout Web applications display the characters directly to the screen.

Here are two examples where HTML markup character issues may occur when building terminal screen layout Web applications:


.NET Web Services "Page Not Found" Errors

If you run the .NET Web service client (Microsoft's automatic Web-based client), and enter some data that causes Verastream Host Integrator to throw an exception, the browser displays an HTTP 500 - Internal server error - "The page cannot be displayed," rather than returning the exception. This is caused by Internet Explorer hiding the real error message. To see the exception error message:

  1. Open Internet Explorer and click Tools > Internet Options.
  2. Click the Advanced tab.
  3. In the Browser section, clear the Show friendly HTTP error messages check box.

Running Web Builder .NET Web Service opens Visual Studio .asmx file instead of opening a browser

If you installed or updated IIS after installing the .NET framework, then IIS will not have the correct configuration to serve .NET pages (like .aspx, .asmx, etc).

To address this problem, use the following to set up IIS:


Run this command with the -i switch to install this version of ASP.NET and update scriptmaps at the IIS metabase root and for all scriptmaps below the root. Existing scriptmaps of lower version are upgraded to this version.

Build Fails When Renaming or Deleting Procedures

When you rebuild a .NET or Java Web application, you may encounter an error if you have renamed or deleted procedures in the model. To correct this:

  1. Delete the previously generated source files that reference the old procedure name.
    • In Java Web applications the source files are located in <VHI install dir>\projects\<project name>\webapp.
    • In .NET Web applications the source files are located in <Inetpub>\<project name>.
  2. Rebuild the Web application.

ASP Procedure-Based Application on Windows Server 2003 and Windows XP Pro x64

If you create an ASP procedure-based Web application in Web Builder, you will need to make a configuration change in IIS Manager. Otherwise, these Web applications will not work when the ASP page is called.

This link provides complete details:

When you request dynamic content such as an Active Server Pages (ASP) page, an ASP.NET page, an Internet Services API (ISAPI) application, or a Common Gateway Interface (CGI) application on a Microsoft Windows Server 2003 or XP Pro x64 server that is running Internet Information Services (IIS) 6.0, you may receive one of the following error messages:

HTTP Error 404 - File Not Found 
HTTP Error 404- File or Directory not found 

By default, when IIS is installed on Windows Server 2003 or XP Pro x64, IIS only serves static content (HTML). To permit IIS to serve dynamic content, the administrator must unlock this content in the Web service extensions node in IIS Manager. To do this, the administrator must either enable a pre-existing Web service extension or add a new Web service extension.

Internet Explorer error messages with .NET 2.0

If you installed IIS after .NET 2.0, you may get the following errors when attempting to build a .NET Web application:

On Win XP, IE error:
You are not authorized to view this page

On Win 2003 Server, IE error:
Directory Listing Denied
This Virtual Directory does not allow contents to be listed.

To resolve this:

From the Properties page of the Web site Documents tab, check Enable default document and verify that Default.aspx is listed.