Migration
The following table lists the known issues in migration.
Table 1–4 Known Issues in Migration
|
Problem ID
|
Description
|
|
6498416
|
Web Server instance creation fails after migration
from Java ES 4 to Java ES 5
After migrating Java ES 4 to Java ES 5, if you try to create a Web Server
instance for the migrated server, the instance creation fail. The following
error message is displayed:
windows.machine.com:ADMIN3210:Could not create the instance
because the Windows service "https-jeswin123.india.sun.com' already exists.
|
For more information , see http://docs.sun.com/app/docs/doc/819-2625/6n4tcivk8.
|
|
6493944
|
Web Server migration fails on Windows
Workaround: After completing migration,
follow these steps to update Root certs library path:
-
List the available root certs.
"WebServer-base\bin\modutil" -list -nocertdb -dbdir
"WebServer-base\admin-server\config-store\test\config"
-
Delete the existing Root certs.
"WebServer-base\bin\modutil" -dbdir "WebServer-base\admin-server\config-store\test\config" -delete "Root Certs"
-force
-
Update the Root certs with correct library
path.
"WebServer-base\bin\modutil"
-dbdir "WebServer-base\admin-server\config-store\test\config"
-add "Root Certs" -libfile "nssckbi.dll" -force
where WebServer-base is C:\Program
Files\Sun\JavaES5\WebServer7 and configuration name is test.
Note –
This procedure should be performed after using the migrate command
and before using the migrated config command.
|
Note – For detailed migration information, see the Sun Java
System Web Server 7.0 Installation and Migration Guide. This guide
contains information about migrating from version 4.1 to 7.0, and from version
6 and compatible versions to 7.0.
