I have tried to install a WP 5.1 on existing WBISF 5.1. The installation pro
cess fails approx. 30% into the install of WP.

I'm installing using the setup CD, chosing custom install for installing por
tal on existing WAS.

The WAS is a version 5.1.1.3 and the WBISF is a 5.1.1.1.

If I try to install on a WAS 5.1.1.1 and WBISF 5.1.1 then WP  validates the 
WAS install and logs that not all required efixes are installed - but when u
sing WAS 5.1.1.3 and WBISF 5.1.1.1 the install begins..

here is the output from the wpsinstalllog.txt: (I have attached the complete
 log file)

(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] Building: /wp.
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Invoking Java Builder on /wp.
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Reading resource change information for wp
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Preparing for build
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Analyzing deltas
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Analyzing sources
(Mar 22, 2005 4:27:21 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Compiling wp/ejbModule/com/ibm/websphere/scheduler
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   (Found 2 errors) Compiling wp/ejbModule/com/ibm/we
bsphere/scheduler
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   (Found 3 errors) Compiling wp/ejbModule/com/ibm/wp
s/datastore/ejb/cleanup
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   (Found 4 errors) Compiling wp/ejbModule/com/ibm/wp
s/datastore/ejb/cleanup
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   (Found 4 errors) Build done
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Invoking Validation on /wp.
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Invoking Library Copying Builder on /wp.
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManager_03598d10.java(8): SchedulerManager cannot be reso
lved or is not a valid superinterface [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ejbModule/com/ibm/wps/datastore/ejb/cleanup
/ EJSRemoteStatelessSchedulerManager_03598
d10.java(8): SchedulerManager canno
t be resolved or is not a valid superinterface
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManager_03598d10.java(8): SchedulerManager cannot be reso
lved or is not a valid superinterface [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManager_03598d10.java(8): SchedulerManager cannot be reso
lved or is not a valid superinterface [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.c
leanup.SchedulerManagerHome cannot be resolved or is not a valid superinterf
ace [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ejbModule/com/ibm/wps/datastore/ejb/cleanup
/ EJSRemoteStatelessSchedulerManagerHome_0
3598d10.java(8): com.ibm.wps.datast
ore.ejb.cleanup.SchedulerManagerHome cannot be resolved or is not a valid su
perinterface
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.c
leanup.SchedulerManagerHome cannot be resolved or is not a valid superinterf
ace [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemot
eStatelessSchedulerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.c
leanup.SchedulerManagerHome cannot be resolved or is not a valid superinterf
ace [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ejbModule/com/ibm/websphere/scheduler/EJSRe
moteStatelessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.clea
nup.SchedulerTaskBean cannot be resolved or is not a type
(Mar 22, 2005 4:27:23 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ejbModule/com/ibm/websphere/scheduler/EJSRe
moteStatelessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.clea
nup.SchedulerTaskBean cannot be resolved or is not a type
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] ejbModule/com/ibm/websphere/scheduler/EJSRemoteState
lessSchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Sched
ulerTaskBean cannot be resolved or is not a type [Severity 2]
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy]   Updating.
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] Shutting down workbench.
(Mar 22, 2005 4:27:24 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] Shutting down workbench.
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] Execution Halted: Compilation Errors Reported
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] Execution Halted: Compilation Errors Report
ed
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction$OutputWatc
her, msg2, StdOut:   [wsadmin] 	[EJBDeploy] 4 Errors, 0 Warnings, 0 Informational Messages
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] 4 Errors, 0 Warnings, 0 Informational Messa
ges
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA5007I: EJBDeploy completed on C:\DOCUME
 ~1\WEBSPH~1\LOCALS~1\Temp\app_102cb16a16
8\dpl\dpl_wps.ear
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA5008E: EJBDeploy failed on C:\DOCUME~1\
 WEBSPH~1\LOCALS~1\Temp\app_102cb16a168\d
pl\dpl_wps.ear: com.ibm.websphere.ma
nagement.exception.AdminException: ADMA0063E: Error in EJB deploy - [ejbModu
le/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerManager_0359
8d10.java(8): SchedulerManager cannot be resolved or is not a valid superint
erface, ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedu
lerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.cleanup.Scheduler
ManagerHome cannot be resolved or is not a valid superinterface, ejbModule/c
om/ibm/websphere/scheduler/ EJSRemoteStatelessSchedulerTask_364deb82
.java(34)
: com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved or 
is not a type, ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSched
ulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskB
ean cannot be resolved or is not a type]
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] Exception in EJBDeploy : com.ibm.websphere.
management.exception.AdminException: ADMA0063E: Error in EJB deploy - [ejbMo
dule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerManager_03
598d10.java(8): SchedulerManager cannot be resolved or is not a valid superi
nterface, ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSche
dulerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.cleanup.Schedul
erManagerHome cannot be resolved or is not a valid superinterface, ejbModule
/com/ibm/websphere/scheduler/ EJSRemoteStatelessSchedulerTask_364deb82
.java(3
4): com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved o
r is not a type, ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSch
edulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.SchedulerTas
kBean cannot be resolved or is not a type]
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA6012I: Exception in run com.ibm.websphe
re.management.exception.AdminException: ADMA0063E: Error in EJB deploy - [ej
bModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerManager
_03598d10.java(8): SchedulerManager cannot be resolved or is not a valid sup
erinterface, ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessS
chedulerManagerHome_03598d10.java(8): com.ibm.wps.datastore.ejb.cleanup.Sche
dulerManagerHome cannot be resolved or is not a valid superinterface, ejbMod
ule/com/ibm/websphere/scheduler/ EJSRemoteStatelessSchedulerTask_364deb82
.jav
a(34): com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolve
d or is not a type, ejbModule/com/ibm/websphere/scheduler/EJSRemoteStateless
SchedulerTask_364deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.Scheduler
TaskBean cannot be resolved or is not a type]
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] Exception: com.ibm.websphere.management.exc
eption.AdminException: ADMA0063E: Error in EJB deploy - [ejbModule/com/ibm/w
ps/datastore/ejb/cleanup/ EJSRemoteStatelessSchedulerManager_03598
d10.java(8)
: SchedulerManager cannot be resolved or is not a valid superinterface, ejbM
odule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerManagerHo
me_03598d10.java(8): com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome 
cannot be resolved or is not a valid superinterface, ejbModule/com/ibm/websp
here/scheduler/ EJSRemoteStatelessSchedulerTask_364deb82
.java(34): com.ibm.wp
s.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved or is not a typ
e, ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364
deb82.java(34): com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot b
e resolved or is not a type]
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] com.ibm.websphere.management.exception.Admi
nException: ADMA0063E: Error in EJB deploy - [ejbModule/com/ibm/wps/datastor
e/ejb/cleanup/ EJSRemoteStatelessSchedulerManager_03598
d10.java(8): Scheduler
Manager cannot be resolved or is not a valid superinterface, ejbModule/com/i
bm/wps/datastore/ejb/cleanup/ EJSRemoteStatelessSchedulerManagerHome_0
3598d10
.java(8): com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be r
esolved or is not a valid superinterface, ejbModule/com/ibm/websphere/schedu
ler/ EJSRemoteStatelessSchedulerTask_364deb82
.java(34): com.ibm.wps.datastore
.ejb.cleanup.SchedulerTaskBean cannot be resolved or is not a type, ejbModul
e/com/ibm/websphere/scheduler/ EJSRemoteStatelessSchedulerTask_364deb82
.java(
34): com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved 
or is not a type]
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA6011I: Deleting directory tree C:\DOCUM
 E~1\WEBSPH~1\LOCALS~1\Temp\app_102cb16a1
