Uniface WRD Configuration Errors

• Possible cause: Page in cache.

  Resolution: Select Ctrl+F5 (Ctrl+Refresh).

• Possible cause: Server Page not (correctly) compiled.

  Resolution: Compile the Server Page and check whether errors occur.

• Possible cause: Server Page not loaded by the Uniface Server.

  Resolution: In the [SETTINGS] section in the Server assignment file, set $TEST_MODE_COMPONENTS.

• Possible cause: Relative paths used in the skeletons (for example, ../css /applic.css) cannot be translated into absolute paths.

  Resolution: Check whether virtual directory specified in WWW publishing service is identical to path specified in WEBAPPURL setting in URD Servlet Alias.

• Possible cause: Non-database fields have an initial value.

  Resolution: Set Is Static property to True.

• Possible cause: Server Page is intended to display one occurrence, but synchronization results in extra occurrence.

  Resolution: Change Database Behavior to Record. For more information, see Data Access .

Bad HTTP request, data size is larger than the maximum allowed size.
Please contact your system administrator.

• Possible cause: the content data size of the request is larger than the value of parameter MAXPOSTDATASIZE.
• Resolution: If the large data size of a request is necessary based on your application logic, adjust the value of the servlet parameter MAXPOSTDATASIZE. Otherwise, talk with your network administrator.

• Possible cause: userver.exe cannot be started. Error -24, NETERR_START_SERVER, is returned if URouter could not create a UServer process, for example, because the executable was not found.

  Resolution:

  1. Specify correct location for Uniface Server in the urouter.asn file.
  2. Stop the Uniface Router service.
  3. Restart the Uniface Router service.

• Possible cause: Server assignment file cannot be found.

  Resolution:

  1. Check the UST entry for UServer in the [SERVERS] section of urouter.asn. For example:

     myust = d:\u8\bin\userver.exe /asn = userver.asn /dir = d:\u8\Project\web.

  2. Also check whether the specified UST assignment file exists in the /adm directory, or in the directory specified in the /dir switch.
  3. Stop URouter via Services.
  4. Start URouter via Services.

Error Text: Cannot connect to the Uniface process on the remote address/port.

Error ID: Number

• Possible cause: URouter is not running.

  Resolution:

  1. Start URouter via Services.
  2. Check the web server log files for the precise error.

• Possible cause: preRequest trigger or preActivate trigger returns $status=-21 when, for example, the wrong password is provided. With Internet Explorer you get Page 213, and Netscape gives a dialog box to redisplay logon form (see CPT 13968). The WRD should redisplay logon form when $status=-21 is returned by UServer.

  Resolution: Specify correct username and password.

• Possible cause: On Logon screen, Cancel button is pressed with empty username and password.

  Resolution: Specify username.

• Possible Cause: The middleware module UV8 is not specified in the MIDDLEWARE servlet setting. For more information, see MIDDLEWARE.

  Resolution:

  1. Specify MIDDLEWARE=UV8:Host| ...
  2. Stop and restart the web server (for example, Tomcat).
  3. Try the Server Page again.

• Possible cause: URL entered without a Server Page name.

  Resolution: Enter URL with Server Page name.

The requested URL could not be retrieved. 
Connection Failed. 

The system returned: 
(61) Connection refused. 

The remote host or network may be down. Please try the request again.			

• Possible Cause: The web server (for example, Uniface 9705 Tomcat), is not running.

  Resolution: Start the web server again.

• Possible Cause: URL entered with incorrect Server Page name

  Resolution: Enter correct URL, for example, .../wrd/ServerPageName

• Possible Cause: The UST specified in the MIDDLEWARE setting of the WRD Servlet does not match with an entry in the [SERVERS] section of urouter.asn.

  Resolution:

  1. Update web.xml and/or urouter.asn. For example, in web.xml set
     MIDDLEWARE=UV8:MyHost|UserName|Password|myust.
  2. In urouter.asn: [SERVERS] section, set
     myust = d:\Uniface\common\bin\userver.exe /asn = userver.asn /dir = d:\Uniface\project\web.

• Possible Cause: Database not started (properly). The Uniface Server reports:

  Logon (SLE:shmem V8WASV:|webuser|***) failed with status -1,
  Error occurred.

  Resolution: Start the database using correct ID, user, and password.

• Possible Cause: Uniface Router cannot find UnifaceInstallDir\common\adm\urouter.asn. The urouter.log is not generated/updated.

  Resolution: Put urouter.asn in UnifaceInstallDir\common\adm

• Possible Cause: The URL is not correct.

  Resolution: Enter the correct URL, for example, .../wrd/ServerPageName

Bad HTTP request, data size is larger than the maximum allowed size.
Please contact your system administrator.

• Possible cause: the content data size of the request is larger than the value of parameter MAXPOSTDATASIZE.
• Resolution: If the large data size of a request is necessary based on your application logic, adjust the value of the servlet parameter MAXPOSTDATASIZE. Otherwise, talk with your network administrator.

• Possible Cause: Improper Anonymous User Account.

  Resolution:

  1. Start Internet Service Manager, and open the Properties window of the item Default Web Site.
  2. Select the tab Directory Security, and click Edit for Anonymous Access and Authentication Control.
  3. Click Edit for Allow Anonymous Access. The username should start with IUSR_ (check list of available users). Enable Automatic Password Synchronization should be selected.

• Possible Cause: Improper Authentication Method set in the web server.

  Resolution:

  1. Start Internet Service Manager, and open the Properties window of the item Default Web Site.
  2. Select the tab Directory Security, and click Edit for Anonymous Access and Authentication Control. Only the Allow Anonymous Access check box should be selected.

