Troubleshooting Web Administration for i

Symptom: Cannot read or write to QUSRSYS/QATMHINSTC

Cause

The Web Administration for i interface uses the IBM Toolbox for Java™. When reading and writing files in QSYS, the Java Toolbox sometimes uses the DDM server. If the DDM server is not running, this may result in problems reading or writing the QUSRSYS/QATMHINSTC file containing HTTP Server definitions.

Solution

On an IBM i command line, enter STRTCPSVR *DDM.

Symptom: Web browser problems with HTTP Server

Cause

Your Web browser may not be configured correctly.

Solution

Below is a list of common problems and solutions for your Web browser.

Miscellaneous Microsoft Internet Explorer errors related to incorrect interpretation of HTTP/1.1 in response

Microsoft Internet Explorer sends requests in HTTP/1.1 format but seems to only accept responses in HTTP/1.0 format. The work around is to tell HTTP Server the request came in as HTTP/1.0 format.

Fore example: BrowserMatch "MSI 4\.0b2;" downgrade-1.0 force-response-1.0

URL not found when clicking on a file in a directory listing from Netscape

If AlwaysDirectoryIndex is set to OFF and a URL for a directory without a trailing slash is requested, then Netscape does not request the file relative to the director in which the file exists in the resulting directory listing.

Microsoft Internet Explorer does not display customized error messages

If Internet Explorer is not displaying the customized error messages, check to see if the preferences for the browser are set to show friendly HTTP error messages. Disable this preference and the customized error massages should display properly.

When using HTTPS, Microsoft Internet Explorer shows pages that were cached when using HTTP

If the browser is showing cached pages instead of connecting to the server using SSL, clear the browser's cache.

Prompted for password when using certificate for client authentication

If you are using a Certificate Authority that offers the option to protect the private key of your certificate with a password (such as for the Microsoft Internet Explorer browser), and you use the certificate for client authentication, you are prompted for the password after about 2 minutes of idle time. This happens even if you have disabled SSLV2 in the browser being used and in the server because you are trying to use the longer SSLV3 cache time-out interval. This is a security feature that protects your private key if you are away form your client, even though it may look like an SSLV3 caching problem.

Certificate not recognized by browser

If you add a certificate to your browser, the browser may not recognize that there is a new certificate until you restart your computer.

Symptom: ADMIN server will not start

Solution

Check to make sure you have the proper authorities. See User profiles and required authorities for HTTP Server for specific authority and profile information.

Symptom: HTTP Server will not start or functions will not work

Solution

General items to check:

1. Check /QIBM/UserData/HTTPA/admin/logs, HTTPAdmin.log, error_log, and any other logs you may have. More information on the cause of the problem may be found there.
2. Use CHKPRDOPT to 57XXDG1, SS1, TC1 and JV1.
3. Check joblog for user QTMHHTTP.
4. Check QTMHHTTP and QTMHHTP1 user profiles.
5. Verify that *PUBLIC is not *EXCLUDEd from '/' (Use WRKLNK '/' and take option 9).
6. Verify that QSERVER and QUSRWRK subsystems are running.

Error messages:

ZSRV_MSG0252: SSL initialization operation failed, return code error = 107

107 is the Secure socket API error code, it means GSK_KEYFILE_CERT_EXPIRED. You may be able to circumvent this problem by going to DCM to extend the validity.

Error ZSRV_MSG0358

Found in admin log. Verify that there is a host table entry in CFGTCP Option 10 that matches the host + domain name in CFGTCP Option 12, and set 'Host Name Search Priority' to *LOCAL.

Error ZUI_50004 - 'no *IOSYSCFG authority'

Verify that user has *IOSYSCFG Authority. If *IOSYSCFG is granted by a GROUP profile, verify that PTF SF65588 (V4R5) is applied. Check that there are NO user .jar files in the /QIBM/ProdData directory path - this directory is for IBM use only.

Error HTP8015

Verify that the latest PTFs for DG1 product are applied.

Error CEE0200

Verify that 57XXJV1 Options *Base, 5, and 6 are installed,

Error ZSRV_MSG0302 :User qsecofr:authentication failure for "/":1

Known problem with 128 character passwords on V5R1. HTTP servers cannot use 128 character passwords. You may be able to circumvent this problem by changing the password in the user profile to CAPITAL letters and using CAPITAL letters to log into the ADMIN screen.

ZSRV_MSG0252: SSL initialization operation failed, return code error = 107.

107 is the Secure socket API error code, it means GSK_KEYFILE_CERT_EXPIRED. You may be able to circumvent this problem by going to DCM to extend the validity.

Symptom: Unknown server type when working with HTTP Servers in ADMIN

Solution

Ensure that LOOPBACK and LOCALHOST are configured to resolve to 127.0.0.1 and can be PINGed from the IBM i command line. Verify that there are no exit programs for exit point QIBM_QPWFS_FILE_SERV. Verify that QSERVER and QUSRWRK subsystems are running and that current group PTF for DG1 product is applied.

Symptom: All servers show status 'Stopped'

Cause

This problem was determined to be caused by an OEM security application that registers many exit point programs.

Solution

Remove the application to eliminate the problem.

Symptom: Cannot access ADMIN or some functions do not work

Solution

Verify the following:

• Verify that user's browser is not using a proxy to access the ADMIN server.
• Verify latest DG1 PTF's.
• Verify that user profiles QTMHHTTP and QTMHHTP1 are enabled.

Symptom: User Profile does not have *IOSYSCFG

Solution

In the HTTPAdmin.log you will find error: 'NoRouteToHostException'. Do the following:

• Verify that 127.0.0.1, LOOPBACK and LOCALHOST are configured and work.

Symptom: Cannot create new HTTP Server instance

Solution

Verify LOCALHOST , LOOPBACK and 127.0.0.1 exist and work.

Symptom: Net.Data® error

Include object specified in /QIBM/ProdData/HTTPSVR/MRIXXX/Macro/qzhamsg.nds at line 208

Solution

Verify that directory /QIBM/ProdData/HTTPSVR/Macro/ contains only objects that are appropriate to the current OS version .

Symptom: Error occurred opening file

Cause

If your HTTP Server configuration uses the Rewrite directive and does not have the proper access for QTMHHTTP configured, your server will not start.

Solution

Make sure QTMHHTTP has *RWX access authority to the /tmp directory.