Sun Java Enterprise System 5 Release Notes for Microsoft Windows

Known Issues and Limitations

This section lists known issues in this release.

Single Quote Not Allowed in Passwords and Root Suffix

In passwords such as for amadmin and the Directory Server root suffix, Access Manager does not support a single quote (\q). However, the back-slash (\\) is supported.

Installing Access Manager 2005Q1 With SSL Enabled Directory Server

If Directory Server is already installed and SSL is enabled, the Directory Server must also listen on a non SSL (LDAP) port. Access Manager must be configured to use the LDAP port, otherwise the installation of Access Managerfails.

After Access Manager has been configured to use the LDAP port, the user may disable the LDAP port.

Access Manager SDK Configuration Causes Web Server Startup Failure Errors (6293225)

InAccess Manager's SDK configuration, the the AMConfig.properties file contains the wrong information and causes a series a web server startup failures. The following variables do not have the correct information:

com.iplanet.am.directory.host
com.iplanet.am.server.host
com.iplanet.am.console.host
com.iplanet.am.profile.host
com.iplanet.am.naming.url
com.iplanet.am.notification.url

Solution On node B, where Access Manager SDK is installed with Web Server, modify the webserver-instance-dir/config/server.xml file and add the required Access Manager JAR files to the classpath.

Web Server Services Do Not Start After a Successful Configuration in `eval config` Mode (6472285)

After installing Web Server in eval config mode on Windows operating system, Web Server services are not started automatically.

Workaround: Manually start the Web Server services.

Web Proxy Server Services Do Not Start After a Successful Configuration in `eval config` Mode (6472289)

After installing Web Server in eval config mode on Windows operating system, Web Proxy Server services are not started automatically.

Workaround: Manually start the Web Proxy Server services.

PS-SRA, FTP, And Netlet Does Not Work If the Reverse Lookup Is Not Configured in DHCP (6472391)

While using the IP address in the netlet, if the reverse lookup entry for a particular host is not configured in the DHCP server, then the operation associated with that host does not work.

For example, if nslookup.exe ipaddress fails to return the host name then the netlet operations will not work for these IP addresses.

Workaround: Use hostnames instead of IP addresses.

HADB Instance Is Not Starting in Application Server Suite (6480152)

If a Windows machine is not connected to the network, the HADB instance does not start.

Workaround: Connect Windows machine to the network.

Installer Does Not Detect Existing Installation of Sun Java WebConsole (6487548)

Workaround: Use one of the following workarounds:

Remove the Sun Java Web Console version already installed on the Windows machine before actually proceeding with Java ES 5 installation.
Re-register the applications that were registered with previous Sun Java Web Console version again with the newer version in order to continue accessing those applications

Java ES 5 Install Fails Unpredictably on the Machine With 1GByte RAM Memory (6496578)

On the Windows platform, installing with Install all in Configure Automatically During Installation mode fails unpredictably in post configuration stages on machine with low memory.

Workaround: Use one of the following workarounds:

Optimize your Windows OS Virtual memory setup.
Maximize free RAM before you start the Java ES installer Stop all unecessary programs and services.
Do a selective install, use the Custom option to install products selectively.

Windows-Natives: Dlls From Windows System32 Conflict With Java ES Dlls (6496600)

This problem occurs when certain DLLs are in the Windows system32 folder, such as libnspr4.dll, nss3, and smime.

These DLLs conflict with Java ES versions of DLLs that are installed in the install-dir/share/liband prevent proper functioning of Java ES servers.

Workaround:

Rename these DLLs in the system32 folder so Java ES servers will use the correct versions of these DLLs.

Note –

Renaming these DLLs could cause some legacy applications that installed these DLLs in system32 folder not to function.

User Unable to Log into he Web Console After Installing on Windows XP SP2 OS (6498436)

Workaround:

On Windows XP Professional, the guest account must be disabled.

The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest must be set to 0 in order for authentication to succeed.

Java ES 5 Windows Upgrade Using Configure Manually After Installation Option Creates Message Queue and High Availability but no Application Server Program Group (6500958 )

Whenever a product component is installed or upgraded in Configure Manually After Installation mode, the product's shortcuts are created only after the product is configured manually.

Note –

Message Queue is not affected by this problem.

Workaround: None.

The View Log Button on the Uninstall Complete Panel Does Not Display the Log Files (6505473)

When installation is done in a remote session, the installer logs are stored in the temp directory.

If the system reboots during installation or uninstallation, the temp is deleted. Therefore, the log files are not available when you click the View Log button.