x

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.

x

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 server log may be found in the following location:

On Windows:

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

On UNIX:

ibi/srv77/server_type/edaprint.log

On IBM i:

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

where:

drive

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

server_type

Designates the type of server. 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 JVM Requirements for Java Services.

x

Problem: In the Security OPSYS mode, the listener start request fails with JVM not found messages written to the edaprint.log file.

Cause: Sun Java installation seems to have changed for newer releases. Depending on the ID it was installed by, the "client" directory (that houses jvm.dll) may not have Read & Execute permission in relation to the ID that is used to start the server.

Solution: Based on the Java locations added to the system PATH variable during initial Java set up for the server, locate these directory folders using Windows Explorer. On each of the folders:

1. Right-click the folder, and select Properties.
2. In the Properties window, select the Security tab.
3. Select the ID that will be used to start the server, and select Read & Execute (which will also set the List Folder Contents and Read attributes).

If the JVM not found behavior continues, other intermediate directories for the already changed directories should also be checked for Read & Execute permissions and set in the same way.

x

Problem: When you try to stop the server, the associated Windows service does not stop.

Cause: Any server administrator can stop the server. The ID that installed the server is automatically defined as a server administrator. You can specify additional IDs as server administrators using the Web Console.

If an ID is not a server administrator it will not be able to stop the server, even if that same ID had started the Windows service that started the server.

Solution: Specify the ID that was not able to stop the service as a server administrator:

1. In the Web Console menu bar, select Access Control from the Workspace menu.

   The Security Mode pane opens.

2. Click the Users label (to the right of the folder) in the navigation pane.

   The New User option appears.

3. Click New User.

   The Access Control pane opens.

4. Identify the new administrator by filling in the fields in the Access Control pane.

   For more information about these fields and about specifying an additional server administrator, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.

5. Click Create, and then click Save and Restart.

x

If you have troubleshooting suggestions that you think others will find helpful, we invite you to send them to us so that we can consider including them in a future release. You can:

• Email them to books_info@ibi.com. Include your name and phone number, and include Server Installation Troubleshooting in the subject line.
• Send them to:
  Technical Content Management
  Information Builders
  Two Penn Plaza
  New York, NY 10121-2898

  Please include your name, phone number, email address, and postal address.