Sun Java System Web Server 7.0 Release Notes for Microsoft Windows

Installation

The following table lists the known issues in installation.

Table 1–3 Known Issues in Installation

Problem ID 

Description 

6492159 

Java ES 5 Web Server is creating two instances

Java ES Installer is updating the WS_DOCROOT value in the properties file. For this reason, the configurator is creating two instances for the Web Server. 

Workaround: None.

6408072 

Need icons for objects in Programs folder.

The objects in the Sun Java System Web Server 7.0 folder are created with default Windows program icons and do not have specific icons that denote Sun programs. 

Workaround: None.

6311607 

Installer crashes in CLI mode if the administration password is >= 8 characters.

If the administration user password is greater than eight characters, any invalid input to the administration port, web server port, or the administration user ID crashes the installer. 

Workaround:

When installing Web Server 7.0 by using the command-line interface (CLI), the administration password must be set to less than (<) eight characters. 

6287206 

Cannot install if the setup is started from a shared folder on the network.

On the Windows platform, you are unable to install the product when the installer setup.exe is started from a shared network folder on another machine.

Workaround: None.

6408072 

On Windows, need icons for objects in Programs folder.

The objects in the Sun Java System Web Server 7.0 folder on Windows are created with default Windows program icons and do not have specific icons that denote Sun programs. 

6492144 

On Windows, CLI installer does not handle ctrl+c while entering the password.

The installer does not accept ctrl+c and hence the terminal becomes unusable.

4988156 

Installing the standalone product over an existing JES installation and vice-versa is not supported

Installing the stand-alone product Web Server 7.0 over an existing Java Enterprise System (JES) installation is not supported. JES users of the Web Server must use the JES installer to upgrade to the newer version of the Web Server.  

Workaround: None.