Troubleshooting

This Troubleshooting section describes how to solve common problems when using the Sun™ ONE Web Services Platform Developer Edition software on the Solaris™ and Windows platforms.

This section contains the following topics:

• Removing Leftover Files, Packages, and Processes from Previous Solaris 8 or 9 Installations
• Removing Leftover Files, Registry Entries, and Services from Previous Windows 2000 Installations
• Helpful Hints
• Known Problems and Limitations
• How to Report Problems

Removing Leftover Files, Packages, and Processes from Previous Solaris 8 or 9 Installations

---

After uninstalling the Sun ONE Web Services Platform Developer Edition, you might need to run the following script:

<install_dir>/utils/install_cleanup.sh

Running this script removes remaining processes, directories, registry entries, or files from your system.

If this script fails, see the install_cleanup.log for error messages. After correcting any errors, if the script still fails, try the manual procedure described below.

Manual Procedure to Clean Up Installation

1. Change to your installation directory and manually remove the following:

• Sun ONE Application Server-specific entries from the product registry file:

/var/sadm/install/productregistry, if the file exists.

• The following files if they are present:

/tmp/setupSDKNative

/tmp/SolarisNativeToolkit_3.0_1

2. Kill all appservd processes that may be running by typing the following at the command line:

ps -ef | grep appservd

3. Remove all remaining files under the Sun ONE Application Server installation directory.
4. Run the script removePackage.sh from the local directory (<install_dir>/utils).

The path on CD1 or the DVD for this utility is: /cdrom/cdrom0/pkg/SUNWsdp/reloc/$BASEDIR/utils/removePackage.sh

This removes all packages that were added by previous Sun ONE Web Services Platform Developer Edition software installations, or from incomplete uninstallations of products included with the Sun ONE Web Services Platform Developer Edition software.




---

Note	When normal uninstallation fails, these packages can be removed manually using the pkgrm command. For example, to remove the SUNWamas package, enter: pkgrm SUNWamas.

---




The following table shows the lists of packages installed by each product.

The table has five columns. The left column shows the packages installed by the Sun ONE Connector Builder. The second column shows the packages installed by the Sun ONE Identity Server. The third column shows the packages installed by the Sun ONE Identity Server Policy Agent. The fourth column shows the packages installed by the Sun ONE Portal Server. The fifth column shows the packages installed by the Sun ONE Application Server.

Sun ONE Connector Builder 2.0	Sun ONE Identity Server 5.1	Sun ONE Identity Server Policy Agent 1.0	Sun ONE Portal Server 6.0	Sun ONE Application Server 7
SUNWscbc SUNWscbd SUNWscblp SUNWscbs SUNWscbt	SUNWamagt SUNWamcds SUNWamcpa SUNWamdoc SUNWamds SUNWamdsc SUNWamjdk SUNWamsam SUNWamsdk SUNWamsvc SUNWamutl SUNWamws	SUNWamas	SUNWps SUNWpsdt SUNWpsdta SUNWpsdtc SUNWpsdtm SUNWpsdtp SUNWpsdtt SUNWpsdtx SUNWpsjdk SUNWpsmig SUNWpsnm SUNWpsoh SUNWpsrw SUNWpsrwa SUNWpssdk SUNWpsse SUNWpssea SUNWpssep SUNWpssp SUNWpstlj	SUNWaclg SUNWant SUNWasaco SUNWascmo SUNWasdbo SUNWasdmo SUNWasdvo SUNWaslco SUNWaso SUNWaspx SUNWasro SUNWicu SUNWiqdoc SUNWiqfs SUNWiqjx SUNWiqlpl SUNWiqr SUNWiqu SUNWiquc SUNWiqum SUNWj3dev SUNWj3dmo SUNWj3man SUNWj3rt SUNWjaf SUNWjaxp SUNWjhrt SUNWjmail SUNWpr SUNWtls SUNWxrgrt SUNWxrpcrt SUNWxsrt

5. If found, remove the following file:

/var/sadm/install/sodpregistry

Removing Leftover Files, Registry Entries, and Services from Previous Windows 2000 Installations

---

After uninstalling the Sun ONE Web Services Platform Developer Edition, you might need to run the following script:

<install_dir>\utils\install_cleanup.bat

Running this script removes remaining processes, directories, registry entries, or files from your system.

If this script fails, see the install_cleanup.log for error messages. After correcting any errors, if the script still fails, try the manual procedure described below.

Manual Procedure to Clean Up Installation

1. If found, remove the following services:

• iPlanet Administration Server 5.1
• iPlanet Directory Server 5 <machine_name>
• Sun Application Server 7 (doman1:server1)
• Sun Application Server 7 Admin Server (domain1:admin-server)
2. Delete the entries (if found) from the Windows registry using the regedit utility.

This utility can be run from start > run > regedit.

   Entries to be Removed using the regedit Utility

