Here are listed error and you can review attached file:
1st Error -
EJPIC0218E: The Portal archieve install step failed.
Refer to the log file c:\Program Files\\PortalServer\log\LocalizeTrace.archive5.log for additional details.
The Portal installation program is exiting.
After clicking Ok, the 2nd Error -
EJPIC0219E: Enabling Security Failed.
Refer to the log file c:\Program Files\\PortalServer\log\wpinstalllog.txt for additional details.
The Portal installation program is exiting,
Last Error, InstallShield Wizard
java.lang.InternalError: Converter malfunction(UTF-16) - please submit a bug report via
at sun.nio.cs.StreamDecoder$ConverterSD.malfunction(StreamDecoder.java:274)
at sun.nio.cs.StreamDecoder$ConverterSD.convertInfo(StreamDecoder.java(Inlined Compiled Code))
at sun.nio.cs.StreamDecoder$ConverterSD.impRead(StreamDecoder.java(Compiled Code))
at sun.nio.cs.StreamDecoder.read(StramDecoder.java(Compiled Code))
at java.io.InputStreamReader.read(InputStreamReader.java(compiledCode))
at java.io.BufferReader.fill(BufferReader.java(Compiled Code))
at java.io.BufferReader.ReadLine(BufferReader.java(Compiled Code))
at java.io.BufferReader.ReadLine(BufferReader.java(Compiled Code))
at com.ibm.wps.install.UnicodeLogProgressWatcher$LogFile.readProgress(Unknown Source)
at com.ibm.wps.install.UnicodeLogProgressWatcher$LogFile.getProgress(Unknown Source)
at com.ibm.wps.install.unicodeLogProgressWatcher.getProgress(Unknown Source)
at com.ibm.wps.install.ExternalCommandAction$ProgressWatcherRunner.run(Unknown Source)
WARNING: could not write using serviceException: (error code=200; message="C:\Program Files\PortalServer\log\wpinstalllog.txtg(The process can not access the file because it is being used by another process)"; severity=0;exception=[java.io.fileNotFoundException: C:\Program Files\PortalServer\log\wpinstalllog.txt(The Process can not access the file because it is being used by another process)])
If so check the thread below yours where Comland has a solution.
Quote - I've just found a solution. The problem was in the password that I selected for the wpsadmin account. It did not match the machines password policy, hence the db2user could not be created and the installation stopped with the bizare error.
I noticed this in h einstall log...
WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: Failed to get a connection with IP address associated with hostname localhost
Anyone have any ideas?
Please:
1) uninstall DB2 Express via Control Panel -> Add/Remove Programs
2) uninstall Portal *and* WAS by using <installDir> \PortalServer\uninstall\uninstall.bat
3) after uninstalling Portal
i) delete all files in install Directory (of Portal)
ii) delete files in Documents and Settings\Administrator\Local Settings\Temp
iii) delete files in Documents and Settings\Administrator that begin with a 'dot'
iv) delete vpd.properties file in C:\Windows
v) delete WPDB2INS folder and files included in it; should be C:\WPDB2INS
vi) Using user manager, remove the DB2INS user that was created by the install
4) Reboot machine
Try a new install after this. Make sure your cell/node/host names only include alphanumeric characters (the default cell/node name is your machine name and if it includes '-', ' ', or other non alphanumeric characters, this can be a problem.
Also, ensure the account installing Portal Express has administration rights on the installation machine.
Hope this helps.
--travis
It worked!
I had a '-' in my computer name which was causing the problem.
Good luck!
FYI : There was "-" and numeric character in machine name and i took it out. Please see the attached document.
Hope this helps?
I had your same troubles but any of your solutions has helped me.
Simply: my operating system didn't have the last updates.
Try to start db2express installation separately from portal instalation: the error messages are clearer.
Sorry for my bad english,
Hope this help.
I also had the problem described above when upgrading WebSphere Portal 6.0.0.1 to 6.0.1 on windows.
Note: running WAS Network Deployment v6 with portal as managed node.
I had set the wpsadmin and wasadmin passwords in the wpconfig.properties
The problem ended up being I had to start the Deployment Manager and the nodeagent (on the same machine). I initially thought ALL websphere products had to be shutdown because the wizard does a check to see if all application servers are stopped. Clearly that does not apply to the deployment mangager or nodeagent.
Hope this helps someone...