BigAdmin: Sun Java Enterprise System (Java ES) 5 Update 1
FAQs: Sun Java System Portal Server Installation on Microsoft Windows
Print-friendly VersionPrint-friendly Version

Santosh Chikurambotla and Sunil Bhaskaran, May 2007

This FAQ provides troubleshooting information on the issues you might face when you install Sun Java System Portal Server (referred to hereafter as Portal Server) on the Microsoft Windows platform.
 

Q:
When I run the Sun Java Enterprise System (Java ES) 5 installer, installation is aborted with the following error message: Error 1607: Unable to Install InstallShield Scripting Run Time. What is the reason?
A:
The Java ES 5 Update 1 installer tries to install the Installscript engine if the Installscript engine is not found on the machine or an older version is installed on the machine. This error message is a system-specific error and can be caused by a system-specific setting. For more information about the reasons, refer to the InstallShield Consumer Central web site.

Back to top

Q:
When I uninstall Java ES 5 Update 1 from the machine, some DLL files that are not installed by the Java ES 5 installer are not found. What is the reason?
A:
The Java ES 4 installer for Microsoft Windows copies some DLLs to the system32 folder since some products need them. The Java ES 5 Update 1 installer for Microsoft Windows installs higher versions of the same DLLs to the JavaES-install-directory\share\lib folder. However, if a DLL with the same name already exists in the system32 folder, Microsoft Windows uses that. To prevent this, the Java ES 5 Update 1 installer for Microsoft Windows renames the following DLLs to DLL-name.old if they are found in the system32 folder:

ctestfw.dll, ctestfwd.dll, digestmd532.dll, fort32.dll, icudt2.dll, icudt3.dll, icuin2.dll, icuin2d.dll, icuin3.dll, icuio2.dll, icuio2d.dll, icuio3.dll, icule2.dll, icule2d.dll, icule3.dll, icuuc2.dll, icuuc2d.dll, icuuc3.dll, libdb42.dll, libdb_java42.dll, libnspr4.dll, libplc4.dll, libplds4.dll, nsldap32v50.dll, nsldappr32v50.dll, nsldapssl32v50.dll, nss3.dll, nssckbi.dll, sasl32.dll, smime3.dll, softokn3.dll, ssl3.dll, swft32.dll

Hence all these DLLs can be found on the target system with the .old extension added to their respective names after Java ES 5 Update 1 is uninstalled. This information is stored in the installer log file located at %TEMP%\SunJavaES.log.

Back to top

Q:
I have JDK 5.0 Update 11 (1.5.0_11) installed on my machine and most of the Java ES 5 Update 1 product configurations are failing. What should I do?
A:
If you are using JDK 5.0 Update 11, do the following before invoking the Java ES 5 Update 1 installer for Microsoft Windows.
  1. Click Start->Run.

  2. Type regedit and press Enter.

  3. The Registry Editor window appears.

  4. Go to the following registry location: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.5.0_11.

  5. Double-click the JavaHome registry key.

  6. Change the Value field from 1 to the JDK 1.5 Update 11 installation directory, for example, C:\Program Files\Java\jdk1.5.0_11.

  7. Go to the following registry location: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.5.

  8. Double-click the JavaHome registry key.

  9. Change the Value field from 1 to the JDK 1.5 Update 11 installation directory, for example, C:\Program Files\Java\jdk1.5.0_11.

Back to top

Q:
Where can I find the Java ES 5 Update 1 for Microsoft Windows installation log files?
A:
The log file is located in the %TEMP%\SunJavaES.log directory.

Back to top

Q:
What is the default user name I can use to log in to the Sun Java System Access Manager administration console and Portal Server administration console?
A:
The default user name is amadmin. The password is the same as the password that you typed in the Administrative Settings panel of the Java ES 5 Update 1 installer.

Back to top

Q:
In the Maintenance mode, I selected Portal SRA in the Product Selection panel and tried to install and configure Portal Server. But in the Summary.txt of the Finish panel, Access Manager and Portal Server are not listed under the list of configured products. Why are these components not configured?
A:
In the Maintenance mode, when you select Portal SRA, its dependent products Directory Server and Service Registry are not selected by default. You need to select them manually. This results in the configuration failure of Portal Server and Access Manager. You can again run the installer in the Maintenance mode and select Directory Server and Service Registry and install them. Then you can configure Access Manager and Portal Server manually.

Back to top


For more information about Portal Server and Java ES 5, see the Sun Java Enterprise System information hub on BigAdmin: http://www.sun.com/bigadmin/hubs/javaes/.


Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License.


BigAdmin
  
 
 
 
Would you recommend this Sun site to a friend or colleague?
Contact About Sun News & Events Employment Site Map Privacy Terms of Use Trademarks Copyright Sun Microsystems, Inc.