|
Problem(Abstract) |
Installation of WebSphere® Application Server V5.1, on all
editions of Microsoft® Windows® 2003, fails when installing from a network
file system or mapped network drive. If the Embedded Messaging feature is
selected, installation hangs at 80% but does not write any errors to the
install log. If Embedded Messaging is not selected, installation fails
with error code 60, "JVM not found." |
|
Cause |
By default, Windows 2003 places security restrictions on
executable files activated through a network resource. The "amqicsdn.exe"
process needs permission to be activated during installation. However, the
activation dialog is never presented to the user because it is activated
underneath the WebSphere Application Server installer. The "amqicsdn.exe"
never starts as a result, which causes the entire installation to hang.
This process is essential, as it is responsible for applying CSD04 to the
MQ product during installation.
Note: A separate issue can cause the WebSphere Application Server
installation to fail during this stage in the installation process. See Technote
1178257 for details.
If Embedded Messaging is not installed, the installation might fail with
error code 601, "JVM not found". This occurs for similar reasons as
described above. The operating system security restrictions prevent the
installation from taking place from a network file system. |
|
Resolving the
problem |
There are two solutions to this issue. Choose the solution
that best suits your environment.
Solution 1: Install from a non-networked resource
- Terminate the hung installation process.
- Manually uninstall the partial WebSphere Application Server
installation. This is a very important step, as the partial installation
can interfere with future installations. See the manual
uninstall instructions in the WebSphere Application Server V5.1
Information Center for full details.
- Copy the install image from the network file system to a local file
system.
- Run the installation again from the local file system.
Solution 2: Temporarily relax operating system security
restrictions
- Terminate the hung installation process.
- Manually uninstall the partial WebSphere Application Server
installation. This is a very important step, as the partial installation
can interfere with future installations. See the manual
uninstall instructions in the WebSphere Application Server V5.1
Information Center for full details.
- Add network share to the list of Trusted Sites:
- Open Control Panel, select Internet Options
- Go to Security tab
- Select the Trusted Sites icon in the list of web content
zones.
- Select the Sites... button.
- Add the server resource to the list.
For example, if the network server is named myserver.ibm.com, then add
"file://myserver.ibm.com/".
- Click OK. Leave the Security panel open, because there is more
work to do here.
- Change permissions for Trusted Sites to Enable "Launching
applications and unsafe files":
- Starting from the Security panel described in the previous
step, select the Trusted Sites icon.
- Click Custom Level... in the "Security level for this zone"
area.
- Locate the Launching applications and unsafe files option.
- Select Enable for this option.
- Click OK, then click OK on the Security panel.
- The system is now prepared to install WebSphere Application Server
from a network file system. Run the installation program again.
- Once the installation is complete, undo the changes made in steps 3
and 4.
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|