68
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] 	at com.ibm.ws.management.application.task.
DeployEJBTask.performTask(DeployEJBTask.java:201)
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] 	at com.ibm.ws.management.application.Sched
ulerImpl.run(SchedulerImpl.java:215)
(Mar 22, 2005 4:27:25 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA5011I: Cleanup of temp dir for app wps 
done.
(Mar 22, 2005 4:27:26 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] ADMA5014E: Installation of application wps 
failed.
(Mar 22, 2005 4:27:26 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] 	at java.lang.Thread.run(Thread.java:567)
(Mar 22, 2005 4:27:26 PM), Wpscore.install, com.ibm.wps.install.ExternalCommandAction
$OutputWatcher, msg2, StdOut:   [wsadmin] WASX7017E: Exception received while running
 file "D:\WebSphere\PortalServer/config/was/EarInstallSingleOrCluster.jacl";
 exception information: com.ibm.ws.scripting.ScriptingException: WASX7132E: 
Application install for d:\WEBSPH~1\PORTAL~1\install\wps.ear failed: see pre
vious messages for details.
(Mar 22, 2005 4:27:26 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdOut: 
(Mar 22, 2005 4:27:29 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdErr: 
(Mar 22, 2005 4:27:29 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdErr: BUILD FAILED
(Mar 22, 2005 4:27:29 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdErr: file:../config/actions/was_cfg.xml:26
6: Java returned: 105
(Mar 22, 2005 4:27:29 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdErr: 
(Mar 22, 2005 4:27:29 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction$OutputWatcher, msg2, StdErr: Total time: 20 minutes 13 seconds
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction, msg2, Return code = 1
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.ibm.wps.install.ExternalComm
andAction, msg2, Executing command: completed
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.installshield.wizardx.condit
ions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windo
ws XP" version="5.1" arch="x86"
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.installshield.wizardx.condit
ions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="IB
M OS/400" version="." arch="."
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.installshield.wizardx.condit
ions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windo
ws XP" version="5.1" arch="x86"
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.installshield.wizardx.condit
ions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="IB
M OS/400" version="." arch="."
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.ibm.wps.install.LogEntryActi
on, msg1, Logging: Configuration of the Portal failed.  Refer to the log fil
e  d:\WebSphere\PortalServer\log\wpsinstall
log.txt for additional information
.  The installer will now exit.
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.ibm.wps.install.ExitCodeActi
on, err, Setting exit code: 401
(Mar 22, 2005 4:27:30 PM), Wpscore.install, com.ibm.wps.install.ExitCodeActi
on, err, Performing system exit

Anybody have any ideas?

Regards,
- Christian

[ Post a follow-up to this message ]

Try installing on top of WAS 5.1.1.3 with WBISF 5.1 or 5.1.1 then after the
install bump the WBISF version.

Having gone through these kinds of issues the levels can be tricky.

Scott

"chrisped" <chrisped.1mbkdb@mail.webservertalk.com> wrote in message
news:chrisped.1mbkdb@mail.webservertalk.com...
>
> I have tried to install a WP 5.1 on existing WBISF 5.1. The installation
> process fails approx. 30% into the install of WP.
>
> I'm installing using the setup CD, chosing custom install for
> installing portal on existing WAS.
>
> The WAS is a version 5.1.1.3 and the WBISF is a 5.1.1.1.
>
> If I try to install on a WAS 5.1.1.1 and WBISF 5.1.1 then WP  validates
> the WAS install and logs that not all required efixes are installed -
> but when using WAS 5.1.1.3 and WBISF 5.1.1.1 the install begins..
>
> here is the output from the wpsinstalllog.txt: (I have attached the
> complete log file)
>
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] Building: /wp.
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Invoking Java Builder on /wp.
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Reading resource change information for wp
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Preparing for build
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Analyzing deltas
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Analyzing sources
> (Mar 22, 2005 4:27:21 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Compiling
> wp/ejbModule/com/ibm/websphere/scheduler
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   (Found 2 errors) Compiling
> wp/ejbModule/com/ibm/websphere/scheduler
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   (Found 3 errors) Compiling
> wp/ejbModule/com/ibm/wps/datastore/ejb/cleanup
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   (Found 4 errors) Compiling
> wp/ejbModule/com/ibm/wps/datastore/ejb/cleanup
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   (Found 4 errors) Build done
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Invoking Validation on /wp.
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Invoking Library Copying Builder on /wp.
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
ager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface
> [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
ager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
ager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface
> [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
ager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface
> [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type
> (Mar 22, 2005 4:27:23 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type [Severity 2]
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy]   Updating.
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy] Shutting down workbench.
> (Mar 22, 2005 4:27:24 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] Shutting down workbench.
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy] Execution Halted: Compilation Errors Reporte
d
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] Execution Halted: Compilation Errors Reported
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] [EJBDeploy] 4 Errors, 0 Warnings, 0 Informational Messag
es
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] 4 Errors, 0 Warnings, 0 Informational Messages
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA5007I: EJBDeploy completed on
>  C:\DOCUME~1\WEBSPH~1\LOCALS~1\Temp\app_1
02cb16a168\dpl\dpl_wps.ear
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA5008E: EJBDeploy failed on
>  C:\DOCUME~1\WEBSPH~1\LOCALS~1\Temp\app_1
02cb16a168\dpl\dpl_wps.ear:
> com.ibm.websphere.management.exception.AdminException: ADMA0063E: Error
> in EJB deploy -
> [ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedul
erManager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface,
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type]
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] Exception in EJBDeploy :
> com.ibm.websphere.management.exception.AdminException: ADMA0063E: Error
> in EJB deploy -
> [ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedul
erManager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface,
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type]
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA6012I: Exception in run
> com.ibm.websphere.management.exception.AdminException: ADMA0063E: Error
> in EJB deploy -
> [ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedul
erManager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface,
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type]
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] Exception:
> com.ibm.websphere.management.exception.AdminException: ADMA0063E: Error
> in EJB deploy -
> [ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedul
erManager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface,
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type]
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] com.ibm.websphere.management.exception.AdminException:
> ADMA0063E: Error in EJB deploy -
> [ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedul
erManager_03598d10.java(8):
> SchedulerManager cannot be resolved or is not a valid superinterface,
> ejbModule/com/ibm/wps/datastore/ejb/cleanup/EJSRemoteStatelessSchedulerMan
agerHome_03598d10.java(8):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerManagerHome cannot be
> resolved or is not a valid superinterface,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type,
> ejbModule/com/ibm/websphere/scheduler/EJSRemoteStatelessSchedulerTask_364d
eb82.java(34):
> com.ibm.wps.datastore.ejb.cleanup.SchedulerTaskBean cannot be resolved
> or is not a type]
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA6011I: Deleting directory tree
>  C:\DOCUME~1\WEBSPH~1\LOCALS~1\Temp\app_1
02cb16a168
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] at
> com.ibm.ws.management.application.task.DeployEJBTask.performTask(DeployEJB
Task.java:201)
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] at
> com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:215
)
> (Mar 22, 2005 4:27:25 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA5011I: Cleanup of temp dir for app wps done.
> (Mar 22, 2005 4:27:26 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] ADMA5014E: Installation of application wps failed.
> (Mar 22, 2005 4:27:26 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] at java.lang.Thread.run(Thread.java:567)
> (Mar 22, 2005 4:27:26 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
> [wsadmin] WASX7017E: Exception received while running file
> "D:\WebSphere\PortalServer/config/was/EarInstallSingleOrCluster.jacl";
> exception information: com.ibm.ws.scripting.ScriptingException:
> WASX7132E: Application install for d:\WEBSPH~1\PORTAL~1\install\wps.ear
> failed: see previous messages for details.
> (Mar 22, 2005 4:27:26 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
>
> (Mar 22, 2005 4:27:29 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
>
> (Mar 22, 2005 4:27:29 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
> BUILD FAILED
> (Mar 22, 2005 4:27:29 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
> file:../config/actions/was_cfg.xml:266: Java returned: 105
> (Mar 22, 2005 4:27:29 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
>
> (Mar 22, 2005 4:27:29 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
> Total time: 20 minutes 13 seconds
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction, msg2, Return code = 1
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.ibm.wps.install.ExternalCommandAction, msg2, Executing command:
> completed
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.installshield.wizardx.conditions.PlatformWizardBeanCondition,
> dbg.platform, target platform: name="Windows XP" version="5.1"
> arch="x86"
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.installshield.wizardx.conditions.PlatformWizardBeanCondition,
> dbg.platform, condition platform: name="IBM OS/400" version="."
> arch="."
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.installshield.wizardx.conditions.PlatformWizardBeanCondition,
> dbg.platform, target platform: name="Windows XP" version="5.1"
> arch="x86"
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.installshield.wizardx.conditions.PlatformWizardBeanCondition,
> dbg.platform, condition platform: name="IBM OS/400" version="."
> arch="."
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.ibm.wps.install.LogEntryAction, msg1, Logging: Configuration of the
> Portal failed.  Refer to the log file
>  d:\WebSphere\PortalServer\log\wpsinstall
log.txt for additional
> information.  The installer will now exit.
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.ibm.wps.install.ExitCodeAction, err, Setting exit code: 401
> (Mar 22, 2005 4:27:30 PM), Wpscore.install,
> com.ibm.wps.install.ExitCodeAction, err, Performing system exit
>
> Anybody have any ideas?
>
> Regards,
> - Christian
>
>
>   +----------------------------------------------------------------+
>   |             Attachment filename: wpinstalllog.zip              |
>   |Download attachment:
> http://www.webservertalk.com/attach...?postid=2484861 |
>   +----------------------------------------------------------------+
>
>
> --
> chrisped
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message965758.html
>

[ Post a follow-up to this message ]