1623427 - XI3.1 install on solaris fails at 55% during initializing CMS state

• XI3.1 SP3 full Install on Solaris server fails at 30 - 55% during initializing CMS state
• Sometimes, a failure at 33% yields following error when instlling with oracle as CMS database :
  Checking for recommended patches...
  Patch checking complete
  FATAL ERROR: Product's parent not found on tree: 4631AB2C-D9BA-BAAC-D09A-4E9AD117891D, parent id: 5418F914-1D31-4849-822C-314AC28B06BF
  
• In another attempt  to install with mysql, a failure occurs at 55% while intializing CMS.
• The install log shows following messaging
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) /usr/sap/BOJ/bobje/setup/jscripts//ccmunix.js started at Fri Jul
  29 2011 19:24:33 GMT-0400 (EDT) Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) About to process commandline parameters...
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Starting cms...
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Finished processing commandline parameters.
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Warning: No password supplied, setting password to default.
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Warning: No username supplied, setting username and password to default.
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Warning: No authentication type supplied, setting authentication type to default.
  Fri Jul 29 2011 19:24:33 GMT-0400 (EDT) Warning: No CMS name supplied setting CMS name to machine name.
  .....
• Further examination of log files shows that the process seems stuck at the call of cmslogon.jar. This portion of the installation should either succeed and move on to the next portion, or fail and retry the logon attempt of the CMS to the database. Neither happens, according to the BusinessObjects.12.1.log file in setup/logs/.
• The CPU utilization at the hung point doesnt show any process related to the Businees objects as consuming CPU resources
  
  
  
  

BOXI3.1 SP3
SUN Solaris servers using Containers / Zones
Each container 24 - 48 virtual processors