Chapter 4   Troubleshooting iPlanet Application Server




Installation Issues

---

This section describes the known iPlanet Application Server, Enterprise Edition 6.5 installation issues, and the associated workarounds.

Problem (549653): Installation/upgradation fails on Windows if iPlanet Application Server installables are placed in a directory containing spaces or special characters.

Workaround
The iPlanet Application Server installables should be placed in a directory, which has no spaces or special characters.

Problem (546941): iPlanet Application Server fails to install Directory Server on Windows 2000, after IDS 5.0 has been uninstalled from the machine.
This problem occurs if you had previously uninstalled iPlanet Directory Server 5.0 from the Windows 2000 machine on which you are installing iPlanet Application Server, along with the default directory server.

Workaround
Delete ns-dshttpd40.dll from the Winnt\System32 directory before installing iPlanet Application Server.

Problem: Installing iPlanet Application Servers on machines that do not have a static IP address.

Workaround
Install a loopback adapter on the Windows 2000 or NT machine on which you are installing iPlanet Application Server and assign it a static IP address.

Problem: Installation crashes when trying to install on an NFS mounted file system.
iPlanet Application Server cannot be installed on a NFS mounted file system.

Core Server Issues

---

This section describes the known iPlanet Application Server, Enterprise Edition 6.5 core server issues, and the associated workarounds.

Problem (546093): Automatic restart of iPlanet Application Server on the Windows platform may not occur on slower machines.
This is due to a problem with iPlanet Directory Service startup.

Workaround
Add the environment variable, IAS_KASWAITTIME, and set it to between 5-15 (seconds) for automatic startup to work in such cases. This variable need not be set for manual startup.

Administration Tool Issues

---

This section describes the known iPlanet Application Server, Enterprise Edition 6.5 Administration Tool issues, and the associated workarounds.

Problem (544526): Deleting Datasource from Administration Tool does not work

Workaround
Deleting an external or iPlanet Type 2 Datasource cannot be done from the Administration Tool. Delete the datasource entry from the registry using kregedit.

For more information, see Chapter 8, `Administering Database Connectivity' in iPlanet Application Server Administrator's Guide.

Problem (540597): Shutdown method in the StartupClass is not invoked when KIVAes.sh stop command is used

Workaround
Use the command iascontrol stop. We recommend that you do not use KIVAes.sh as it has been deprecated.

For more information, see Chapter 1, `Performing Basic Administrative Tasks' in iPlanet Application Server Administrator's Guide.

---

Note	To use the iascontrol command, you must have registered the server with the Administration Tool.

---

Deployment Issues

This section describes the known iPlanet Application Server, Enterprise Edition 6.5 Deployment issues, and the associated workarounds

Problem: While trying to deploy an EAR file, iasdeploy displays `no servers registered in the registry' error.

Workaround
This message will be displayed if you haven't first registered the iPlanet Application Server using the Administration Tool.

This error could also be caused if there are multiple instances of iPlanet Application Servers or the server is deployed in a remote machine. In such cases you have to mention the instance of iPlanet Application Server you are deploying the application on and its host and port number information.

For more information, see iPlanet Application Server Administrator's Guide.

Problem: Either home or remote of the bean Document.class not found".
This error message usually occurs if you have packaged Servlets, JSPs, XML files and Beans in a single EAR file.

Workaround

1. Create a new EJB module and add the EJBs and any classes they depend on to it.

2. Create a Web module and add the Servlets, JSPs, XML files and any classes they depend on to it.

3. Add both these modules to a J2EE application and fix any unresolved links to the EJBs.

Problem (548426): Redeployment of an application/module does not remove the contents of the previously deployed application's/modules's contents. It just overwrites the currently deployed application/modules.
Some of the registry settings are also not overwritten when an application is redeployed.

Workaround
To perform a clean redeployment, first perform a remove followed by a deploy.

Database Support Issues

---

This section describes the known iPlanet Application Server, Enterprise Edition 6.5 database support issues, and the associated workarounds.

Problem (481221): RowSet lookups from JNDI is not implemented for Third Party drivers.

Workaround
To use RowSet, construct the RowSet object directly and set the URL to make the underlying connection.

Problem (427149): Text/blob datatypes in prepared statements is not supported for Informix and Sybase native drivers.

Workaround
Use Third Party JDBC drivers.