Path to Follow	Entries to be Removed
HKEY_LOCAL_MACHINE        \SYSTEM                \CurrentControlSet                       \Services	\slapd5 \slapd-{machine-name} \admin51-serv \https-admserv60 \ https-{machine-name}<.domain_name>
HKEY_LOCAL_MACHINE        \SOFTWARE                \Sun Microsystems	\Application Server

   Entries to be Removed using the regedit or regedt32 Utility

Path to Follow	Entries to be Removed
HKEY_LOCAL_MACHINE        \SOFTWARE\Netscape                \Administration	\5.1
HKEY_LOCAL_MACHINE        \SOFTWARE\Netscape                \Directory	\5
HKEY_LOCAL_MACHINE        \SOFTWARE\Netscape                \Enterprise	\6.0

---

Note	After removing the entries, reboot the machine.

---

3. Remove the file productregistry found in the following directory:

%SystemRoot%\system32

4. Remove the Sun ONE Web Services Platform Developer Edition internal data directory sodpregistery from the Windows USERPROFILE directory.

Typically the path is:

C:\Documents and Settings\<user_name>\sodpregistry

or

C:\WINNT\Profiles\<user_name>\sodpregistry




---

Note	If you are logged in as Administrator at the time of installation, the <user_name>=Administrator.

---




5. Clean Up the Temp directory.

The Sun ONE Web Services Platform Developer Edition installer and all components install many intermediate files in the temp directory, which occupy a good amount of space on the %SystemDrive%.

Find the following files and delete them:

%SystemDrive%\setupSDKToolkitLog.txt
%TEMP%\Sun_ONE_Web_Services_Platform_Developer_Edition_install.*
%TEMP%\Sun_ONE_Web_Services_Platform_Developer_Edition_uninstall.*
%TEMP%\setupSDKNative.exe
%TEMP%\S1Ident.Template*install
%TEMP%\S1AS.Template*install
%TEMP%\S1FF.Template*install
%TEMP%\S1ASClient.Template*install
%TEMP%\WindowsNativeToolkit_3.0_1.exe
%TEMP%\WindowsNativeToolkit_5.5_1.exe

6. Remove Leftover Start Menu Entries.

Sometimes after uninstalling, the Start menu entries of the installed components are not removed.

If found, remove the following unwanted entries:

• <system profile directory>\All Users\Start Menu\Programs\

For example: C:\WINNT\Profiles\All Users\Start Menu\Programs

• iPlanet Server Products
• iPlanet Web Server
• <system profile directory>\<install user id>\Start Menu\Programs\Sun Microsystems\

Sun ONE Application Server 7

Sun ONE Web Services Platform Developer Edition

Sun ONE Identity Server




---

Note	<system profile directory> can be either: C:\Documents and Settings or C:\WINNT\Profiles

---




7. Sometimes the process setupsdk*.exe is left behind.

To remove this, reboot your system.

Helpful Hints

---

• If the domain name is incorrectly configured, the product does not function properly.

When your machine's DNS domain name differs from the actual domain name detected by the installation program, specify the actual DNS domain name of your machine in the Machine Configuration panel.

• Similarly, if the IP Address and host name of the machine are not detected by the installer, the installation fails.

This could apply if you edit these values (since they are displayed in the editable text fields) and provide an incorrect value.

• (For Solaris 8 or 9 only): The Sun ONE Portal Server and Sun ONE Identity Server installers check for 200MB each in /etc/opt and /var/opt partitions.

Make certain that disk space is available in the above mentioned partitions if you are planning to install the Sun ONE Portal Server or the Sun ONE Identity Server software.

• There are scripts provided to start and stop the core Sun ONE servers. These can be found under:

• <install_dir>/utils directory (for Solaris)
• <install_dir>\utils directory (for Windows)
• A resource kit for deploying and fine tuning the Sun ONE Directory Server can be found at the following location:

http://wwws.sun.com/software/download/developer/5175.html

Using Multiple CDs (Solaris only)

---

It is important to exit from the directory where the disk is mounted. Otherwise, the Installer is not able to eject the disk from the current drive.

A message with this warning appears in the console when the install.sh script is executed.

• When the Sun ONE Web Services Platform Developer Edition installer is finished installing from CD1, it tries to eject CD1.

It might throw a message such as Unable to eject CD. Device Busy.

If this message appears, one or more programs are holding the disk drive.

• Run the command fuser /cdrom/platformcd1

The output is in the form of 123x, where 123 is the numeric pid that is holding the disk and x indicates how the process is holding the disk.

The x can be one of the characters.

The following table shows the characters and their indications.

Character	Indications
c	Indicates that the process is using the file as its current directory.
m	Indicates that the process is using a file mapped with mmap(2). See map(2) for details.
o	Indicates that the process is using the file as an open file.
r	Indicates that the process is using the file as its root directory.
t	Indicates that the process is using the file as its text file.
y	Indicates that the process is using the file as its controlling terminal.

Run the command ps -ef | grep 123 to find the particular process and the command that is holding up the disk.