• Possible Cause: You did not enter the complete URL (for example, http://locahost:8080/uniface/wrd/).

  Resolution: Specify the complete URL, for example, http://locahost:8080/uniface/wrd/ServerPageName

• Possible cause: You do not have the proper rights on the SCRIPTS directory.

  Resolution: Configure your web server to enable Execute permissions for the virutal directory in which scripts are located.

• Possible cause: Using URL without /run if the USERUNPREFIX is servlet setting is true; for example, http://localhost:8080/wrd/formstart

  Resolution: Enter URL with /run before /ServerPageName

• Possible cause: Using incorrect servlet, for example, http://localhost:8080/uniface/wrd/formstart or http://localhost:8080/unifacex/wrd/intstate2

  Resolution: Enter URL with correct servlet specification.

The Web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct.

• Possible cause: Invalid WEBAPURL specified. When style sheets are used, the URL to the style sheet is displayed in the location box. In Internet Explorer, you may not get an error.

  Resolution:

  1. Specify correct WEBAPPURL for servlet alias.
  2. Stop and restart the web server.
  3. Try Server Page again.

Error Text: Cannot connect to the Uniface process on the remote address/port.

Error ID :Number

• Possible cause: Directory with error pages cannot be found.

  Resolution: Enter proper directory name in ERRORDIR setting of the URD Servlet Alias. Check the web server log files for the precise error.

The WRD trust store or default Java trust store are missing.

Resolution: Ensure that the WRD trust store file or default Java trust store file are correctly configured.

The WRD trust store is empty.

Resolution: Ensure that the WRD trust store file includes the correct CA certificates.

The certificate configured on Uniface Router has expired.

Resolution: Ensure that the certificate that is imported in java trust store file has not expired.

The Uniface Router uses a Pre-Shared Key (PSK) for TLS Authentication.

Resolution: Configure the Uniface Router to use certificates instead of a PSK. The WRD only supports certificate-based TLS, which provide better security. For more information, see Certificate-Based Authentication.

Resolution:

1. Use the latest wrd*.jar file (for example, for V8.2.02, use wrd2014.jar). In the web server, specify in JavaClassPath, with correct location.
2. Stop and restart the web server.
3. Try Server Page again. If error page is still displayed, try another Server Page or enter a few spaces after the Server Page name and press Enter. If this succeeds, try the previous Server Page.

Resolution:

1. The web server .log file has not reported this error. Put the .jar file in correct location, or specify correct location in the web server's JavaClassPath.
2. Stop and restart the web server.
3. Try Server Page again. If error page is still displayed, try another Server Page or enter a few spaces after the Server Page name and then press Enter. If this succeeds, try the previous Server Page.

error.log file reports, for example, "Couldn’t connect to application server: The Uniface Application Server cannot be started due to wrong logon information specified in the MIDDLEWARE setting."

Resolution:

1. Specify correct UV8 string.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports (getServlet "wrong") javax.servlet. ServletException: No middleware module found.

Resolution:

1. Specify MIDDLEWARE=UV8:Host| ...
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, "Couldn’t connect to application server: Invalid host specified in the MIDDLEWARE setting. The system returned: "invalid host name"".

Resolution:

1. Specify correct Host string.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, "Couldn’t connect to application server: Cannot connect to the Uniface process on the remote address/port. The system returned: "Bad connection parameters"".

Resolution:

1. Specify correct username and password.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, No resource directory set.

Resolution:

1. Specify correct RESOURCEDIR for servlet alias.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, No error directory set.

Resolution:

1. Specify correct ERRORDIR for servlet alias.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, No web application URL set.

Resolution:

1. Specify correct WEBAPPURL for servlet alias.
2. Stop and restart the web server.
3. Try Server Page again.

Resolution:

1. Specify correct definition in the Servlet Class setting.
2. Stop and restart the web server.
3. Try Server Page again.

Resolution:

1. Specify WRD servlet as a Servlet Alias.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, “Couldn’t connect to application server: Invalid format of the MIDDLEWARE setting".

Resolution:

1. Specify correct username and password in Middleware string in the format UV8:Hostname+Portnumber|Username|Password|UST.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, (getServlet "wrong") javax.servlet.ServletException: The value of setting RESOURCETIMEOUT is invalid.

Resolution:

1. Specify a valid RESOURCETIMEOUT value > 0 or remove setting and use default value for servlet.
2. Stop and restart the web server.
3. Try Server Page again.

The error.log file reports, for example, (getServlet "wrong") javax.servlet.ServletException: Given resource directory does not exist.

Resolution:

1. Specify correct RESOURCEDIR pointing to existing correct location for servlet alias.
2. Stop and restart the web server.
3. Try Server Page again.

• Possible cause:AUTHORIZATION is set to RealmName in the servlet properties of the URD servlet.

  Resolution: Remove the AUTHORIZATION servlet property of the URD servlet.

• Possible cause: Incorrect Authentication Method set in the web server.

  Resolution:
  Start Internet Service Manager and open Properties window of the item Default Web Site.
  Select the tab Directory Security.
  Click Edit for Anonymous Access and Authentication Control.
  Only the Allow Anonymous Access check box should be selected.

With view source of HTML page, a line appears such as <IMG SRC="_GET_RESOURCE _?RESOURCENAME= error!!!">.

• Possible cause: The RESOURCEDIR setting of the URD Servlet Alias is not set to the correct location, for example c:\webapps\wasvwww \resources is set while c:\webapps\wasvwww \resource exists.

  Resolution: Specify correct match between RESOURCEDIR and the resources directory.