Troubleshooting for IBM i

Reference:

To troubleshoot an installation problem, identify your problem in the following list, and follow the link to a description of the solution.

If you cannot find your problem described in the list, and cannot resolve it yourself, contact Customer Support Services as described in Information You Should Have and Customer Support.

Problems:


Top of page

x
Reference: Problem: The Server Starts in Safe Mode

Problem: The server starts in safe mode. The Web Console home page displays a message stating that the server is in safe mode and describing what triggered it.

Cause: A common cause for the server starting in safe mode is a problem with the server administrator ID password. For example, the password may have been updated on the operating system but not on the server, so the encrypted copy of the password stored by the server is out of synchronization with the password on the operating system.

Solution: The server administrator can click the fix hyperlink, which is displayed under the problem description, to display the relevant pane and resolve the problem.

For example, if the problem is that the server administrator password is out of synchronization:

  1. Click the fix hyperlink displayed under the problem description.
  2. In the left pane, open the Users folder, then the Server Administrator folder.
  3. Click your user ID and select Properties from the pop-up menu.

    The Access Control pane is displayed on the right.

  4. Type the correct operating system password in the Password field, and type it again in the Confirm Password field.
  5. Click Save and Restart.

    The Security Mode pane opens on the right.

  6. Click the Home icon in the menu bar to return to the Web Console home page.

Top of page

x
Reference: Problem: Java Listener Fails to Start With JVM not found Messages Written to the Log

Problem: The listener start request fails with JVM not found messages written to the edaprint.log file.

Cause: If the server cannot find the Java Virtual Machine (JVM), the JSCOM Listener will not be able to start, and messages will be written to the server log stating that the JVM cannot be found.

The log may be found in the following location:

On Windows:

drive:\ibi\srv77\product_type\edaprint.log

On UNIX:

ibi/srv77/product_type/edaprint.log

On IBM i:

/home/iadmin/ibi/srv77/product_type/edaprint.log

where:

drive

Is the hard drive on which the directory resides (on Windows).

product_type

Designates the type of product. The default values are:

FFS

for a Full-Function Server

DM

for a DataMigrator Server

WFS

for a WebFOCUS Reporting Server

WFM

for a Shared Application Server for WebFOCUS Maintain

Solution: Set up the JVM as described in JVM Requirements for Java Services.


Top of page

x
Reference: Problem: Secured Server Starts Unsecured or Does not Start after Upgrade

A server will implicitly attempt to start unsecured if proper authorization steps have not been completed. Starting the server normally clears edatemp. If prior edatemp files exist (and authorization has not been done), start up will fail due to an inability to clear the directory. However, if an edastart -cleardir command was issued just before the upgrade, there is nothing to clear, no error occurs, and the server starts. If the server starts and is not inspected after the initial start up, the server being in the wrong mode may go unnoticed.

The proper solution is to add proper authorizations after an upgrade, as described in How to Satisfy Security Provider OPSYS Requirements, and restart the server. A new safety measure has also been added. If the environment variable EDAEXTSEC is set to OPSYS explicitly, and a server lacks authorization, it will not start (see Preventing Unsecured Server Starts After Upgrades for details).


Top of page

x
Reference: Problem: CREATE SYNONYM Fails for Excel 2007 (or Higher) Workbooks

Problem: Using the Adapter for Excel Direct Retrieval, the CREATE SYNONYM process for Excel 2007 (or higher) Workbook .xlsx files fails on i5 V5R4.

Cause: The server uses Apache poi-ooxml-schemas (a light version of Java ooxml-schemas) to interpret Excel files. However, poi-ooxml-schemas fail on i5 V5R1 (but work on higher operating system levels). This has been investigated and determined to be outside the server code. It works if the ooxml-schemas jar file is substituted for the poi-ooxml-schemas jar file, or if the JVM is forced into interpret mode.

Solution: If you need to create synonyms from Excel 2007 .xlsx files on i5 V5R4, the simplest solution is to add a JVM property of -Dos400.run.mode=interpret to the Java Listener properties, rather than substituting jar files.


iWay Software