If you are able to recognize the program that is holding the disk, exit the program. Otherwise, kill the process that is holding up the disk, provided you know that there are no severe consequences.

Click the OK button in the dialog box that appears.

The installer now ejects the disk 1 successfully, and you can insert disk 2 and proceed with the installation.

The programs that are most likely to hold up the disk are:

• A command prompt with a current directory, such as /cdrom/platformcd1.

This could occur if you are in a shell with the current directory as /cdrom/platformcd1 and you switched users, or the shell using commands such as su -, tcsh, sh, csh.

• In some systems, a File Manager GUI program automatically launches when you insert a disk into the disk drive. Interference occurs when the installer is trying to eject the disk, and the error message: Device busy. Unable to eject CDROM appears.

Known Problems and Limitations

---

Following are known problems and limitations of the Sun ONE Web Services Platform Developer Edition:

• Installer Fails on some Solaris machines: Not enough resources.

Sometimes the installer fails after running for a period of time (for example, a half hour in a one CPU, 256MB RAM, Ultra 10). This happens because of inadequate resources.

The installer tries to bring up the first instance of the application server, and the JVM might fail to initialize if there are not enough system resources available. The error is Not Enough Memory or JVM Failed to Initialize.

Solution

Reboot the machine, and try the installation again.

• Installer Fails on some Windows 2000 machines: Not enough resources.

On certain Windows 2000 machines (for example, RAM 523,280 KB System OS: 5.00.2195 Service Pack 2, Free Hard Disk Space 28.4 GB), the installer throws an OutofMemory Exception and hangs while starting the installer.

This happens because of inadequate resources.

Solution

Reboot the machine, and try the installation again.

• The installer fails to install the Sun ONE Web Services Platform Developer Edition software.

When the installation program fails to install the product, the uninstaller is invoked. The uninstallation program restores the system to the original state after cleaning up the product files and directories. You can invoke the installation program again after detecting and resolving the problems that caused the installation failure.




---

Note	You cannot install individual products across different directories. When an installation instance is detected, the same installation directory is used even if you specify a new directory path in the Installation Directory text area.

---




• An attempt to reinstall the product fails, if the previous installation was aborted by invoking the Ctrl+C keys.

Aborting an installation by invoking the Ctrl+C keys causes inconsistencies in the product registry, and any further attempt to reinstall the product might fail.

Workaround: Remove the product registry file created by Setup SDK, and restart the installation program. The Product Registry file is stored at the following location:

/var/sadm/install/productregistry (for Solaris 8 or 9)

%SystemRoot%\system32\productregistry (for Windows 2000)

• The uninstallation program fails to uninstall the Sun ONE Web Services Platform Developer Edition software.

Workaround: Go to the product specific directories, and invoke the uninstallation program separately for each of the products.

• If the installation directory for the platform or for any underlying product has not been properly uninstalled (has been deleted using the rm command), the given platform or product cannot be properly reinstalled.

Workaround: To prevent issues, the related registry information must be removed, as follows:

1. Go to the /var/sadm/install/sodpregistry directory (for Solaris 8 or 9)

Go to %userprofile%\sodpreregistry (for Windows 2000)

2. Remove the .registry file for that particular product.

OR

Remove the entire sodpregistry directory to reinstall the Web Services Platform Developer Edition software.

Remove the entries from the productregistry file which is located at /var/sadm/install.

3. Restart the installer.




---

Note	The above steps can be performed even when partial installation and/or uninstallation was done, and they are required in order to clean-up before performing a fresh installation.

---




• DVD on Solaris 8 and 9 Operating Environments (OE)

The DVD was made in UDF Format.

There is a bug with Solaris 9 OE and some versions of the Solaris 8 OE which mounts the UDF DVD as High Sierra File System (hsfs).

The result is uppercase characters appear to be lowercase.

To verify that you have this problem:

• Do a cd to your DVD Drive.Do an ls.

The DeveloperPlatform.class file appears in lowercase.

• Follow the steps listed below for the workaround for this bug.

1. Eject the DVD.
2. Enter su - root.
3. Enter /etc/init.d/volmgt stop.
4. Enter edit /etc/rmmount.conf and move ident

udfs ident_udfs.so cdrom floppy rmdisk to the top of the ident list.

For example:

# File system identification

this line has been moved to the top

ident udfs ident_udfs.so cdrom floppy rmdisk
ident hsfs ident_hsfs.so cdrom
ident ufs ident_ufs.so cdrom floppy rmdisk
ident pcfs ident_pcfs.so floppy rmdisk

5. Save the file.
6. Enter /etc/init.d/volmgt start.
7. Insert the DVD.
8. Enter cd (DVD Drive).
9. Verify that the DeveloperPlatform.class file is listed in Mixed Case.

How to Report Problems

---

Your feedback is welcome and is extremely helpful for improving the product.

Before contacting us to request assistance, please check the latest documentation for this release at this site:

http://sunonedev.sun.com/building/development/