Error in KMC installation. waiting 1800 seconds at 2nd phase and errors out

Question

Hi,
I am installing KMC and on 2nd phase "Deploy Content Mangement and Collaboration Components " it hangs stating
Portal Configuration upgrade (66 of 69 done.0 with warning Time elapsed
<Number> seconds. waiting....... ".
Note 779699 referred. In the file cf_installation.report there are no
two lines. it has only one line. Please help..
Thanks

Answer 1

Hi Tony,
you should adjust the timeout parameters and do a redeployment again, in order to fix this problem.
Have you checked the two SAPNotes mentioned in your note (779699): Note: 769859 (About the parameter: PingReplyTimeout)
and Note: 752049 (About the parameter: AdditionalLoadTimeOut)???
You might experience problems seeing the second Note so I paste the important paragraph here:
a) ATTENTION : Duration of configmerge
By starting the engine after deployment a CM configmerge is initiated as part of the upgrade
process.
Depending on the hardware the configmerge may take 15min up to 2h.
Do NOT restart the servlet engine before you're absolutely sure that the config merge has
finished.
Wait till the portal is back on its own.
View the status of the configmerge in the latest config.*.trc file, located in
..usrsap<j2ee instance>clusterserver.
The status of the merge process is also written to the error.log available under:
..usrsap<j2ee instance>clusterservermanagerconsole_logs
Wait for this entry in processing the upgrade 41 out of 41 : "The upload sequence is now
complete, all the upgrades have been performed."
b) ATTENTION : Beware of Timeout definition for SAP J2EE
Be sure that the J2EE engine is not stopped due to a timeout definition during the merge.
This would cause an undefined status of the system. Toavoid this, set parameter
AdditionalLoadTimeout=10800 (in seconds) to an appropiate value for that upgrade
(..usrsapxxj2eej2ee_00 clusterservermanagerssettingsServiceManager.properties).
Additional timeout parameter since J2EE PL 22
This AdditionalLoadTimeout parameter needs also to be set in ServiceManager.properties
for state (..usrsapxxj2eej2ee_00 clusterstatemanagerssettingsServiceManager.properties).
The configtool can also be used for checking and setting these parameters.
If server node is started by the r3startup service of the dispatcher
Set the r3startup to manual and call any "go" directly.
Troubleshooting a timeout
If run already into timeout and stucked on certain stage of config- merge it's usually
sufficient to adjust timeout parameters and choose SDM option 'Redeploy' and do another
deploymenent and subsequent configmerge, normaly this keeps the system in a valid state.
Hope this helps,
Robert